Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!destroyer!cs.ubc.ca!unixg.ubc.ca!sitka.triumf.ca!felawka From: felawka@sitka.triumf.ca (Larry Felawka) Newsgroups: comp.unix.bsd Subject: Re: 386BSD - cpio and etc01 Date: 12 Oct 1992 23:39:44 GMT Organization: TRIUMF, Vancouver BC Lines: 24 Distribution: world Message-ID: <1bd2c0INNrfe@iskut.ucs.ubc.ca> References: <1992Oct11.220636.29711@cronkite.ocis.temple.edu> NNTP-Posting-Host: sitka.triumf.ca In article <1992Oct11.220636.29711@cronkite.ocis.temple.edu>, lafollet@astro.ocis.temple.edu (Paul Lafollette) writes: |> I fear the answer to this is no, but here goes anyhow... |> |> I do not have room for both sources and the etc distribution. I |> need the sources, so etc has to go. I do, however, have |> all of the etc01 files on a series of DOS diskettes. Is there |> any way that I can retrieve specific files or directories |> from them without copying them all to my unix hard disk (no |> room to hold them all). I am able on our mainframe to The answer is "yes" - RTFM (on your mainframe). Sorry ... couldn't resist. |> room to hold them all). I am able on our mainframe to |> cat them all together and uncompress them, but then cpio |> on that machine says the result is not a cpio file. I suspect |> that the header is in byte reversed order or something like that. Right you are ... I had the same problem. A simple filter will make your cpio file extractable on the mainframe. It would have been nicer if the compressed cpio files had been created with the cpio "-c" option (which produces ASCII headers). -- Larry Felawka