From: Gregory Pavelcak <g.pavelcak@comcast.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] New plan 9 Installation and File Systems
Date: Mon, 21 Mar 2005 10:58:11 -0500 [thread overview]
Message-ID: <dbec90a42e78bf4bdf2cb9576a528480@comcast.net> (raw)
In-Reply-To: <85dde4f80df65f2a8903a75ce091ad05@vitanuova.com>
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
OK, thanks. Now we're getting somewhere. I guess I just mention
hardware availability because I got the impression that while you
could run everything from a single PC with fossil (by "run everything"
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
a red herring, so allow me to rephrase a bit more concisely.
In Plan 9 you can use fossil, kfs or Ken's fs, which do you choose and
why?
Greg
[-- Attachment #2: Type: message/rfc822, Size: 2470 bytes --]
From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] New plan 9 Installation and File Systems
Date: Mon, 21 Mar 2005 15:40:54 +0000
Message-ID: <85dde4f80df65f2a8903a75ce091ad05@vitanuova.com>
>>Is fossil/venti the standard now, or if you had enough hardware around
>>to have a dedicated file server, would you use Ken's fs?
i run venti and fossil on dedicated file servers,
so i don't think having hardware (or not) is the key.
next prev parent reply other threads:[~2005-03-21 15:58 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 [this message]
2005-03-21 16:38 ` Russ Cox
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=dbec90a42e78bf4bdf2cb9576a528480@comcast.net \
--to=g.pavelcak@comcast.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).