9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: james palmer <9front@9front.org>
Subject: Re: [9front] Venti in 9front
Date: Tue, 7 Sep 2021 08:04:04 +0000 (UTC)	[thread overview]
Message-ID: <08533c32-116e-48f2-8bc4-3954f6721dc8@sirjofri.de> (raw)
In-Reply-To: <C0656D52-8E0E-4022-B6F5-B2E4B80615E5@biobuf.link>

07.09.2021 01:43:45 james palmer <james@biobuf.link>:

> Quoth <sirjofri+ml-9front@sirjofri.de>:
>> I'd be interested in patching cwfs so I can have an alternative layout
>> without a worm partition, but dump with a venti. I believe this is
>> possible. What do people who touched cwfs (and/or venti) source code
>> think about that?
> i dont know if you really need to patch cwfs, i ran cwfs with no dump 
> and backed up to venti with a cron job for a while.

That's also a solution. I assume you used vac? Did you change the 9fs 
script to fit the venti situation (9fs dump)?

> if you do feel like patching libventi is used by both venti clients and 
> the server so you should be able to use that in cfws. i don't know 
> about the on-disk format though.

Absolutely. I didn't look at cwfs dump code yet, but I can imagine it's 
just a matter of injecting libventi code there, together with some config 

> though if you want a venti backed fs, you could always just import 
> fossil :P perhaps from ants?

That's exactly what I do _not_ want :). The reason is that fossil is not 
part of 9front and future changes might break compatibility and/or make 
the system unstable. I believe cwfs is becoming more stable, especially 
considering nobody wants to patch fossil code (which is the reason why 
it's removed). Therefore, a venti-driven backup solution for the standard 
pretty-stable supported cwfs is more tempting than installing fossil.

It would be great if you could share more details (and scripts?) for your 
venti backup solution with cwfs nodump.


  reply	other threads:[~2021-09-07  8:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-04 11:41 sirjofri
2021-09-05  4:51 ` unobe
2021-09-05 10:43   ` Stuart Morrow
2021-09-06  4:23     ` unobe
2021-09-06  7:45       ` sirjofri
2021-09-06 23:43         ` james palmer
2021-09-07  8:04           ` sirjofri [this message]
2021-09-07 17:59             ` james palmer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=08533c32-116e-48f2-8bc4-3954f6721dc8@sirjofri.de \
    --to=sirjofri+ml-9front@sirjofri.de \
    --cc=9front@9front.org \


* 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).