---------- Forwarded message ----------
Date: Tue, 28 Mar 2000 15:45:29 +0100
From: [EMAIL PROTECTED]
To: Tom Oehser <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [tomsrtbt] Best use of pax/tar/cpio for cloning?
Tom,
I've checked the code. Support for SPARSE filesystems is already in the
code and should work. It was there from the beginning before I added new
functionality. So I have to assume it works, but I don't have a SPARSE
filesystem to test against.
Regards
Ian.
Tom Oehser <[EMAIL PROTECTED]>
21/03/00 18:57
To: Jose Marin <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED], Ian Stewartson <[EMAIL PROTECTED]>
Subject: Re: [tomsrtbt] Best use of pax/tar/cpio for cloning?
> OK, my question: what's the best utility to preserve the permissions,
> UIDs, GIDs, sparse files,...? Woud GNU tar cut it? I was thinking
about
> something like this:
Any pax or tar or cpio should do OK for UIDs, GIDs, permissions, devices,
etc.
Tomsrtbt does not include gnu-tar, it has a pax = tar = cpio.
Normal (non-gnu) cpio is better than normal (non-gnu) tar, as the tar
standard does not support arbitrary lengths of file names. If you use the
tomsrtbt pax, use either the pax or cpio syntax with the cpio file format.
You can maintain more portability with gnu-cpio than with gnu-tar.
I doubt the tomsrtbt pax/tar/cpio preserves sparseness. You might want to
check and see if there is anything on the system where you care...
> Will something like this work and not affect things like, say, the /dev
> directory, or the lost+found dirs on every partition (I think it won't
but
> wanna make sure).
Gnu tar should work. Gnu cpio should work. I personally think cpio is a
better file format than tar, though I prefer the tar command syntax.
Tomsrtbt tar or cpio or pax will also work well enough, with the exception
of the sparse files issue.
I will copy the pax maintainer re: is there sparse support in the works?
-Tom
---
This email is confidential, and is not intended to have
contractual effect. If you are not an intended recipient,
please contact the sender, and do not read this email,
use it, rely on it or retransmit it. You must ensure that this
email, which may contain attachments, is virus free before
opening it.
www.osi.co.uk
---
