From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Anyone using p9p or Plan 9 venti as a more generic backup system?
Date: Wed, 17 Nov 2010 09:44:27 -0800 [thread overview]
Message-ID: <AANLkTim-VFL=1h8ZjoHcRyqGFXKTVTqbHfMN9TH_NgzS@mail.gmail.com> (raw)
In-Reply-To: <201011171823.27527.dexen.devries@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
On Wed, Nov 17, 2010 at 9:23 AM, dexen deVries <dexen.devries@gmail.com>wrote:
> On Wednesday 17 November 2010 18:14:35 Venkatesh Srinivas wrote:
> > (...)
> > I'd be very careful with vac -m and -a on Unix; both have been at the
> > root of considerable data-loss on a unix venti for me. I'd recommend
> > vac-ing tarballs, rather than using vac's on unix trees directly. But
> > your mileage may vary...
>
>
> could you please elaborate a bit about that data loss?
> traversing symlinks breaks? some files not getting read by vac at all?
>
> (I'm interested in using p9p vac+venti in similar manner, but on Linux w/
> GNU
> stuff)
>
> --
> dexen deVries
>
I could imagine vac/unvac not dealing with resource forks or POSIX extended
attributes and such properly, as well as potentially having difficulty with
symlinks, but having dealt with stuff like that in "xar", I don't think it's
too difficult to address.
I may need to read up on venti and see what sorts of data types it supports.
Might be time to add some extensions?
Dave
>
>
> ``One can't proceed from the informal to the formal by formal means.''
>
>
[-- Attachment #2: Type: text/html, Size: 1765 bytes --]
next prev parent reply other threads:[~2010-11-17 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 16:51 David Leimbach
2010-11-17 17:14 ` Venkatesh Srinivas
2010-11-17 17:23 ` dexen deVries
2010-11-17 17:43 ` Venkatesh Srinivas
2010-11-17 17:44 ` David Leimbach [this message]
2010-11-18 19:40 ` Bakul Shah
2010-11-18 19:44 ` dexen deVries
2010-11-17 17:24 ` David Leimbach
2010-11-22 15:56 ` Latchesar Ionkov
2010-11-22 20:35 ` David Leimbach
2010-11-23 4:21 ` Anthony Sorace
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='AANLkTim-VFL=1h8ZjoHcRyqGFXKTVTqbHfMN9TH_NgzS@mail.gmail.com' \
--to=leimy2k@gmail.com \
--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).