From owner-freebsd-current Thu Jul 20 03:32:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id DAA02360 for current-outgoing; Thu, 20 Jul 1995 03:32:08 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id DAA02337 for ; Thu, 20 Jul 1995 03:31:47 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id UAA21969; Thu, 20 Jul 1995 20:28:07 +1000 Date: Thu, 20 Jul 1995 20:28:07 +1000 From: Bruce Evans Message-Id: <199507201028.UAA21969@godzilla.zeta.org.au> To: jkh@time.cdrom.com, rgrimes@gndrsh.aac.dev.com Subject: Re: Hmmmm! New error encountered with cpio while building root.flp Cc: current@freefall.cdrom.com Sender: current-owner@FreeBSD.org Precedence: bulk >> cpio: stand/date not dumped: minor number would be truncated >> cpio: stand/dd not dumped: minor number would be truncated >Looks like Bruces changes to cpio to skip dumping dev nodes that have >high values is causing some problems :-(. These changes should be in 2.1 (I submitted them very late for 2.0.5). Apparently 2.2 isn't used enough for them to be tested enough. To see the bug, try `cd somedir; /bin/ls | cpio -o | cpio -it'. This works here for somedir=/bin but fails for somedir=/usr/src/bin/cat. I think this has something to do with /bin being on a smaller file system. >Looks like we are going to have to be _very_ carefull that we build 2.1R >on a 2.1R system or we may get some really bizzare problems :-(. >And you may very well want to build your 2.2 snaps on a 2.0.5R system >for similiar reasons, until 2.1R can be rolled :-(. 2.0.5R cpio should That would be another way to get a system that can't build itself. >properly read 2.2 cpio files, if it does not we have a bigger problem >than I thought :-(. There is no problem reading. cpio now refuses to copyout files that it can't handle. Bruce