From: Charles Forsyth <forsyth@terzarima.net>
To: bruce.ellis@gmail.com, 9fans@cse.psu.edu
Subject: Re: [9fans] remove files in /srv
Date: Wed, 2 Feb 2005 23:57:17 +0000 [thread overview]
Message-ID: <30ca86da2ca3ed36cef431bf41d55a88@terzarima.net> (raw)
In-Reply-To: <775b8d1905020215226123a9c7@mail.gmail.com>
>>(the #s in VN inferno is different).
no it's not!
>>if a user binds '#s' he gets a new empty one. a named srv, e.g.
>>#sauth, is shared and a rebind is possible. permissions and
>>lots of details are handled differently.
in fact, i was going to post something almost word-for-word!
next prev parent reply other threads:[~2005-02-02 23:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 3:48 YAMANASHI Takeshi
2005-02-01 4:06 ` arisawa
2005-02-01 4:33 ` Russ Cox
2005-02-01 4:49 ` [9fans] allocb question Tim Newsham
2005-02-01 20:31 ` [9fans] remove files in /srv rog
2005-02-02 23:22 ` Bruce Ellis
2005-02-02 23:57 ` Charles Forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-01 4:05 YAMANASHI Takeshi
2005-02-01 4:44 ` geoff
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=30ca86da2ca3ed36cef431bf41d55a88@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
--cc=bruce.ellis@gmail.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).