From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] kfs and cwfs comparison
Date: Sun, 24 Apr 2011 07:13:59 -0400 [thread overview]
Message-ID: <63d88c3d38162974e6c68ebc13f86f8d@ladd.quanstro.net> (raw)
In-Reply-To: <201104240344.27289.errno@cox.net>
> Question, regarding kfs and cwfs: why choose one over the other?
>
> In other words, what points are important to be aware of when deciding
> which of the two are more appropriate for any given new
> installation/deployment? (let's assume that kfs's 28-character filename
> limit isn't an issue, and that there's no concern for supporting legacy fs
> formats)
>
> Additionally, under what conditions/circumstances might either of those
> two be a more suitable/optimal alternative to, say, fossil?
in my experience, both are more robust in the face of unexpected outages
than fossil.
ken fs/cwfs also provides a dump file system (that is, history) without the
need to run venti.
- erik
next prev parent reply other threads:[~2011-04-24 11:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 10:44 errno
2011-04-24 11:13 ` erik quanstrom [this message]
2011-04-24 11:31 ` errno
2011-04-24 14:10 ` David du Colombier
2011-04-24 15:52 ` erik quanstrom
2011-04-24 15:01 ` Steve Simon
2011-04-24 16:10 ` erik quanstrom
2011-04-24 17:36 ` John Floren
2011-04-24 18:03 ` erik quanstrom
2011-04-24 18:56 ` errno
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=63d88c3d38162974e6c68ebc13f86f8d@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.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).