From: presotto@plan9.bell-labs.com
To: arisawa@ar.aichi-u.ac.jp, 9fans@cse.psu.edu
Subject: Re: [9fans] user none
Date: Sun, 9 Jul 2000 10:55:49 -0400 [thread overview]
Message-ID: <200007091455.KAA13396@cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 172 bytes --]
Off hand, I can't thing of anything that would break. In security,
less priviledge is always better. I'll change it on our syystems
and see if it does break anything.
[-- Attachment #2: Type: message/rfc822, Size: 1524 bytes --]
From: arisawa@ar.aichi-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] user none
Date: Sat, 8 Jul 2000 19:13:29 -0400 (EDT)
Message-ID: <20000708224524.281.qmail@nx.aichi-u.ac.jp>
Hello,
I have a question.
In Plan9, we have a rule: "everyone can become none."
However user none plays important role for Internet service.
What's wrong if we replace the rule by the following ?
"Only host owner can become none."
Thanks,
Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp
next reply other threads:[~2000-07-09 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-09 14:55 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-08 23:13 arisawa
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=200007091455.KAA13396@cse.psu.edu \
--to=presotto@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
--cc=arisawa@ar.aichi-u.ac.jp \
/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).