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:34:21 +0100 [thread overview]
Message-ID: <ae6d528fae04aa749f7a7914ca7e718f@plan9.escet.urjc.es> (raw)
When I wrote:
> Our local fs is now the one distributed
I tried to say just that what we're running now is the file server
code as distributed (with no further changes). Since it now includes
the changes to support our disks, we have no reason to run a different one.
Excuse me in case what I wrote could also mean something
different.
next reply other threads:[~2002-12-03 8:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 8:34 Fco.J.Ballesteros [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-03 8:20 Fco.J.Ballesteros
2002-12-03 10:37 ` Kenji Arisawa
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=ae6d528fae04aa749f7a7914ca7e718f@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).