On 26 October 2007 19:21, Larry Hall (Cygwin) wrote:
>> A cool new network tool would be a RCP that runs D2U as a option.
>> Does such a tool exist?
>
>
> Don't know. But it's simple in principle to write a script that you invoke
> to do what you want.
Bog-standard ftp does text-mode transfe
Steve Richmond wrote:
Is there a standard (read easy) way to bring over files and run D2U on each
file?
I'm guessing what you really mean is "automated". Not anything in Cygwin
as far as I know.
I just found a tool called RSYNC. Do you have experience with that?
Why isn't RCP and FTP inc
s for your help!
> Date: Sat, 22 Sep 2007 06:28:38 -0600
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]; cygwin@cygwin.com
> Subject: Re: Cygwin setup on XP/Vista (UNIX/DOS compatibilty question)
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> htt
Steve Richmond wrote:
> Hi Eric,
>
> I removed everything and completely re-installed Cygwin with
> setup.exe using the UNIX
> binary option. I 'set -o igncr' in .bashrc. 'set | grep SHELLOPTS'
> show igncr is set.
> Yet the problems of bash scripts failing with '\r' errors and the
> resultant
On Sep 24 02:30, Steve Richmond wrote:
> In a unrelated problem, the diff command doesn't seem to be in the
> installation.
> It was missing the last time I installed cygwin-1.5.24.
diff is part of the diffutils package which isn't installed by default.
You have to manually select it in setup's p
PROTECTED]
> To: [EMAIL PROTECTED]; cygwin@cygwin.com
> Subject: Re: Cygwin setup on XP/Vista (UNIX/DOS compatibilty question)
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> http://cygwin.com/acronyms/#PPIOSPE -> redirecting to the list.
>
> According to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://cygwin.com/acronyms/#PPIOSPE -> redirecting to the list.
According to Steve Richmond on 9/22/2007 12:31 AM:
However it behaves differently. After I install it using UNIX, bash scripts
fail with '\r' errors, meaning it can't find the C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Steve Richmond on 9/21/2007 5:40 PM:
> On PC2 and PC3, I have an up-to-date version of Cygwin and bash
> (3.2.5(7) i686-pc-cygwin).
That's not up-to-date. The latest is 3.2.25(16).
>
> However it behaves differently. After I install i
I have a problem with running bash scripts and UNIX/Win compatibility.
I have 3 computers: a Windows ME PC (PC1), a Windows XP (PC2) and a
Windows Vista (PC3).
On PC1, I have an old version of Cygwin and bash (3.00.16.14 i686-pc-cygwin).
All my scripts have a .TXT suffix, so I can edit with Vim e
9 matches
Mail list logo
