9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] New plan 9 Installation and File Systems
Date: Mon, 21 Mar 2005 11:38:18 -0500	[thread overview]
Message-ID: <ee9e417a05032108383175d076@mail.gmail.com> (raw)
In-Reply-To: <dbec90a42e78bf4bdf2cb9576a528480@comcast.net>

> I mean have it handle auth/cpu/fs), Ken's fs was designed to be run on
> a machine that acts as a file server and nothing else, though I'm
> guessing now that nothing would prevent me from using Ken's on a
> multipurpose machine.  In any case, you're right the hardware stuff is

The worm file system still requires its own dedicated machine,
so unless you're using something like VMware, the machine
won't be very multipurpose.

> In Plan 9 you can use fossil, kfs or Ken's fs, which do you choose and
> why?

Fossil is the successor to the WORM file server.
Unless you're using a real WORM jukebox, I don't see
any good reason to install the old file server.  Using Venti
on a disk instead of pretending it is a fake WORM takes
up significantly less space and lets you use vac, vacfs, etc.
as well as the file server.

I know people had stability concerns for a while, but fossil
seems solid now.  I've only seen one reported bug in the
last few months or more, and it was fixed within a day.

Fossil also gives you features not available in the WORM file
server, like long file names, the DMTMP bit, file service over TCP,
and temporary snapshots.

Russ


  reply	other threads:[~2005-03-21 16:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-21 15:21 Gregory Pavelcak
2005-03-21 15:40 ` C H Forsyth
2005-03-21 15:58   ` Gregory Pavelcak
2005-03-21 16:38     ` Russ Cox [this message]
2005-03-21 23:29       ` geoff
2005-03-22  2:07       ` Skip Tavakkolian
2005-03-23  4:34         ` Brantley Coile
2005-03-23 11:44           ` vdharani
2005-03-23  3:07       ` Kenji Okamoto
2005-03-23  3:14         ` boyd, rounin
2005-03-23  3:32           ` Kenji Okamoto
2005-03-22  0:59 YAMANASHI Takeshi
2005-03-22 10:23 ` Steve Simon
2005-03-22 11:59 ` kazumi iwane
2005-03-22 12:10   ` Steve Simon
2005-03-22 12:29     ` Steve Simon
2005-03-23  0:42 YAMANASHI Takeshi
2005-03-23  2:36 ` Kenji Okamoto
2005-03-23  2:43 YAMANASHI Takeshi

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=ee9e417a05032108383175d076@mail.gmail.com \
    --to=russcox@gmail.com \
    --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).