Date: Thu, 20 Jul 1995 04:32:29 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: bde@zeta.org.au (Bruce Evans) Cc: jkh@time.cdrom.com, current@freefall.cdrom.com Subject: Re: Hmmmm! New error encountered with cpio while building root.flp Message-ID: <199507201132.EAA09014@gndrsh.aac.dev.com> In-Reply-To: <199507201028.UAA21969@godzilla.zeta.org.au> from "Bruce Evans" at Jul 20, 95 08:28:07 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > >> 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. Should that error perhaps be ``inode number would be truncated''??? > >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. Yes I suppose that could be true, I use to start with a system that had 2 iterations of make world run on it before I used that to create a chroot tree which I then ran a 3rd make world in that was the actually production build. Perhaps overkill, but it made darn sure I could say the last release can build the current release and the current release can build itself. I use to have to do all this double build stuff by hand until Poul and Jordan went and automated it for the 2.0 release, and then heavly improved that for the 2.0.5 release. [I may have release numbers off here, I didn't look at src/release until the 2.0.5 release when I started to run it every 24 hours for Jordan to make sure we didn't do anything that made it fall over] My concern is that you may have problems building the chroot tree using 2.2 as the release tools need some fixing, but that fixing may break the release tools when they run inside the 2.1 tree, and as you point out the opposite may be true as well :-(. > >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. Okay, good. So the problems will all happen during the builds which means worse case we end up missing bits, and in the case above all the bits :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199507201132.EAA09014>