From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs hardware configuration
Date: Tue, 3 Dec 2002 09:20:04 +0100 [thread overview]
Message-ID: <a6448fbc6dbeb7a56faa1da1969fe7c9@plan9.escet.urjc.es> (raw)
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
Well, for me, allow is just to too dangerous and we use it just
to upgrade system files including wstats. Before using it you can
always ask who to the file server. And it's sensible to put an
'echo dont forget to disllow' in whatever scripts you use to install
files. If you fell you really need it, I might change that for you
when I get some time, but I'd prefer not to put that into our regular
kernel.
[-- Attachment #2: Type: message/rfc822, Size: 1628 bytes --]
From: Kenji Arisawa <arisawa@ar.aichi-u.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs hardware configuration
Date: Tue, 3 Dec 2002 08:53:26 +0900
Message-ID: <400A7402-0651-11D7-9E52-000393A941BC@ar.aichi-u.ac.jp>
Hello,
>With or without the "allow/disallow" commands? I disabled the former,
>left the latter because I feel more comfortable that way.
I might asking too much...
I would like to have allow command that allows limited users, i.e.,
allow bootes arisawa
Kenji Arisawa
next reply other threads:[~2002-12-03 8:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 8:20 Fco.J.Ballesteros [this message]
2002-12-03 10:37 ` Kenji Arisawa
-- strict thread matches above, loose matches on Subject: below --
2002-12-03 8:34 Fco.J.Ballesteros
2002-12-02 23:40 Geoff Collyer
2002-12-02 14:48 Fco.J.Ballesteros
2002-12-02 14:27 Fco.J.Ballesteros
2002-12-02 14:40 ` Lucio De Re
2002-12-02 8:31 Fco.J.Ballesteros
2002-12-02 14:21 ` Lucio De Re
2002-12-02 23:53 ` Kenji Arisawa
2002-11-30 13:42 Skip Tavakkolian
2002-11-30 16:38 ` Nigel Roles
2002-11-30 18:00 ` William Josephson
2002-11-29 23:57 Skip Tavakkolian
2002-11-29 23:13 Geoff Collyer
2002-11-29 15:53 Skip Tavakkolian
2002-11-30 8:49 ` Nigel Roles
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=a6448fbc6dbeb7a56faa1da1969fe7c9@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).