Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!think.com!ames!haven.umd.edu!darwin.sura.net!uvaarpa!cv3.cv.nrao.edu!laphroaig!cflatter From: cflatter@nrao.edu (Chris Flatters) Newsgroups: comp.unix.bsd Subject: Re: Sorry, everyone, but I'm cpio clueless... Message-ID: <1992Jul17.180345.1296@nrao.edu> Date: 17 Jul 92 18:03:45 GMT Article-I.D.: nrao.1992Jul17.180345.1296 References: <1992Jul17.160256.4518@news.iastate.edu> Sender: news@nrao.edu Reply-To: cflatter@nrao.edu Organization: NRAO Lines: 30 In article 4518@news.iastate.edu, musik@iastate.edu () writes: >Evidently the distribution of 386bsd 0.1 is cpio'd... >The bindist directory contains a slew of files named >bin01.00 thru bin01.56 and the MANIFEST. >The INSTALL.NOTES say that this is ten floppies... >Do I just copy this stuff to floppies and then use >the install procedures outlined? Or... do I need >to do something cpio-ish with these files before >I put them on the floppies, i.e. while they're still >on the UNIX system I'm ftp'ing them with. For those that a REALLY clueless about cpio: cpio is an archive program/format that may be used as an alternative to tar. It has a rather more flexible command line format than tar. If concatenated together, the bin01.?? files form a compressed cpio archive file. I am pretty certain that the bin01.?? should be copied to messy-dos floppies. I think that loadfd just copies them from the floppies to /tmp (presumably using mread from the mtools package. The extract command then checks the bin01.?? files and, if they pass muster, passes them through a pipeline that concatenates them, uncompresses the result, and extracts the system from the cpio archive. Since I just got a new system unit (the old one went flatline) with a new 120 Meg IDE drive it seems like a good time to try 386BSD instead of Linux so I'll try this out this evening. Chris Flatters cflatter@nrao.edu