On Tue, 21 Mar 2000, Tom Oehser wrote:
> 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.
Thanks for such a quick answer, Tom.
I gather that for best results, it will be better to use _exactly_ the
same program for both creating and unpacking the archive; and if that's
not possible, then cpio is more likely to succeed, rigth? I say this
because my reference workstation is running Debian, which has GNU-tar,
GNU-cpio, and OpenBSD's pax (written by Keith Muller). So if I want to
_create_ the archive with one of these tools and then _unpack_ it with
tomsrtbt, which one would you recommend? Pax in both cases I guess?
The other option of course is to install tomsrtbt's version of pax on the
reference machine, but then I'd need to install libc5 as well, no?
> 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...
I was just being a bit paranoid here; the machine is a more-or-less stock
Debian installation, and I don't have many db, dbm, or any other files
suspect of having huge holes, I think. Old versions of the SAG
(http://www.linuxdoc.org/LDP/sag/index.html) had a program to check the
filesystem for holes; I guess that a quick check with "df" on the cloned
workstation will also reveal quickly if there are any problems.
However it will be always nice to have a sparse-aware pax in tomsrtbt...
Thanks,
Jose
--
Jose L Marin [EMAIL PROTECTED]
Dept of Mathematics [EMAIL PROTECTED]
Heriot-Watt University
Edinburgh EH14 4AS, U.K.
Phone: +44 131 451 3893
Fax: +44 131 451 3249
