bug-cpio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-cpio] Absolute filenames in copy-in


From: J Martin Rushton
Subject: [Bug-cpio] Absolute filenames in copy-in
Date: Mon, 29 Feb 2016 23:35:48 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The documentation for cpio is currently seriously misleading,
particularly for those who have used the utility for many years.
Specifically in both the info page tutorial and in the bottom part of
the man page there is the claim:

- -------%<-------------
If you are  dealing  with  an archived directory tree, you need to use
the `-d' option to create directories as necessary, something like:

       % cpio -idv < tree.cpio

This  will  take  the  contents  of  the  archive tree.cpio and
extract it to the current directory.
- -------%<-------------

Please note the final few words.  For someone used to older version
(for instance that supplied with CentOS 5), this claim is correct.  A
dump of a filesystem will have the leading "/"s stripped off and the
tree built in the current directory.  Later versions do not do this
and I note that --absolute-filenames is marked as default.

I had retrieved a number of cpio from tape where each was a complete
dump of a root filesystem.  On one machine I used the above command to
expand the tree based on the current filesystem (as I have done many
times before) and it worked.  To speed things up I repeated the
command on one of the other nodes and it overwrote my CentOS 6.7
system with a CentOS 5.11 system.  As you can imagine the result was
an unbootable system.

Is it possible to update the documentation to warn about this change
in behaviour?  Quite apart from those updating from earlier versions,
the current documentation is internally inconsistent.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJW1NXUAAoJEAF3yXsqtyBlZtUP/R3Vu5kODgyZh0yTTzqWcmR6
hv5G3kUrrKahFBeTEMiySio1AUK1Lv2nI3s7N7WVEknLmqeU8JlzPoi2KhuvH/bI
mp+0upy3O5i32QPxAQADAhZLxTzjgXLTo95NUFovkBmGO6r54llY2LS3KBwK2NiV
DmxL+LjuQHvLe2Uly0VqpHiKywA2Z7jUEqA8cGT/I5H+V4sr15BrewWnJvtKhs51
NbOz+v9qILjFdu9pr/rRqerujLDFdONwgo/PrLHqozPXm7g5wsvyh/VjkPlR5wI8
Mn4ihafU7TvoL1CAHK3ie0mG9d1lzkdrFt88J63moKyubxm2Z77ljRkV+qTF1YdC
CBK1tql+s9X+w5n7ekr0dR8aVKQtghzIO/Exlnx8sanTuQyX7y69mL4zHXHPvfzj
XfwFqPjjuJVcceXDS4TQd4QM6m9778e0igvtf2IsNMXhkSHNafiNa3k4aVgWNoco
x5loHsTKlBKmhYllUYVWv3jdItWN2jPVR5k12y4bSTjefK/xjvLzySlWCM/Bk6rS
CmWW7MubjqPEruSaTw/ZwQsIFR1up+oR/WlL1BFXoqhFqyCfYo0E0JnlRHxV1L/2
hdnwf2KjIlMnMlUpAj+X3mJOB9wpJighbDeAjozFUxIujfRMQdwYRv6QRdPw90fJ
FAvv19EdFMOs81fGepic
=WR5m
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]