From: L Anderson <lowella@mvseac.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: 1.1.7:mount and ls problem
Date: Tue, 23 Jan 2001 23:55:00 -0000 [thread overview]
Message-ID: <3A6E8A4D.30461468@mvseac.com> (raw)
In-Reply-To: <3A6E3D52.A697CA49@yahoo.com>
Hi Earnie,
Thanks for your reply. I have commented below:
Earnie Boyd wrote:
>
> L Anderson wrote:
>
> > Hi,
> >
> > Being new to Cygwin, I searched the faq and mail archives but could find
> > no answer to my question. An answer would be appreciated.
> >
> > I'm running Win98 and Cygwin 1.1.7.
> >
> > I have drives ... e:, f:, g: ... on win98. I installed cygwin on g:. I
> > fire up cygwin and do:
> > cd /
> > mkdir e
> > mount e: /e
> > All is well -- e shows up in both an ls ( as e) and mount (as e: /e).
> >
> > Now I do:
> > mount f: /f
> > I get the error:
> > mount: warning - /f does not exist
> > but mount shows
> > f: f/ . . .
> > and ls doesn't show f.
>
> Note: it says warning, it doesn't say error. The non-list would be the
> reason for the warning. IMO, it's probably time to make it an error.
>
Ah! Since it says "warning", the "principle of least astonishment"
should not have been violated and therefore, the software should have
acted consistent with my first example, i.e., have done a "mkdir f"
before doing the "mount f: f/"?
At this point, I don't know what you mean by "non-list", so I can't
comment.
Based on the "side effects" of the command sequence, I agree. The
software should have "done it right" or only issued an error message
that said, effectively, "Hey dude, create the damn directory before you
do a mount! Don't leave it up to me!" :-)
> >
> >
> > If I do an ls f, all the files under f:'s root are listed.
>
> >
> > If I do mkdir f, I get:
> > mkdir: cannot make directory `f': File exists
> >
>
> Yes, another reason for the warning. You can either umount /f and then do
> the mkdir /f and mount f:/ /f or you can mkdir /cygdrive/c/cygwin/f
> assuming / is pointed at c:/cygwin
>
I figured this out but it still doesn't answer why the directory for f
(mount point) looks like any other directory but doesn't show up in an
"ls" in the root?
> >
> > So where is f hiding except in the mount table?
> >
>
> The mount table, in the windows registry.
>
This confirms what I expected but why doesn't "f" show up in an "ls" in
the root (/)?
> >
> > Why does f seem to work like any other directory (I can cd to it or its
> > subdirs and ls their contents) but not show up in an ls at the root?
> >
> > Is this a bug or a feature?
> >
>
> It's a feature with old history.
>
Sounds like the code needs a good "slap side da head"! Unfortunately,
I'm not there yet. Is it a problem with "mount", "ls", "cygwinxxx.dll",
or ...?
Thanks for your help!
Lowell Anderson
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2001-01-23 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 16:47 L Anderson
2001-01-23 17:35 ` Larry Hall (RFK Partners, Inc)
[not found] ` <3A6E67E5.CD2C0CF7@serv.net>
2001-01-24 7:27 ` Larry Hall (RFK Partners, Inc)
2001-01-24 8:57 ` Ehud Karni
2001-01-24 9:26 ` Larry Hall (RFK Partners, Inc)
2001-01-24 10:46 ` Earnie Boyd
2001-01-24 11:17 ` Larry Hall (RFK Partners, Inc)
2001-01-24 12:28 ` Christopher Faylor
2001-01-23 18:26 ` Earnie Boyd
2001-01-23 23:55 ` L Anderson [this message]
2001-01-24 6:16 ` Earnie Boyd
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=3A6E8A4D.30461468@mvseac.com \
--to=lowella@mvseac.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).