From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Fossil robustness
Date: Tue, 20 Apr 2010 12:05:37 -0400 [thread overview]
Message-ID: <0A0FF5E0-7544-49CE-A119-50F406D70FA7@9srv.net> (raw)
In-Reply-To: <4BCD85B5.1060404@tecmav.com>
[-- Attachment #1: Type: text/plain, Size: 357 bytes --]
Both fossil and kfs seem like the wrong tool for your job. In
addition to the robustness questions, they (especially fossil)
include features you're not going to get anything out of in
your environment. If you use something like paqfs(4) or
sacfs(4) (not sure which is more appropriate) you'll get
safer operation and have a smaller system as well.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2010-04-20 16:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 10:45 Adriano Verardo
2010-04-20 11:12 ` maht
2010-04-20 11:29 ` Adriano Verardo
2010-04-20 12:32 ` erik quanstrom
2010-04-20 12:50 ` Adriano Verardo
2010-04-21 4:49 ` [9fans] updating 9vx root EBo
2010-04-21 5:18 ` Fernan Bolando
2010-04-21 5:29 ` EBo
2010-04-21 5:45 ` Fernan Bolando
2010-04-21 6:31 ` yy
2010-04-21 11:58 ` EBo
2010-04-21 12:20 ` EBo
2010-04-20 11:13 ` [9fans] Fossil robustness John Soros
2010-04-20 11:39 ` Adriano Verardo
2010-04-20 12:18 ` John Soros
2010-04-20 12:37 ` erik quanstrom
2010-04-20 16:05 ` Anthony Sorace [this message]
2010-04-20 17:55 ` [9fans] 9vx crashing EBo
2010-04-20 18:05 ` erik quanstrom
2010-04-20 18:13 ` EBo
2010-04-21 8:39 ` Balwinder S Dheeman
2010-04-21 8:56 ` ron minnich
2010-04-21 11:22 ` erik quanstrom
2010-04-21 12:27 ` Balwinder S Dheeman
2010-04-21 13:05 ` EBo
2010-04-21 13:10 ` ron minnich
2010-04-21 13:17 ` EBo
[not found] ` <twig.1271856045.77201@swcp.com>
2010-04-21 13:22 ` EBo
2010-04-26 4:18 ` lucio
2010-04-26 4:27 ` EBo
2010-04-26 4:30 ` lucio
2010-04-26 10:13 ` EBo
2010-04-26 12:30 ` lucio
2010-04-26 15:15 ` Balwinder S Dheeman
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=0A0FF5E0-7544-49CE-A119-50F406D70FA7@9srv.net \
--to=a@9srv.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).