This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: bash: difference between //c/ and c:/
- To: cygwin <cygwin at cygwin dot com>
- Subject: Re: bash: difference between //c/ and c:/
- From: Corinna Vinschen <cygwin at cygwin dot com>
- Date: Thu, 15 Mar 2001 19:17:09 +0100
- References: <71171405@toto.iv> <15024.62910.662998.88543@jupiter.akutech-local.de>
On Thu, Mar 15, 2001 at 06:02:54PM +0100, Ralf Fassel wrote:
> * Corinna Vinschen
> | Bash is a UNIX shell. Why not using UNIX paths?
>
> Because we use non-Cygwin programs which don't grok /cygwin pathnames.
> Unfortunately, there is a world besides cygwin.
>
> $ cl t.c -o t
> Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 11.00.7022 for 80x86
> ...
> $ ./t /cygdrive/c/autoexec.bat c:/autoexec.bat
> 1: /cygdrive/c/autoexec.bat: fopen failed
> 2: c:/autoexec.bat: fopen succeeded
>
> | Actually not C:/ is deprictaed but //c! The syntax is ambiguous
> | since that could also address a SMB server. We may decide to
> | eliminate that syntax for local drives completely in the future.
>
> Uh, please don't... :-/ Aren't single letter SMB servers rather rare?
>
> | Use the /cygdrive/c syntax instead.
>
> As I described in another mail, this currently breaks my openssh
> installation, so I stick with //c for now.
Why don't you mount your drives and drop the double slash:
mount -f -s -b C: /c
...
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple