From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] fossil?
Date: Fri, 26 Mar 2021 12:45:56 +0100 [thread overview]
Message-ID: <CAFSF3XPMYQp8DQRywuOa4Ax2VSVY_smnqzx4zgcSOhfnNCDMqg@mail.gmail.com> (raw)
In-Reply-To: <08B2BC7C-F72C-453C-AA68-A80D21A66A06@quintile.net>
mycroftiv has fixes for fossil/venti that also work on 9front, it's
just that nobody has stepped up to provide this in mainline 9front or
support it (and accept the responsibility).
i prefer this over dumping it in and then generating all kinds of bug
reports from users.
even having 2 default filesystems is one too many IMO and adding a
third option just makes it worse. having more options is not always
better, especially not with something so centrally important as your
central file server.
On 3/26/21, Steve Simon <steve@quintile.net> wrote:
>
> I have run fossil 24x7 since 2004,
> i can attest to it being solid and reliable.
>
> there was a bug in the snapshot code (not dumps but ephemeral snapshots) but
> this was fixed years ago.
>
> there is an issue where it can fail badly if the file system fills up - but
> this has never happened to me as i run fossil with venti.
>
> i would say fossil+venti is can be slow, but large ram caches help
> considerably.
>
> i have never tried hjfs or cwfs, i can only say i am happy with fossil and
> venti.
>
> -Steve
>
>
>
next prev parent reply other threads:[~2021-03-26 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 23:31 kokamoto
2021-03-26 3:34 ` Noam Preil
2021-03-26 5:14 ` Kurt H Maier
2021-03-26 7:31 ` Steve Simon
2021-03-26 11:45 ` hiro [this message]
2021-03-26 15:29 ` Noam Preil
2021-03-27 10:38 ` Steve Simon
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=CAFSF3XPMYQp8DQRywuOa4Ax2VSVY_smnqzx4zgcSOhfnNCDMqg@mail.gmail.com \
--to=23hiro@gmail.com \
--cc=9front@9front.org \
/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).