From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] fs (was: /rc/bin/C; hey, where'd my consoles go?)
Date: Thu, 16 Jan 2003 08:57:11 +0100 [thread overview]
Message-ID: <32a4a48e4cd12dfabde4b1b4c1bc6ba3@plan9.escet.urjc.es> (raw)
In-Reply-To: <200301152109.h0FL9Ww21064@augusta.math.psu.edu>
Hi,
I just couldn't resist to tell you that here we're now running
using fossil with its partitions (as well as venti's) living in a raid
made with fs(3). It's just great. We're now using a single server
to service both auth and fs. All other machines are really stateless,
which means that there's just a single machine to admin (no consolefs,
more ups time, less points of failure, highly available alan parsons
project mp3 service, ...)
BTW, fossil seems to be quite robust. We had no panics, no aborts. It's
a great file system.
prev parent reply other threads:[~2003-01-16 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 21:09 [9fans] /rc/bin/C; hey, where'd my consoles go? Dan Cross
2003-01-15 22:19 ` Russ Cox
2003-01-15 22:21 ` Dan Cross
2003-01-15 22:26 ` Russ Cox
2003-01-15 22:32 ` Dan Cross
2003-01-16 7:57 ` Fco.J.Ballesteros [this message]
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=32a4a48e4cd12dfabde4b1b4c1bc6ba3@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).