9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Pitch for devskel
Date: Mon, 06 Jun 2022 10:40:28 -0400	[thread overview]
Message-ID: <08B58C43C8BB3ABC8B89ADE9C37573F1@eigenstate.org> (raw)
In-Reply-To: <d93b5e5c-fd7c-846f-3e53-ea5b465a8e1a@posixcafe.org>

Quoth Jacob Moody <moody@mail.posixcafe.org>:
> +	case 'M':
> +		mountok = 1;
> +		snprint(devs, sizeof devs, "%s%c", devs, 'M');
> +		break;

I think this should be allowed by default -- I we can
already allow programs to mess with their namespace
as they see fit using bind and unmount, and I don't
think mount should be any more privileged.

Actually, thinking about this more, I think that all
devices should be dropped by default (bind them in
if you care), and mounts should be allowed.

mimic seems like it'd be largely unneeded, since
you can already bind things into your ns before

  reply	other threads:[~2022-06-06 14:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05  0:57 Jacob Moody
2022-06-06  3:16 ` Jacob Moody
2022-06-06  6:41   ` Jacob Moody
2022-06-06 14:40     ` ori [this message]
2022-06-06 15:08       ` Jacob Moody
2022-06-06 15:24         ` ori
2022-06-06 15:31           ` Jacob Moody

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=08B58C43C8BB3ABC8B89ADE9C37573F1@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \


* 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).