From: rsc@plan9.bell-labs.com rsc@plan9.bell-labs.com
Subject: [9fans] The user 'none'
Date: Wed, 1 Oct 1997 10:25:18 -0400 [thread overview]
Message-ID: <19971001142518.cKsPGhJQvGrhxPhFvbvgAEmZiDMORqV-_Rc7cFvvmiE@z> (raw)
none has to be able to read a lot of files.
your algorithm doesn't (i don't think) handle
things like stuff up for ftp in /usr/none, which
is most likely owned by others.
none also has to be able to read the kernels from
/$objtype directories so that tftp can serve them.
i don't see how none ever gets access to files
it doesn't own.
russ
next reply other threads:[~1997-10-01 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-01 14:25 rsc [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-10-01 15:33 G.David
1997-10-01 13:36 G.David
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=19971001142518.cKsPGhJQvGrhxPhFvbvgAEmZiDMORqV-_Rc7cFvvmiE@z \
--to=rsc@plan9.bell-labs.com \
/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).