Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<m10tghA-007vPHC@light.lbin.com>
Date:	Mon, 14 Jun 1999 17:03:16 -0700 (PDT)
From:	<itz AT lbin DOT com>
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	text vs binary again (ftp) :-(

After trying for a long time to get some very basic functionality with
a text mount setup, I gave up and started from scratch, with binary
mount only.  I have only a single entry in my mount table:

d:    /      native      text=binary

Instead of making mount entries for drives shared from other WinBlows
machines, I created symlinks for them, for example:

amazon:~$ ls -l cstrans
lrwxrwxrwx   1  administ        None    22      Jun 2 19:43 cstrans -> //l/cstrans

where L: is mapped to another machine's F: in the WinBlows GUI.

Overall, this seems to work much better.  Gone are all bash troubles
with history, sourcing the startup files, etc.  I compiled man_db and
now feel _almost_ like on a true Unixoid system (working as root all
the time, of course :-)

One trouble remains, though.  When I ftp a file from a Unix server to
one of the symlinked foreign drives, newline -> CRLF conversion
happens, no matter what I do.  That is, even if the ftp transfer mode
is set to binary.  On the other hand, transfers to my local drive work
OK.

This is with the ftp client from Sergey's inetutils.  I wonder if I
should compile an ftp client myself instead?  Has anyone else seen
this problem, and can you suggest a way out (other then using horrible
dysfunctional WinBlows clients, of course :-)

Best regards,

-- 
Ian Zimmerman
Lightbinders, Inc.
2325 3rd Street #324
San Francisco, California 94107
U.S.A.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -