Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <1465A9A047FF514D95217900DBB83954022165@wlgexch01.optimation.co.nz> From: James Roberts-Thomson To: "'cygwin AT cygwin DOT com'" Subject: Failure in cygwin-1.3.6-1 with remapped "cygdrive" Date: Mon, 3 Dec 2001 16:34:11 +1300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" 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/