9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] Pitch for devskel
Date: Mon, 6 Jun 2022 09:31:59 -0600	[thread overview]
Message-ID: <bc05a9e2-400f-7c2b-93b4-3484f7f6b473@posixcafe.org> (raw)
In-Reply-To: <D3FCC338E819E63FBE74309787B11EA6@eigenstate.org>

On 6/6/22 09:24, ori@eigenstate.org wrote:
> Quoth Jacob Moody <moody@mail.posixcafe.org>:
>> You _can_ just bind things in to your namespace,
>> and if you did you just wouldn't need auth/box.
>> The point of auth/box is take potentially deeply
>> nested/relative paths and to mimic that hierarchy
>> the the new root. Due to the restriction of devskel
>> to only permit one skeleton per attach. Mimicking some
>> hierarchies can be tedious. This removes that tedium.
> I'm not disagreeing with that; I'm wondering if we can
> drop the device munging part of it, and instead fix
> references to '#'-devs throughout the tree.
Yeah I perfectly content just blocking all devices
unless explicitly stated otherwise(through -e flag).
And yeah, there likely will need to be some code
that directly references devices through '#' in the
tree that we need to clean up.

I will clean up the device inference parts of this
code and rework how mount permissions are specified.


      reply	other threads:[~2022-06-06 15:34 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
2022-06-06 15:08       ` Jacob Moody
2022-06-06 15:24         ` ori
2022-06-06 15:31           ` Jacob Moody [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:

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

  git send-email \
    --in-reply-to=bc05a9e2-400f-7c2b-93b4-3484f7f6b473@posixcafe.org \
    --to=moody@mail.posixcafe.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).