From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <56605425-FCCD-417D-A188-3A1F5CD30D2A@quintile.net> References: <56605425-FCCD-417D-A188-3A1F5CD30D2A@quintile.net> From: Ole-Hjalmar Kristensen Date: Wed, 13 Dec 2017 08:29:57 +0100 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="94eb2c19b976078b6f056033bc22" Subject: Re: [9fans] A potentially useful venti client Topicbox-Message-UUID: c6e8c38c-ead9-11e9-9d60-3106f5b1d025 --94eb2c19b976078b6f056033bc22 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable No need to be sorry. I've been looking at the code now and then, but haven't really got the hang of the difference between the vac and venti formats. On Wed, Dec 13, 2017 at 1:03 AM, Steve Simon wrote: > grief, sorry. > > what can i say, too old, too many kids. important stuff gets pushed out o= f > my brain (against my will) to make room for the lyrics of =E2=80=9CLet it= go=E2=80=9D. > > > On 12 Dec 2017, at 21:40, Ole-Hjalmar Kristensen < > ole.hjalmar.kristensen@gmail.com> wrote: > > Yes, I know. I was thinking along the same lines a while ago, we even > discussed this here on this mailing list. I did some digging, and I found > this interesting comment in vac/file.c: > > /* > > * > * Fossil generates slightly different vac files, due to a now > * impossible-to-change bug, which contain a VtEntry > * for just one venti file, that itself contains the expected > * three directory entries. Sigh. > */ > VacFile* > _vacfileroot(VacFs *fs, VtFile *r) > > Ole-Hj > > On Tue, Dec 12, 2017 at 9:38 PM, Steve Simon wrote: > >> The best solution (imho) for what you want to do is the feature I never >> added. >> >> It would be great if you could vac up your linux fs and then just cut an= d >> past the >> vac score into fossil's console with a command like this: >> >> main import -v 7478923893289ef928932a9888c98b2333 /active/usr/ole/linux >> >> the alternative is a 1.6Tb fossil. >> >> -Steve >> >> > --94eb2c19b976078b6f056033bc22 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
No need to be sorry. I've been looking at the code now= and then, but haven't really got the hang of the difference between th= e vac and venti formats.

On Wed, Dec 13, 2017 at 1:03 AM, Steve Simon <steve@quin= tile.net> wrote:
grief, sorry.=C2=A0

what= can i say, too old, too many kids. important stuff gets pushed out of my b= rain (against my will)= =C2=A0to make room for the lyrics of =E2=80=9CLet it go=E2=80=9D.


On 12 Dec 2017, at 21:40,= Ole-Hjalmar Kristensen <ole.hjalmar.kristensen@gmail.com> wrote:=

Yes, I know. I was thinking along the same lines a wh= ile ago, we even discussed this here on this mailing list. I did some diggi= ng, and I found this interesting comment in vac/file.c:

/*
=C2=A0<snip>
=C2=A0*
=C2=A0* Fossil generates = slightly different vac files, due to a now
=C2=A0* impossible-to-change = bug, which contain a VtEntry
=C2=A0* for just one venti file, that itsel= f contains the expected
=C2=A0* three directory entries.=C2=A0 Sigh.
= =C2=A0*/
VacFile*
_vacfileroot(VacFs *fs, VtFile *r)

Ole= -Hj

On T= ue, Dec 12, 2017 at 9:38 PM, Steve Simon <steve@quintile.net> wrote:
The best solution (imho) for wh= at you want to do is the feature I never added.

It would be great if you could vac up your linux fs and then just cut and p= ast the
vac score into fossil's console with a command like this:

main import -v 7478923893289ef928932a9888c98b2333 /active/usr/ole/linu= x

the alternative is a 1.6Tb fossil.

-Steve



--94eb2c19b976078b6f056033bc22--