From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Namespace inheritance between processes
Date: Sat, 21 May 2016 23:14:20 -0700 [thread overview]
Message-ID: <cdf28091b8147cd4e6608c143ecac78b@lilly.quanstro.net> (raw)
In-Reply-To: <d6ae2485b0a77c30504133351ee5cbeb@9netics.com>
> > Also, a totally random question: It seems like poor ergonomics that
> > one must create empty directories in order to serve as mount points.
> > Why not just allow mounting to names that don't exist yet?
>
> mntgen(4)
linux has the same restriction, and no mntgen. :-)
- erik
prev parent reply other threads:[~2016-05-22 6:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 7:26 Casey Rodarmor
2016-05-21 7:37 ` Casey Rodarmor
2016-05-21 8:49 ` Skip Tavakkolian
2016-05-21 10:01 ` Anthony Martin
2016-05-21 12:06 ` Anthony Martin
2016-05-22 3:01 ` Casey Rodarmor
2016-05-22 5:28 ` Skip Tavakkolian
2016-05-22 6:14 ` erik quanstrom [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=cdf28091b8147cd4e6608c143ecac78b@lilly.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).