From: ori@eigenstate.org
To: 23hiro@gmail.com
To: 9front@9front.org
Subject: Re: [9front] RFNOMNT vs unmount
Date: Sun, 20 Dec 2020 12:33:25 -0800 [thread overview]
Message-ID: <E6F92E6F39963B184A4E26417FF72DE4@eigenstate.org> (raw)
Quoth hiro <23hiro@gmail.com>:
> > When trying to restrict a program, it seems common to
> > bind /path/to/resource over /, and then calling
> > 'rfork m'.
>
> really? i have never seen this on plan9. instead it seems like
> something you would do on linux (with chroot).
It's something done by tcp80 and ftpd, for example.
But, you're right: it's not used nearly enough, considering
that the system is designed around namespacing. Probably
because glaring gaps like this make it less useful.
next reply other threads:[~2020-12-20 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 20:33 ori [this message]
2020-12-20 21:39 ` cinap_lenrek
2020-12-20 21:52 ` ori
2020-12-21 18:51 ` magma698hfsp273p9f
-- strict thread matches above, loose matches on Subject: below --
2020-12-21 6:25 [9front] " ori
2020-12-21 15:34 ` [9front] " Xiao-Yong Jin
2020-12-20 19:22 ori
2020-12-20 19:49 ` hiro
2020-12-20 20:32 ` Steve Simon
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=E6F92E6F39963B184A4E26417FF72DE4@eigenstate.org \
--to=ori@eigenstate.org \
--cc=23hiro@gmail.com \
--cc=9front@9front.org \
/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).