9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: [9fans] unmount
Date: Mon, 24 Feb 2003 19:51:42 +0000	[thread overview]
Message-ID: <1b3fe87cf5edd5de4fb773acd0a96244@vitanuova.com> (raw)

while we're on the subject of namespaces, it would be lovely to be
able to temporarily put something in the namespace, and then take it
away, without forking the namespace (i.e.  undo an arbitrary mount or
bind request).

i don't know how, though.

perhaps one could give every mount a unique id (visible in
/proc/$pid/ns, and perhaps as a return from mount) that could then be
named in an unmount request.

perhaps /proc/$pid/mnt could enumerate all the "mounted from"
points in the current name space:

	% bind -v -b '#|' /tmp
	543464
	% unmount /proc/$pid/mnt/543464 /dev

just a thought.



             reply	other threads:[~2003-02-24 19:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 19:51 rog [this message]
2003-02-24 20:08 ` rob pike, esq.
2015-12-01  3:24 arisawa
2015-12-01  9:39 ` arisawa
2015-12-01 17:06 ` Charles Forsyth

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=1b3fe87cf5edd5de4fb773acd0a96244@vitanuova.com \
    --to=rog@vitanuova.com \
    --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).