This is the mail archive of the
mailing list for the Cygwin project.
Re: mount policy
- To: jorg dot schaible at db dot com, cygwin at sourceware dot cygnus dot com
- Subject: Re: mount policy
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Thu, 27 Apr 2000 05:32:25 -0700 (PDT)
- Reply-To: earnie_boyd at yahoo dot com
--- email@example.com wrote:
> after installing the new 1.1.0 version I recognized the binary mounts created
> by setup (or the cygwin1.dll). Up to now I worked with the B20.1 and have
> always used text based mounts and had never problems. What advantage do I
> have in which situation from a binary mount especially because I read other
> users having problems with make, etc. ?
It's about half a dozen in one basket and six in the other. When using a cross
platform network with file servers say in UNIX it's been found it best to be
binary mode. BTW, the CD V1.0 version sets the filesystem to binary mode
processing as well. That doesn't mean that the headaches don't still exist
they do. In binary mode processing, text files must end in \n (UNIX style)
> I also used to have the following mount
> mount $TEMP /tmp
> to sync the temporary directories for Windows and Cygwin. Should I prefer
> here a symbolic link ? Pros & cons for mount vs. ln ?
The symbolic link is slower as Cygwin has more work to do to find the
Earnie Boyd: <mailto:firstname.lastname@example.org>
__Cygwin: POSIX on Windows__
Cygwin Newbies: <http://www.freeyellow.com/members5/gw32/index.html>
__Minimalist GNU for Windows__
Mingw32 List: <http://www.egroups.com/group/mingw32/>
Mingw Home: <http://www.mingw.org/>
Do You Yahoo!?
Talk to your friends online and get email alerts with Yahoo! Messenger.
Want to unsubscribe from this list?
Send a message to email@example.com