9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: quanstro@quanstro.net (erik quanstrom)
Subject: [9fans] Encrypting file systems
Date: Thu, 31 Mar 2011 08:01:16 -0400	[thread overview]
Message-ID: <aa3d230ec51ddc23f3b0f1c8f678f807@ladd.quanstro.net> (raw)

> I thought I read somewhere that kfs was deprecated.  In one of the man
> pages?  On the wiki?  I don't recall.  It was about the old kfs file
> system being replaced by fossil...or something like that.

ken's file server (aka the plan 9 file server) is not kfs.  kfs is a stripped
down, stand-alone version with no history.  see /sys/doc/fs/fs.ps for
a somewhat terse overview of ken's file server.

i run several instances.  the big one at coraid handles a moderately-sized
company on relatively modest hardware.  it can push 100s of mb/s.
yet it lacks mp and 64-bit support.

in theory venti+fossil replaces ken's fs.  but in practice, there seem to
be lingering questions about fossil.

my personal opinion is that ken's fs does it's job very well, and competing
by reducing the amount of storage used (such as fossl+venti do in this
role) is hard to do today, especially if the result is more complicated.

clearly, to gain traction, you'll need a compelling story.  say, a properly
distrbuted file server.

- erik



             reply	other threads:[~2011-03-31 12:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 12:01 erik quanstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-29 23:24 [9fans] encrypting " erik quanstrom
2011-03-29 14:42 [9fans] Encrypting " smiley at zenzebra.mv.com
2011-03-29 14:54 ` Jacob Todd
2011-03-30 17:19   ` smiley at zenzebra.mv.com
2011-03-30 17:25     ` erik quanstrom
2011-03-31  0:12       ` smiley at zenzebra.mv.com
2011-03-31 11:02         ` Steve Simon
2011-03-31 11:55           ` erik quanstrom
2011-03-30 20:22     ` Jacob Todd
2011-03-29 15:06 ` ron minnich
2011-03-30 20:47 ` Mechiel Lukkien

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=aa3d230ec51ddc23f3b0f1c8f678f807@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    /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).