This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: FS layout issues for v1.1 (eg., /bin and /usr/bin)
- To: "Parker, Ron" <rdparker at butlermfg dot org>
- Subject: Re: FS layout issues for v1.1 (eg., /bin and /usr/bin)
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Tue, 29 Feb 2000 13:34:24 -0500
- Cc: "'cygwin-developers at sourceware dot cygnus dot com'" <cygwin-developers at sourceware dot cygnus dot com>, Egor Duda <deo at logos-m dot ru>
- References: <200002291744.JAA18000@cygnus.com>
- Reply-To: cygwin-developers at sourceware dot cygnus dot com
On Tue, Feb 29, 2000 at 11:43:21AM -0600, Parker, Ron wrote:
>
>-----Original Message-----
>From: Egor Duda [mailto:deo@logos-m.ru]
>Sent: Tuesday, February 29, 2000 1:37 AM
>To: cygwin-developers@sourceware.cygnus.com; Mumit Khan
>Subject: Re: FS layout issues for v1.1 (eg., /bin and /usr/bin)
>
><snip>
>
>> MK> The question is -- how do we make /bin and /usr/bin the same?
>
>> MK> a. Symlinks: cygcheck could check and report this if the user somehow
>> MK> deletes it.
>
>> the only drawback i see is performance going down. we all know that
>> symlinks are rather slow.
>
>What would be the side effects of using matched mounts instead of symlinks?
>
>For, example
> mount -b C:\\cygwin /
> mkdir /usr/bin
> mount -b C:\\bin /usr/bin
>
>or,
> mount -b C:\\cygwin /
> mkdir /bin
> mount -b C:\\usr\\bin /bin
There are no side effects. The biggest problem is "user confusion". It's pretty
obvious what's going on when you do a "ls -l /usr". It's not so obvious when
you are using mounts.
Someone mentioned that symlinks might be slow on network drives. I'm not worried
about that. The problem is that symlinks *may not work* on network drives.
That may blow the symlink idea out of the water, unfortunately.
cgf