Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!network.ucsd.edu!swrinde!sdd.hp.com!caen!uunet!stanford.edu!leland.Stanford.EDU!leland.Stanford.EDU!yergeau From: yergeau@leland.Stanford.EDU (Dan Yergeau) Newsgroups: comp.unix.bsd Subject: Re: 386bsd/srcdist corrupt? Message-ID: <1992Aug12.194241.11748@leland.Stanford.EDU> Date: 12 Aug 92 19:42:41 GMT References: <1992Aug12.023903.1433@msuinfo.cl.msu.edu> <veit.713610524@du9ds3> Sender: news@leland.Stanford.EDU (Mr News) Organization: DSG, Stanford University, CA 94305, USA Lines: 22 In article <veit.713610524@du9ds3>, veit@du9ds3.uni-duisburg.de (Holger Veit) writes: |> In <1992Aug12.023903.1433@msuinfo.cl.msu.edu> ignasiak@convex.cl.msu.edu (Todd Ignasiak) writes: |> |> >I think the problem is the first line of the tar file, it seems to be |> >garbled. After that it looks normal. [stuff deleted] |> RTFM. These are cpio archives, to be extracted with "extract" or with |> cat src* | uncompress | cpio -ivd |> The information about this can be found in INSTALL.NOTES. But, of course, |> real programmers don't read doc-files. Real programmers can recognize the differences between cpio archive headers and tar headers. Real programmers can figure out either header structure and write a perl script to do the extraction without using tar or cpio. :^) -- Dan Yergeau He's dead Jim. Take his phaser yergeau@gloworm.Stanford.EDU and I'll get his wallet.