From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] union directories
Date: Fri, 28 Feb 2003 14:58:28 -0800 [thread overview]
Message-ID: <8d3497c42250108c201dc829c7769f20@collyer.net> (raw)
In-Reply-To: <1f229e0b2b861ffeebd62738b74c9cd3@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
`bind -c 9 9' remains useful, however, to retain createability of the
directory in which a union mount is then performed:
; cd /tmp
; mkdir x
; bind -a /sys/lib x
; ns|tail -4
mount -b '#s/rio.geoff.73279' /dev
bind /tmp/x /tmp/x
bind -a /sys/lib /tmp/x
cd /tmp
; >x/FOO
x/FOO: rc: can't open: mounted directory forbids creation
versus
; unmount x
; bind -c x x
; bind -a /sys/lib x
; ns|tail -4
mount -b '#s/rio.geoff.73279' /dev
bind -c /tmp/x /tmp/x
bind -a /sys/lib /tmp/x
cd /tmp
; >x/FOO
; unmount x; ls x
x/FOO
[-- Attachment #2: Type: message/rfc822, Size: 1984 bytes --]
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] union directories
Date: Fri, 28 Feb 2003 13:56:18 -0500
Message-ID: <1f229e0b2b861ffeebd62738b74c9cd3@plan9.bell-labs.com>
You used to need to say "bind foo foo" to set up a mount
point for future union mounts. (A long time ago.)
Now the system inserts these for you, though they're
still visible in the /proc/$pid/ns file (and thus the
output of ns).
Bind -bc 9 9 is a different thing, and almost
certainly not what is wanted, especially in the
example given -- it doesn't have any effect except
to make everything appear twice in the directory.
(Bind -bc 9 9 is like:
bind 9 9
bind -bc 9 9
hence everything appears twice.)
Russ
next prev parent reply other threads:[~2003-02-28 22:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 18:52 Joel Salomon
2003-02-28 18:56 ` Russ Cox
2003-02-28 21:16 ` Jack Johnson
2003-02-28 22:58 ` Geoff Collyer [this message]
2003-02-28 23:19 ` Jack Johnson
2003-02-28 23:59 ` Geoff Collyer
-- strict thread matches above, loose matches on Subject: below --
2003-03-03 20:45 Keith Nash
2003-03-03 20:51 ` Russ Cox
2003-03-03 20:00 Keith Nash
2003-03-03 20:05 ` Russ Cox
2003-03-03 18:58 rog
2003-03-03 23:17 ` anyrhine
2003-03-03 13:18 rog
2003-03-03 17:40 ` Ronald G. Minnich
2003-03-03 18:05 ` Russ Cox
2003-03-03 18:09 ` Ronald G. Minnich
2003-03-03 18:16 ` Russ Cox
2003-02-15 19:37 [9fans] presentation preparation Scott Schwartz
2003-02-15 19:48 ` andrey mirtchovski
2003-02-27 9:35 ` Ralph Corderoy
2003-02-28 18:44 ` [9fans] union directories Jack Johnson
2003-02-28 18:53 ` Russ Cox
2003-03-04 9:44 ` Adrian Tritschler
2001-03-23 13:30 G. David Butler
2001-03-23 13:08 rog
2001-03-26 8:44 ` Douglas A. Gwyn
2001-03-22 3:28 rob pike
2001-03-23 10:06 ` Douglas A. Gwyn
2001-03-22 2:57 Gorka Guardiola Muzquiz
2001-03-22 2:46 Gorka Guardiola Muzquiz
2001-03-22 2:42 Gorka Guardiola Muzquiz
2001-03-22 2:37 Russ Cox
2001-03-22 2:02 Russ Cox
2001-03-22 1:56 Gorka Guardiola Muzquiz
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=8d3497c42250108c201dc829c7769f20@collyer.net \
--to=geoff@collyer.net \
--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).