On Thu Mar 29 07:05:00 EDT 2007, [EMAIL PROTECTED] wrote:
> From time to time i get back to plan9 and starting fiddling with it,
> now i might found a reason to make it useful where i work..
> If i understand correctly, venti uses fossil as a write buffer for
> today's modifications, and if i want to access data in previous week's
> state, then files are served by venti.
fossil is not a proper cache. fossil uses venti for archival snapshots
(this would be called a dump in ken's fileserver). fossil is useful
without venti. in fact, i think fossil without venti is better for a
combined auth/cpu/fileserver as fossil is much kinder if you turn
the machine off or hang it.
the downside is if you do have a venti,
> Or (as i read in plan 9 intro pdf): "In some cases, a single file server
> may provide more than one file tree.
this means you can connect to different file trees. so i can connect
to kibbiee like this
; srv il!kibbiee kibbiee
then mount the other filesystem, dump or main respectively
; mount /srv/kibbiee /n/other other
; mount /srv/kibbiee /n/dump dump
; mount /srv/kibbiee /n/kibbiee
the 3d argument to mount is the "attach point". the server is free
to choose a default, which for ken's fs is "main" and for fossil is "active".
fossilcons(8) explains how to make different fossil filesystems. typically
all you need is one.
>
> What id like to know is:
> can i simply use fossil
yes. you don't get archival snapshots without venti. you could
use vac to roll your own.
> or do i need fossil+venti?
> can backup period (currently daily) be set to stg. else? Like every two
> hours?
you'd have to do this manually. you get one archive per day.
- erik
