Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<00ef01c17bac$3ed9b150$4a49689e@MagusLaptop>
From:	"Collin Grady" <cgrady AT willamette DOT edu>
To:	"James Roberts-Thomson" <James DOT Roberts-Thomson AT Optimation DOT co DOT nz>,
	<cygwin AT cygwin DOT com>
References:	<1465A9A047FF514D95217900DBB83954022165 AT wlgexch01 DOT optimation DOT co DOT nz>
Subject:	Re: Failure in cygwin-1.3.6-1 with remapped "cygdrive"
Date:	Sun, 2 Dec 2001 19:40:23 -0800
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

     You could map /cygdrive to something shorter, like /mnt
     I think it worked before because you couldn't cd into /cygdrive in
previous versions, whereas you can now, since 1.3.6-1 treats /cygdrive as a
directory now.  Not treating it as a directory in earlier versions is what
allowed your mapping it to / to work, if I understand it correctly.
     -Collin Grady

I never met a piece of chocolate I didn't like.

----- Original Message -----
From: "James Roberts-Thomson" <James DOT Roberts-Thomson AT Optimation DOT co DOT nz>
To: <cygwin AT cygwin DOT com>
Sent: Sunday, December 02, 2001 7:34 PM
Subject: Failure in cygwin-1.3.6-1 with remapped "cygdrive"


> Regretfully, cygwin1.dll v1.3.6-1 doesn't work correctly on my systems (I
> use more than one).
>
> Attempting to start a bash shell displays "bash.exe: warning: could not
find
> /tmp, please create!".  The environment seems completely trashed - no
cygwin
> executables or bash builtins work correctly (i.e. mount, ls, cd, etc).
>
> I have determined that this is most likely because I have used the "mount
> -c" option to re-map "cygdrive" as "/" - this meant I could go to specific
> drives as "/c", "/d", etc - perhaps not the best way to implement this,
but
> it did work well until now.
>
> I have verified this by using "mount -c /cygdrive" from a C:\ prompt to
> reset back to original behaviour, and bash now starts and works correctly.
>
> Should this be considered a bug in v1.3.6-1, or a "feature", or simply
> listed as a caveat (i.e. DON'T map /cygdrive to /).  I could create
> individual mappings (/c, /d, etc) for the drives I use most frequently -
but
> to be honest, mapping cygdrive as / was good as my drive letters on the
LAN
> are very flexible and dynamic.
>
> Thanks for the good work so far, however!
>
> James Roberts-Thomson
>
>
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
>


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -