This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
File name syntax (WAS: RE: FW: Can not config sshd)
- To: cygwin <cygwin at sourceware dot cygnus dot com>
- Subject: File name syntax (WAS: RE: FW: Can not config sshd)
- From: "Parker, Ron" <rdparker at butlermfg dot com>
- Date: Fri, 26 May 2000 12:00:51 -0500
> No, bash defaults HOME to / and then that get's prepended to
> the path name
> after it resolves the tilde character ~ sor ~/myfile bcomes
> //myfile. Now the
> problem with //myfile is that // is translated to \\ and
> \\myfile as a server
> doesn't exist. The time it takes to eventually time out is
> directly related to
> the number of domains your associated with * the timeout
> period * the number of
> retries. This is the reason we now have /cygdrive instead of
> using // to
> denote an unmounted device/directory.
Which makes me wonder would a patch to cygwin be welcome that did the
following?
* Make multiple introductory slashes on a path behave as a single
introductory slash
* Make paths that begin with name: and contain no backslashes behave as a
network path
In other words, "///myfile" would translate to "/myfile" and
"machine:dir/file" or "machine:/dir/file" would map to the Windows path
\\machine\dir\file.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com