9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve Simon <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Migration of vac score to fossil
Date: Thu, 17 Dec 2015 22:13:02 +0000	[thread overview]
Message-ID: <41E0E7F1-C19C-47F1-9326-C2791EA3378B@quintile.net> (raw)
In-Reply-To: <CAHqDL_8599=Hw31VD=civmRguGzJkm+z3tj3xsBXRwJJ8vB5cQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1774 bytes --]

I have long wanted to do this but on the one occasion I tried I got lost inside fossil.

the problem is fossil expects venti to have a hierarchy of the form /active/ and /archive/ where as your venti does not, I guess it has just your home dir.

it is easy to create the required placeholder in a new fossil attached to your fossil. what is missing is a fossil admin command to create a new directory but attach it to a given, existing venti score. if you could do this you could creat an empty fossil attached to your existing fossil and then populate your /archive/yyyy/mmdd/usr/yourname with each venti score you have from your old vac(1)s.

have a look at the fossil create command.

-Steve




> On 17 Dec 2015, at 17:05, Ole-Hjalmar Kristensen <ole.hjalmar.kristensen@gmail.com> wrote:
> 
> I have a file server running Linux at home, with a normal ext3 file system and a plan9port venti. I use this venti for vac backup of both the ext3 file system and other Linux boxes. However, the 2 TB ext3 is running out of space, while the venti is roughly 50% full. I could just buy a bigger disk, of course, but the exit3 itself is mainly an archive (pictures, video, and many years of accumulated documents and software), so I consider switching to a fossil+venti file server instead. The fossil manual says "The score should have been generated by fossil rather than by vac, so that the appropriate snapshot metadata is present". Is there any way of coercing fossil to initialize itself properly from a score produced by vac? I could copy the files from ext3, but would likely run out of space in fossil, which I gather is a bad idea. I run a 9front cwfs auth/cpu/file server, but have no experience with fossil, so any help is welcome.
> 
> 
> 
> 
> 

[-- Attachment #2: Type: text/html, Size: 2748 bytes --]

  reply	other threads:[~2015-12-17 22:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 17:05 Ole-Hjalmar Kristensen
2015-12-17 22:13 ` Steve Simon [this message]
2015-12-20  0:31   ` 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=41E0E7F1-C19C-47F1-9326-C2791EA3378B@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).