From: "Scott Prive" <Scott.Prive@storigen.com>
To: "Jan Nieuwenhuizen" <janneke@gnu.org>, <cygwin@cygwin.com>
Subject: RE: paths like //usr/local
Date: Tue, 15 Oct 2002 14:01:00 -0000 [thread overview]
Message-ID: <7BFCE5F1EF28D64198522688F5449D5AD63A44@xchangeserver2.storigen.com> (raw)
FYI: I actually *had* hostnames like "var", "tmp" and so on at one time... :-)
Cygwin maps UNIX/POSIX behavior on top of NT, but NT was designed to be compatible with DOS's *broken* conventions, so NT is half-broken.
Any kind of parsing for mounts like you suggest would probably incur a performance hit, generate limitations, and cause breakage everywhere.
The escaping can be annoying but it's livable IMO. I suggest not to use //, but to use the "proper" path convention -- and escape accordingly. This is more keystrokes and more to remember, but it seems bugfree and 100% consistent. I shudder at the thought of `rm -rf /path` going to an "interpreted" mount point.
Example:
Desired path: \\server\share
Bash: \\\\server\\share
Perl - going THROUGH bash, using system():
\\\\\\\\server\\\\share
Slightly off topic, but standard Bash *does* support hostname completion. You have to configure it -- see standard BASH2 documentation online. I have no idea how well it works with Cygwin and with UNC pathing, but it works on UNIX with automount and ssh.
If nothing, it could be extended by someone for UNC.
-Scott
> -----Original Message-----
> From: Jan Nieuwenhuizen [mailto:janneke@gnu.org]
> Sent: Tuesday, October 15, 2002 4:01 PM
> To: cygwin@cygwin.com
> Subject: Re: paths like //usr/local
>
>
> Christopher Faylor <cygwin@cygwin.com> writes:
>
> > cygwin allows the user to specify paths like: c:\foo\bar
> and c:/foo/bar.
> > Similarly, it allows //foo/bar and \\foo\bar .
>
> > If that doesn't satisfy you then you can go back to the
> "Because we're mean"
> > argument.
>
> I've been hurt by this too, and it makes me think. It would be even
> more satisfactory if some configurable list of 'hosts' would map to
> //localhost/. Hosts with names such as \\bin, \\etc, \\tmp,
> \\usr or \\var come to mind.
>
> Now if such a thing could be implemented without some horrible kludge,
> would that be nice?
>
> Jan.
>
> --
> Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The
> music typesetter
> http://www.xs4all.nl/~jantien | http://www.lilypond.org
>
>
> --
> 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/
next reply other threads:[~2002-10-15 20:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 14:01 Scott Prive [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-15 11:06 Sven Köhler
2002-10-15 11:45 ` cygwin
2002-10-15 12:23 ` Sven Köhler
2002-10-15 12:51 ` Christopher Faylor
2002-10-15 13:25 ` Jan Nieuwenhuizen
2002-10-15 12:58 ` Igor Pechtchanski
2002-10-15 12:59 ` Sven Köhler
2002-10-15 13:00 ` Christopher Faylor
2002-10-16 0:37 ` Sven Köhler
2002-10-16 0:41 ` Sven Köhler
2002-10-15 13:27 ` Sven Köhler
2002-10-15 13:57 ` Shankar Unni
2002-10-15 14:12 ` Shankar Unni
2002-10-16 0:14 ` egor duda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7BFCE5F1EF28D64198522688F5449D5AD63A44@xchangeserver2.storigen.com \
--to=scott.prive@storigen.com \
--cc=cygwin@cygwin.com \
--cc=janneke@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).