DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=YqitoYopfOPO6nKbBlwKN66uqbp/QpPFw/n/SUD6prH
	TQfFSh7jy3bcmNCbJpxZI0vMzrF0RdHfB74cPCDp4dtTPyudro24PTIDAXLzZqW8
	rq3NGSQvDLkFL3QTIc675sb2uWeOztmV1APUg6kouZo2IYJEABQPbnW1sfpZVA5I
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <53CF3548.6030206@tlinx.org>
Date: Tue, 22 Jul 2014 21:08:40 -0700
From: Linda Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Caveats for removing /cygdrive prefix?
References: <53CE4D27 DOT 9010900 AT codespunk DOT com>
In-Reply-To: <53CE4D27.9010900@codespunk.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Matt D. wrote:
> I've always used Cygwin's fstab /cygdrive default but I'm growing 
> tired of always typing it out; msys's simple "/a" "/c" "/d" prefix for 
> drive letters always seemed closer to home while on a Windows machine.
>
> The only problem I've encountered is a borked ls display when an 
> actual folder "a", "b", etc., appears in the Cygwin root folder and 
> the inability to enumerate drive with "ls /cygdrive".
>
> Are there any other caveats to consider?
----
    I've had my system set this way for well over 10 years.  Doing it 
any other way
wouldn't be nearly as useful to me.

    If it wasn't for the cygwin bug ignoring MS-mounts and treating them as
symlinks, you could also have cygwin32 and cygwin64 running side-by-side 
with
32-procs calling cygwin32 and 64-bit procs calling cygwin64.

But due to the cygwin treating MS mount/reparse points as symlinks (and not
just MS symlinks), the mounts won't survive an upgrade (i.e. have to 
recreate
them).

    The reason for the cygwin bug was to prevent behaviors present in
cygwin already as well as in linux (cycles in the file system), but I 
get that
that already:


law.Bliss> find / -name testmenow
find: File system loop detected; '/C' is part of the same file system 
loop as '/'.

It doesn't seem to cause a problem with any utils nor does it on linux
which honors the 'mount' flags and allows you to mount files or dirs
elsewhere in your hierarchy (so does windows, but cygwin break that).

Also you may find that many Win-utils accepts "/" as well as "\" --
the underlying OS, NT does, just some Winlib that were crafted to
disable this ability.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple