*BSD News Article 4013


Return to BSD News archive

Path: sserve!manuel!munnari.oz.au!mips!mips!darwin.sura.net!haven.umd.edu!decuac!pa.dec.com!jrdzzz.jrd.dec.com!tkou02.enet.dec.com!tlaeng.enet.dec.com!engage.pko.dec.com!irenaeus.mlo.dec.com!eje
Newsgroups: comp.unix.bsd
Subject: 386bsd cross-cpio fix!
Message-ID: <1992Aug21.194924.24383@engage.pko.dec.com>
From: eje@irenaeus.mlo.dec.com (Eric James Ewanco)
Date: Fri, 21 Aug 1992 19:49:24 GMT
Reply-To: ewanco@kalvin.enet.dec.com
Sender: newsdaemon@engage.pko.dec.com (USENET News Daemon)
Organization: Digital Equipment Corporation
Lines: 25


OK, folks.  Several people mentioned problems with using native cpio on their
non-Intel system, unable to unarchive the BSD distribution. I also ran into
this problem, but none of the suggestions helped me; the cpioswap program, -s,
-b, -c.

Someone suggested using the 386BSD cpio program, except that one needs to
access the archive in order to get it.

But since the 386BSD cpio should be the standard BSD cpio, I downloaded BSD
CPIO and I compiled it.  It works (once I set the _PATH_TTY #define to "/dev/".
Ignore the libraries).  

For those who want it, cpio.c.Z should be available on gatekeeper.dec.com,
pub/bsd-sources-2/usr.bin/cpio/cpio.c.Z.  If anyone wants it I'll mail it to
them.

Eric Ewanco
--
/=============================================================================\
| Eric Ewanco - Software Engineer     For the rash and outrageous opinions ex-|
| Digital Equipment Corp, Maynard MA  pressed herein I alone am responsible;  |
| ewanco@kalvin.enet.dec.com          they do not belong to DIGITAL(TM).      |
\==============================- 2 Th 2:15 -==================================/