From: Steve Simon <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] A potentially useful venti client
Date: Wed, 13 Dec 2017 00:03:47 +0000 [thread overview]
Message-ID: <56605425-FCCD-417D-A188-3A1F5CD30D2A@quintile.net> (raw)
In-Reply-To: <CAHqDL__3aY03ivjB7jx0U3S6HD7teRFoiVB=SoUH1o_DverYTw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
grief, sorry.
what can i say, too old, too many kids. important stuff gets pushed out of my brain (against my will) to make room for the lyrics of “Let it go”.
> 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:
>
> /*
> <snip>
> *
> * 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 <steve@quintile.net> 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 and 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
>>
>
[-- Attachment #2: Type: text/html, Size: 2056 bytes --]
next prev parent reply other threads:[~2017-12-13 0:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 9:33 Ole-Hjalmar Kristensen
2017-12-12 14:07 ` Steve Simon
2017-12-12 15:45 ` Steven Stallion
2017-12-12 16:11 ` Steve Simon
2017-12-12 16:23 ` Steven Stallion
2017-12-12 18:42 ` Ole-Hjalmar Kristensen
2017-12-12 19:16 ` Steven Stallion
2017-12-12 20:31 ` hiro
2017-12-12 23:36 ` Skip Tavakkolian
2017-12-13 10:17 ` Bakul Shah
2017-12-12 18:33 ` Ole-Hjalmar Kristensen
2017-12-12 19:53 ` Steve Simon
2017-12-12 20:03 ` Steve Simon
2017-12-12 20:07 ` Ole-Hjalmar Kristensen
2017-12-12 20:15 ` Steve Simon
2017-12-12 20:31 ` Ole-Hjalmar Kristensen
2017-12-12 20:38 ` Steve Simon
2017-12-12 21:40 ` Ole-Hjalmar Kristensen
2017-12-13 0:03 ` Steve Simon [this message]
2017-12-13 7:29 ` Ole-Hjalmar Kristensen
2017-12-13 9:44 ` hiro
2017-12-13 11:00 ` Steve Simon
2017-12-13 12:22 ` Richard Miller
2017-12-13 14:13 ` Ole-Hjalmar Kristensen
2017-12-13 13:37 ` Ole-Hjalmar Kristensen
2017-12-12 21:02 ` Steven Stallion
2017-12-12 21:55 ` Ole-Hjalmar Kristensen
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=56605425-FCCD-417D-A188-3A1F5CD30D2A@quintile.net \
--to=steve@quintile.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).