From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Venti r/o directory
Date: Tue, 9 Feb 2010 14:53:03 -0500 [thread overview]
Message-ID: <437751e28b3db632b6cea684c49a8a0b@brasstown.quanstro.net> (raw)
In-Reply-To: <4B71B95B.8050707@maht0x0r.net>
> But when I unvac the resulting score with 9p9 [sic] on Debian it segfaults
> because 'My Documents' is dr-xr-x-- so unvac creates a read only
> directory and then tries to write into it.
>
[...]
>
> The only general purpose solution I can think of is two passes for unvac
> but that doesn't sound very nice.
wouldn't it suffice to set temporary permissions of 777 and fixup
when leavinging that directory?
> btw. it is a great way to backup. < 1% of CPU while running, which is
> doubly fortunate because vacput doesn't have an option to compare
> against previous backups
so you're completely disk bound? if disk activity on the windows
box is also low, your venti machine must be suffering.
- erik
next prev parent reply other threads:[~2010-02-09 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 19:36 maht
2010-02-09 19:53 ` erik quanstrom [this message]
2010-02-09 20:08 ` maht
2010-02-10 12:55 ` maht
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=437751e28b3db632b6cea684c49a8a0b@brasstown.quanstro.net \
--to=quanstro@quanstro.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).