From: Richard Foulk <richard@skydive1.com>
To: cygwin@cygwin.com
Subject: Re: mount never fails ... sorta
Date: Sun, 11 Jun 2006 23:22:00 -0000 [thread overview]
Message-ID: <200606112215.k5BMFOW7015470@sd.skydive1.com> (raw)
> Richard Foulk wrote:
> > Give mount(1) nonexistent hosts or directories and it will complain,
> > but it still populates the mount table as if it succeeded.
> >
> > It also always returns zero, for success or failure.
>
> Cygwin's mount is a different bird than on Unix. It really is just a mapping
> table of POSIX names to DOS or UNC-style paths. It is not required that the
> POSIX path exist for things to work. But since most people coming from a UNIX
> background expect that it does and it certainly helps things like shell
> path completion if the paths do already exist, you get a warning to let you
> know about this difference.
>
I guess I should have said mount's behavior is wrong and broken.
It knows when there's an error it just does the wrong things.
1. mount reports the error to stderr, but not via the return code.
2. mount knows about the error but signals success anyway -- by
listing a (non-existent) mount within the mount table.
Sure Cygwin's mount is different than Unix's. That's what Cygwin is all
about, hiding those differences. Cygwin's mount fails at that.
Registering a mount that doesn't exist is quite broken.
Richard
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2006-06-11 22:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 23:22 Richard Foulk [this message]
2006-06-12 0:41 ` Larry Hall (Cygwin)
-- strict thread matches above, loose matches on Subject: below --
2006-06-11 13:57 Richard Foulk
2006-06-11 18:04 ` Larry Hall (Cygwin)
2006-06-11 19:31 ` Christopher Faylor
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=200606112215.k5BMFOW7015470@sd.skydive1.com \
--to=richard@skydive1.com \
--cc=cygwin@cygwin.com \
/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).