From: Mellman Thomas <Thomas.Mellman@icn.siemens.de>
To: "'Conrad Scott'" <Conrad.Scott@dsl.pipex.com>, cygwin@cygwin.com
Subject: RE: Mount point not visible in ls
Date: Tue, 07 May 2002 07:30:00 -0000 [thread overview]
Message-ID: <BE684E2C997AD51199530002A56B20796C364D@MCHH2A1E> (raw)
>>-----Original Message-----
>>From: Conrad Scott [mailto:Conrad.Scott@dsl.pipex.com]
>>Sent: Monday, May 06, 2002 5:54 PM
>>To: cygwin@cygwin.com
>>Subject: Mount point not visible in ls
>>
>>
>>I'm befuddled and I can't find anything on any of the cygwin
>>mailing lists
>>to help me, so I hope someone here can spot my mistake.
>>
>>My system has been working fine for a long time but just
>>recently I noticed
>>that when I do an `ls' of `/usr' or `echo /usr/*', `/usr/bin'
>>doesn't show
>>up. It's there (if I do, for example, `ls -d /usr/bin') but
>>in some way
>>invisible. Strangely `/usr/lib' is shows up fine, despite its mount
>>information being identical to that for `/usr/bin'
It seems that you're mount point /usr/bin doesn't exist.
That's not a bug, it's a feature.
Try umounting and checking if the mount points exist: likely
/usr/lib does and /usr/bin doesn't, and when you mount them, the
mount for /usr/bin gives you a warning.
--
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-05-07 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 7:30 Mellman Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-07 6:24 Conrad Scott
2002-05-07 8:12 ` Mark Himsley
2002-05-07 13:43 ` Conrad Scott
2002-05-07 13:43 ` Larry Hall (RFK Partners, Inc)
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=BE684E2C997AD51199530002A56B20796C364D@MCHH2A1E \
--to=thomas.mellman@icn.siemens.de \
--cc=Conrad.Scott@dsl.pipex.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).