From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] remove files in /srv
Date: Mon, 31 Jan 2005 20:44:11 -0800 [thread overview]
Message-ID: <15cc4d61b9ec75c7277a026702d4cc8d@collyer.net> (raw)
In-Reply-To: <c1665724bd566308f2588db2f6afafbf@orthanc.cc.titech.ac.jp>
[-- Attachment #1: Type: text/plain, Size: 111 bytes --]
Would it make sense for cs to maintain the posted connections in /srv?
Then only the hostowner has to do so.
[-- Attachment #2: Type: message/rfc822, Size: 3124 bytes --]
From: YAMANASHI Takeshi <9.nashi@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] remove files in /srv
Date: Tue, 1 Feb 2005 13:05:59 +0900
Message-ID: <c1665724bd566308f2588db2f6afafbf@orthanc.cc.titech.ac.jp>
> This won't work well. 9fs alice creates /srv/alice as the user
> who runs it, but if the connection is lost and someone else
> runs 9fs alice, then they need permission to remove it and
> replace it.
They can post a new connection under another name like
/srv/alice.username, can't they?
There are many other important services now in /srv to trust users.
I'm concerned for /srv/^(fossil fscons cs dns factotum) especially.
# boot is excluded because of the special treatment
--
next prev parent reply other threads:[~2005-02-01 4:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 4:05 YAMANASHI Takeshi
2005-02-01 4:44 ` geoff [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-01 3:48 YAMANASHI Takeshi
2005-02-01 4:06 ` arisawa
2005-02-01 4:33 ` Russ Cox
2005-02-01 20:31 ` rog
2005-02-02 23:22 ` Bruce Ellis
2005-02-02 23:57 ` Charles Forsyth
2005-02-01 1:11 YAMANASHI Takeshi
2005-02-01 3:21 ` arisawa
2005-02-01 3:56 ` Russ Cox
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=15cc4d61b9ec75c7277a026702d4cc8d@collyer.net \
--to=geoff@collyer.net \
--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).