From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] [reminder] pointer to Plan 9 FAQ
Date: Mon, 17 Sep 2001 23:42:39 -0700 [thread overview]
Message-ID: <20010918064242.2F38A199E8@mail.cse.psu.edu> (raw)
The standalone file server gets more use at the Labs than kfs does.
However, I've used kfs over the years without incident. kfs gets used
in laptops quite a bit, so that they can run standalone. Others have
experienced kfs corruption (notably on the standalone systems at the
Labs) but I don't know if those were due to kfs bugs or hardware
failures. I believe that kfs bugs have been fixed over the years.
It's really better to use a standalone file server for performance
too. kfs is slower and less versatile. That doesn't mean that you
have to spend a fortune. Now that there's support for IDE disks and
mirroring in the file server, one can buy a suitable system for under
$1,000 and prices continue to drop. Don't skimp on RAM; a big RAM
cache helps performance. Half a gigabyte costs about $80. Processor
speed, on the other hand, isn't terribly important.
Ultimately I don't trust magnetic media. Tapes rot, stretch, jam and
magnetic fields decay, and disks crash. Moving cross-country has
killed Seagate SCSI disks. Only optical media are worth the effort it
takes to record backups on them.
next reply other threads:[~2001-09-18 6:42 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 6:42 geoff [this message]
2001-09-18 10:29 ` Boyd Roberts
2001-09-18 20:41 ` Richard
-- strict thread matches above, loose matches on Subject: below --
2003-11-21 4:42 Andrey S. Kukhar
2003-09-18 4:05 Andrey S. Kukhar
2003-07-15 4:01 steve-9fans
2003-06-15 4:01 steve-9fans
2003-05-15 4:01 Steve Kotsopoulos
2003-04-15 4:01 Steve Kotsopoulos
2003-03-15 5:01 Steve Kotsopoulos
2003-02-15 5:01 Steve Kotsopoulos
2003-01-15 5:01 Steve Kotsopoulos
2002-12-15 5:01 Steve Kotsopoulos
2002-11-15 5:01 Steve Kotsopoulos
2002-10-15 4:01 Steve Kotsopoulos
2002-09-15 4:01 Steve Kotsopoulos
2002-08-15 4:01 Steve Kotsopoulos
2002-08-15 5:26 ` Lucio De Re
2002-07-15 4:01 Steve Kotsopoulos
2002-06-15 4:01 Steve Kotsopoulos
2002-05-15 4:01 Steve Kotsopoulos
2002-04-15 4:01 Steve Kotsopoulos
2002-03-15 5:01 Steve Kotsopoulos
2002-02-15 5:01 Steve Kotsopoulos
2002-01-15 5:01 Steve Kotsopoulos
2001-12-15 5:01 Steve Kotsopoulos
2001-11-15 5:01 Steve Kotsopoulos
2001-10-15 4:01 Steve Kotsopoulos
2001-09-20 22:03 Russ Cox
2001-09-21 8:42 ` Anthony Mandic
2001-09-21 15:49 ` Dan Cross
2001-09-20 15:24 anothy
2001-09-20 14:43 erik quanstrom
2001-09-20 8:49 geoff
2001-09-18 14:50 jmk
2001-09-18 12:41 Boyd Roberts
2001-09-18 8:26 Richard Miller
2001-09-16 22:48 jmk
2001-09-18 4:33 ` Richard
2001-09-15 4:01 Steve Kotsopoulos
2001-09-16 21:28 ` Richard
2001-08-15 4:01 Steve Kotsopoulos
2001-07-15 4:01 Steve Kotsopoulos
2001-06-15 4:01 Steve Kotsopoulos
2001-06-18 9:16 ` cLIeNUX user
2001-05-15 4:01 Steve Kotsopoulos
2001-04-15 4:01 Steve Kotsopoulos
2001-03-15 5:01 Steve Kotsopoulos
2001-03-15 5:30 ` Jim Choate
2001-02-15 5:01 Steve Kotsopoulos
2001-01-15 13:28 Richard Miller
2001-01-15 5:01 Steve Kotsopoulos
2001-01-15 10:01 ` cLIeNUX user
2000-12-15 5:01 Steve Kotsopoulos
2000-11-15 5:01 Steve Kotsopoulos
2000-10-15 4:01 Steve Kotsopoulos
2000-09-15 4:01 Steve Kotsopoulos
2000-08-15 4:01 Steve Kotsopoulos
2000-07-15 4:01 Steve Kotsopoulos
2000-06-15 4:01 Steve Kotsopoulos
2000-05-15 4:01 Steve
2000-04-15 4:01 Steve
2000-03-15 5:01 Steve
2000-02-15 5:01 Steve
2000-01-15 5:01 Steve
1999-12-15 5:01 Steve
1999-11-15 5:01 Steve
1999-10-15 4:01 Steve
1999-09-15 4:01 Steve
1999-08-15 4:01 Steve
1999-07-15 4:01 Steve
1999-06-15 4:01 Steve
1999-05-15 4:01 Steve
1999-04-15 4:01 Steve
1999-03-15 5:01 Steve
1999-02-15 5:01 Steve
1999-01-15 5:01 Steve
1998-12-15 5:01 Steve
1998-11-15 5:01 Steve
1998-05-15 4:01 Steve
1998-03-15 5:01 Steve
1998-02-15 5:01 Steve
1998-01-15 5:01 Steve
1997-12-15 5:01 Steve
1997-11-15 5:01 Steve
1997-10-15 4:01 Steve
1997-09-15 4:01 Steve
1997-08-15 4:01 Steve
1997-07-15 4:01 Steve
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=20010918064242.2F38A199E8@mail.cse.psu.edu \
--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).