From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bind, ns weirdness
Date: Thu, 6 Mar 2003 17:16:56 -0500 [thread overview]
Message-ID: <38c1a33c1aaf02e7c0c477e50e0bea47@plan9.bell-labs.com> (raw)
In-Reply-To: <20030306215848.25459.qmail@mail.dirac.net>
A process has an underlying idea of what / is, i.e., there is a
up->slash in the Proc structure of the process. In all cases,
this is actually '#/'. Therefore, after your 'unmount /',
an 'ls /' should show:
% ls -l /
d-r-xr-xr-x / 0 presotto presotto 0 Mar 3 11:05 /bin
d-r-xr-xr-x / 0 presotto presotto 0 Mar 3 11:05 /boot
d-r-xr-xr-x / 0 presotto presotto 0 Mar 3 11:05 /dev
d-r-xr-xr-x / 0 presotto presotto 0 Mar 3 11:05 /env
d-r-xr-xr-x / 0 presotto presotto 0 Mar 3 11:05 /fd
d-r-xr-xr-x / 0 presotto presotto 0 Mar 3 11:05 /mnt
d-r-xr-xr-x / 0 presotto presotto 0 Mar 3 11:05 /net
d-r-xr-xr-x / 0 presotto presotto 0 Mar 3 11:05 /net.alt
d-r-xr-xr-x / 0 presotto presotto 0 Mar 3 11:05 /proc
d-r-xr-xr-x / 0 presotto presotto 0 Mar 3 11:05 /root
d-r-xr-xr-x / 0 presotto presotto 0 Mar 3 11:05 /srv
In other words, you can't get rid of the underlying thing
that eveything else is mounted on.
All of the binds that happened onto / are indeed gone.
Therefore, there will be no /386. However, /386/bin was
originally bound onto '#/'/bin which is still in your
namespace. Therefore, it is still visible since it's
still in your namespace.
You're right that ns isn't good about figuring out
how to get back stuff that is no longer reachable.
next prev parent reply other threads:[~2003-03-06 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 21:58 Keith Nash
2003-03-06 22:16 ` David Presotto [this message]
2003-03-06 23:52 Keith Nash
2003-03-06 21:18 ` Russ Cox
2003-03-07 1:32 Joel Salomon
2003-03-06 22:51 ` Russ Cox
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=38c1a33c1aaf02e7c0c477e50e0bea47@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).