From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] RFNOMNT vs unmount
Date: Sun, 20 Dec 2020 20:49:28 +0100 [thread overview]
Message-ID: <CAFSF3XP1Xf+1SHk+63Fy1oiNky6r_h4TMbnRrYvwQ5xORoZSQQ@mail.gmail.com> (raw)
In-Reply-To: <2B00BA68FFBEF791E1A7F8173F3F4257@eigenstate.org>
On 12/20/20, ori@eigenstate.org <ori@eigenstate.org> wrote:
> 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).
next prev parent reply other threads:[~2020-12-20 19:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 19:22 ori
2020-12-20 19:49 ` hiro [this message]
2020-12-20 20:32 ` Steve Simon
2020-12-20 23:51 ` [9front] " Anthony Martin
2020-12-21 6:25 ` ori
2020-12-21 15:34 ` [9front] " Xiao-Yong Jin
2020-12-20 20:33 ori
2020-12-20 21:39 ` cinap_lenrek
2020-12-20 21:52 ` ori
2020-12-21 18:51 ` magma698hfsp273p9f
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=CAFSF3XP1Xf+1SHk+63Fy1oiNky6r_h4TMbnRrYvwQ5xORoZSQQ@mail.gmail.com \
--to=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).