From: "Michael Kerrisk" <mtk-manpages@gmx.net>
To: janak@us.ibm.com
Cc: Linus Torvalds <torvalds@osdl.org>,
akpm@osdl.org, ak@muc.de, hch@lst.de, paulus@samba.org,
viro@ftp.linux.org.uk, linux-kernel@vger.kernel.org,
michael.kerrisk@gmx.net
Subject: Re: unhare() interface design questions and man page
Date: Thu, 2 Mar 2006 22:40:46 +0100 (MET) [thread overview]
Message-ID: <27686.1141335646@www004.gmx.net> (raw)
In-Reply-To: Pine.LNX.4.64.0603011959340.22647@g5.osdl.org
Replying to myself...
> > > Do you have any further response on this point?
> > > (There was none in your last message?)
> >
> > I personally don't think it's worth makign UNSHARE_NEWNS just because
> > it's a flag that acts differently from the other CLONE_xxx flags.
>
> See my comments above. (And in case it wasn't clear, I meant
> make a complete set of UNSHARE_* flags that mirror the
> corresponding CLONE_* flags.)
(By the way, I meant that the flag should preferably be called
UNSHARE_NS, not UNSHARE_NEWNS -- as noted in an earlier message
in this thread, CLONE_NEWNS was itself a bad name.)
I had another thought about why using names of the form
UNSHARE_* might be worthwhile. It just might be that in the
future, someone might want to add a flag that has nothing
to do with clone(). I mean some flag that somehow performs
some other modification of the behaviour or unshare(), or
perhaps unshares something that isn't shared/unshared by
clone(). (The first possibility seems more likely than
the second.) In that case, it would make litte sense to
name the flag(s) CLONE_xxx.
Cheers,
Michael
--
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7
Want to help with man page maintenance?
Grab the latest tarball at
ftp://ftp.win.tue.nl/pub/linux-local/manpages/,
read the HOWTOHELP file and grep the source
files for 'FIXME'.
prev parent reply other threads:[~2006-03-02 21:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200602072059.k17KxJUI016348@shell0.pdx.osdl.net>
2006-02-13 22:10 ` unhare() interface design questions and man page Michael Kerrisk
2006-02-14 13:44 ` JANAK DESAI
2006-02-14 18:49 ` Michael Kerrisk
2006-02-14 20:47 ` JANAK DESAI
2006-02-16 5:50 ` Michael Kerrisk
2006-02-19 17:52 ` Janak Desai
2006-03-02 3:31 ` Michael Kerrisk
2006-03-02 4:03 ` Linus Torvalds
2006-03-02 4:48 ` Michael Kerrisk
2006-03-02 21:40 ` Michael Kerrisk [this message]
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=27686.1141335646@www004.gmx.net \
--to=mtk-manpages@gmx.net \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=janak@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.kerrisk@gmx.net \
--cc=paulus@samba.org \
--cc=torvalds@osdl.org \
--cc=viro@ftp.linux.org.uk \
/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).