From: "Roman V. Shaposhnik" <rvs@sun.com>
To: erik quanstrom <quanstro@coraid.com>
Cc: 9fans@9fans.net
Subject: Re: [9fans] several things
Date: Sat, 18 Oct 2008 00:26:18 -0700 [thread overview]
Message-ID: <1224314778.32175.28.camel@goose.sun.com> (raw)
In-Reply-To: <64debd1118fe0541e4b377bfbb18b2a2@coraid.com>
On Wed, 2008-10-15 at 08:17 -0400, erik quanstrom wrote:
> > > ; mntgen a
> > > ; bind /env a/env
> > > ; bind /bin a/bin
> > > ; bind /proc a/proc
> > > ; bind a /
> > > ; ns
> > >
> > > consider it a security feature.
> >
> > Be it as it may, I still can't quite follow why *manual* pruning
> > of the entries from the namespace would be forbidden. unmount(2)
> > takes two strings as arguments, right? It doesn't even need an fd.
>
> because they're not visible. you have to access
> it in order to unmount it.
I see what you meant now. For some reason, I constantly assume
that namespace is sort of a substitution table that helps you
walk(5) across the bind/mount points. But it is not. Is there
a simple reason for mandating access to the target of the bind?
Or here's an easier way to ask the same: is there a simple reason
for
$ bind /foo /really/nested/bar
always triggering walks into /foo and /really/nested/bar and not
allowing for "lazy evaluation"?
Thanks,
Roman.
next prev parent reply other threads:[~2008-10-18 7:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 21:35 Rudolf Sykora
2008-10-13 22:35 ` erik quanstrom
2008-10-14 8:10 ` Rudolf Sykora
2008-10-14 9:30 ` Steve Simon
2008-10-14 12:22 ` Yaroslav
2008-10-14 13:15 ` Charles Forsyth
2008-10-14 21:44 ` Derek Fawcus
2008-10-14 22:28 ` Charles Forsyth
2008-10-15 9:42 ` Roman V. Shaposhnik
2008-10-15 12:17 ` erik quanstrom
2008-10-18 7:26 ` Roman V. Shaposhnik [this message]
2008-10-20 14:09 ` Yaroslav
2008-10-20 17:21 ` Roman V. Shaposhnik
2008-10-13 22:51 ` Pietro Gagliardi
2008-10-14 3:07 erik quanstrom
2008-10-14 13:03 erik quanstrom
2008-10-14 14:07 ` Kernel Panic
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=1224314778.32175.28.camel@goose.sun.com \
--to=rvs@sun.com \
--cc=9fans@9fans.net \
--cc=quanstro@coraid.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 NNTP newsgroup(s).