Date: Wed, 6 Jun 2001 09:22:03 -0400 (EDT) From: Stephen Hovey <shovey@buffnet.net> To: "T. William Wells" <bill@twwells.com> Cc: questions@FreeBSD.ORG Subject: Re: cpio weirdness Message-ID: <Pine.BSF.4.05.10106060921500.397-100000@buffnet11.buffnet.net> In-Reply-To: <E157Sbu-000IH0-00@twwells.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ill stick with pax - its bad enough gettin beeped outta bed! :) On Tue, 5 Jun 2001, T. William Wells wrote: > > Um no - even static system binaries would get chewed up. Unless you mean > > 1 changed file pukes em all up. > > That's exactly what I mean. > > If you're doing cpio, make sure the files involved are not > changing. This includes cpio -p, too. > > > On Tue, 5 Jun 2001, T. William Wells wrote: > > > > I use pax with its defaults and avoid cpio - cpio tends to restore oddly, > > > > like a counter can go off, puttin the end of some files at the top of > > > > other files etc. > > > > > > This is a long-standing problem with cpio. It occurs when the > > > length of a file changes during a cpio run. cpio does work reliably > > > for static files. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.10106060921500.397-100000>