From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] group ownership for shared devices
Date: Mon, 9 Nov 2009 23:24:47 -0700 [thread overview]
Message-ID: <alpine.BSF.2.00.0911092318070.42237@legolas.yyc.orthanc.ca> (raw)
In-Reply-To: <dd6fe68a0911092200j33c60239s577a336a5dd0ce11@mail.gmail.com>
> or you could write a custom file server
> with its own group list, like consolefs has.
This seems to make the most sense. And it makes it simple to implement
(configurable) exclusive open semantics for devices that need it.
--lyndon
next prev parent reply other threads:[~2009-11-10 6:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 5:44 Lyndon Nerenberg
2009-11-10 6:00 ` Russ Cox
2009-11-10 6:24 ` Lyndon Nerenberg [this message]
2009-11-10 7:20 ` Lyndon Nerenberg
2009-11-10 13:22 José Brandão
[not found] <<a4d96da30911100522w825d264v56bf72fd3f99385c@mail.gmail.com>
2009-11-10 13:58 ` erik quanstrom
2009-11-10 15:27 José Brandão
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=alpine.BSF.2.00.0911092318070.42237@legolas.yyc.orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@9fans.net \
/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).