From owner-freebsd-questions Tue Jun 5 18:16:54 2001 Delivered-To: freebsd-questions@freebsd.org Received: from buffnet4.buffnet.net (buffnet4.buffnet.net [205.246.19.13]) by hub.freebsd.org (Postfix) with ESMTP id D173C37B401 for ; Tue, 5 Jun 2001 18:16:50 -0700 (PDT) (envelope-from shovey@buffnet.net) Received: from buffnet11.buffnet.net (buffnet11.buffnet.net [205.246.19.55]) by buffnet4.buffnet.net (8.9.3/8.8.7) with ESMTP id VAA73147; Tue, 5 Jun 2001 21:18:02 -0400 (EDT) (envelope-from shovey@buffnet.net) Date: Tue, 5 Jun 2001 21:15:35 -0400 (EDT) From: Stephen Hovey To: "T. William Wells" Cc: questions@FreeBSD.ORG Subject: Re: cpio weirdness In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Um no - even static system binaries would get chewed up. Unless you mean 1 changed file pukes em all up. 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