This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: file-system layout in b20.2+ [Re: yikes, what are these?]
- To: "Cygwin@Sourceware. Cygnus. Com" <cygwin@sourceware.cygnus.com>
- Subject: Re: file-system layout in b20.2+ [Re: yikes, what are these?]
- From: Mumit Khan <khan@xraylith.wisc.EDU>
- Date: Thu, 17 Jun 1999 16:21:49 -0500
"Robert Campbell" <campbell@calgary.paradigmgeo.com> writes:
>
> I Disagree (in part). I would like to see Cygwin installed to
> /cygwin/<version>
> but then have the installer create the appropriate symbolic links or mount
> points to /usr,/bin,/etc et-al such that /etc is actually a (mount point or
> symbolic link) to /cygwin/<version>/etc.
Could you please elaborate as why you prefer this approach? I don't like
multiple symbolic links when a cleanly (single) rooted system is viable
and available for free.
> I would also like to see the
> installer automatically mount / to C:\
Please, no. This is simply a bad idea no matter how you look at it.
> This would provide a unix friendly envionment for compiling and installing
> things, as you mentioned above, but would leave / as C:\ which IMHO is a
> logical way of doing things.
Why is 'C:\' naturally '/'? I don't follow. 'C:\' may be more natural to
Windows32, but has nothing to do with Cygwin, which will translate the
paths appropriate before calling win32 API and interfacing with the
system.
> As far as changing to another version is concerned, instead of one or two
> registry entries to modify, you would need a number of them, but this could
> still be handled by a simple program, etc.
I can do this with just one registry key that the pathname lookup code
uses. If I had some free time, I could almost get the current snapshot
to do this, but since Chris is already working on this, I'll just wait
and get it for free ;-)
Thanks for your comments on this.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com