From: arisawa@ar.aichi-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] allow
Date: Sat, 15 Jul 2000 12:20:30 -0400 [thread overview]
Message-ID: <20000715155153.242.qmail@nx.aichi-u.ac.jp> (raw)
In-Reply-To: <20000714235707.287.qmail@nx.aichi-u.ac.jp>
Hello,
Rob Pike said:
>Better ideas (short of a superuser) are welcome.
How about is the followings?
1. Storage device is owned by user adm.
2. ^X key (for example) swaps consoles of user adm and hostowner.
3. disk/* can be executed only by user adm.
Please forgive me if I misunderstand what you said.
Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp
next prev parent reply other threads:[~2000-07-15 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-14 14:18 rob pike
2000-07-15 0:25 ` arisawa
2000-07-15 16:20 ` arisawa [this message]
2000-07-14 18:51 pip
2000-07-15 0:18 ` Randolph Fritz
2000-07-16 22:54 presotto
2000-07-17 15:11 ` Douglas A. Gwyn
2000-07-17 21:14 ` arisawa
2005-02-07 7:11 tapique
2005-02-07 7:31 ` Lucio De Re
2005-02-07 10:19 ` Heiko Dudzus
2005-02-07 10:57 ` Lucio De Re
2005-02-07 7:32 ` 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=20000715155153.242.qmail@nx.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9fans@cse.psu.edu \
/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).