From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Couple of Venti questions
Date: Sun, 27 Mar 2005 12:13:02 -0500 [thread overview]
Message-ID: <ee9e417a05032709136defe54c@mail.gmail.com> (raw)
In-Reply-To: <20050327152052.GC22577@smp500.sitetronics.com>
> Well, actually, there's only one question. I'm wondering if it's
> possible to, instead of configuring Venti to take snapshots of
> entire filesystems at a given interval, configure Venti to take
> a snapshot of a single file and only when you tell it to
> yourself.
No, there isn't. Full file system snapshots are not that
expensive. Let yourself go. If you're worried about particular
huge churn, you could chmod +t (or maybe +T, I forget)
certain things to exclude them from the periodic snapshots.
For example chmod +t $home/tmp, or if you're super aggressive,
chmod +t /386/bin /386/lib.
You'll find that once you've had daily snapshots of everything
around for a while you'll never want to go back to having to
explicitly ask for something to be snapshotted.
But see also vac(1).
Russ
prev parent reply other threads:[~2005-03-27 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 15:20 Devon H. O'Dell
2005-03-27 17:13 ` Russ Cox [this message]
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=ee9e417a05032709136defe54c@mail.gmail.com \
--to=russcox@gmail.com \
--cc=9fans@cse.psu.edu \
/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).