From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] Unmount to remove sharp devices.
Date: Mon, 23 May 2022 11:37:20 -0600 [thread overview]
Message-ID: <d0c23d89-d009-c7ce-8dec-6cf5249ee728@posixcafe.org> (raw)
In-Reply-To: <360D31817B067471414B1C6D6DF6DF92@felloff.net>
On 5/23/22 11:06, cinap_lenrek@felloff.net wrote:
> try to preserve that the ns file looks like shell script.
>
> avoid "eject", as that is already a existing command that does
> something completely different.
>
> i dont like "permit" as it is too generic and not clear what it
> operates on.
>
> in any case, think of these operations as something that we should
> also provide a shell wrapper for and it lives in the /bin namespace.
>
> maybe should be a single command limilar to chmod/chgrp but operating
> on the kernel device map?
>
> like:
>
> devmask -X # "eject" X device
> devmask ABCDEF # set ABCDEF as allowed
>
> any better ideas?
This all makes sense.
There was some followup discussion for this on irc that I want to
make sure is captured here:
The command written to /dev/drivers will change to be one of:
chdev DEVS
chdev -DEVS
with them acting like the current 'permit' and 'eject' commands respectively.
This will be given a matching chdev(1) rc script, and the ns file command
will be updated to match the chdev(1) interface.
thanks,
moody
next prev parent reply other threads:[~2022-05-23 17:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 14:09 Jacob Moody
2022-05-04 15:05 ` ori
2022-05-04 15:31 ` ori
2022-05-04 16:15 ` Stanley Lieber
2022-05-04 17:41 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-05-04 17:55 ` Jacob Moody
2022-05-05 1:59 ` Alex Musolino
2022-05-05 16:07 ` Jacob Moody
2022-05-08 2:55 ` Jacob Moody
2022-05-11 14:47 ` Jacob Moody
2022-05-11 16:11 ` Stanley Lieber
2022-05-12 4:29 ` Jacob Moody
2022-05-12 3:18 ` ori
2022-05-12 5:10 ` Jacob Moody
2022-05-12 14:21 ` ori
2022-05-23 5:42 ` Jacob Moody
2022-05-23 17:06 ` cinap_lenrek
2022-05-23 17:37 ` Jacob Moody [this message]
2022-05-25 19:03 ` Jacob Moody
2022-05-25 20:53 ` hiro
2022-05-25 21:20 ` Jacob Moody
2022-05-26 5:55 ` Jacob Moody
2022-05-26 23:36 ` unobe
2022-05-27 0:33 ` Jacob Moody
2022-05-27 3:25 ` unobe
2022-05-26 3:13 ` ori
2022-05-27 1:11 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-05-27 2:25 ` Frank D. Engel, Jr.
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=d0c23d89-d009-c7ce-8dec-6cf5249ee728@posixcafe.org \
--to=moody@mail.posixcafe.org \
--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).