*BSD News Article 26625


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!news.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!news.clark.edu!spool.mu.edu!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!noc.near.net!das-news.harvard.edu!honeydew.srv.cs.cmu.edu!bb3.andrew.cmu.edu!andrew.cmu.edu!nn07+
From: "N. R. Natraj" <nn07+@andrew.cmu.edu>
Newsgroups: comp.os.386bsd.questions
Subject: FreeBSD: binarydist extract problems
Date: Thu, 27 Jan 1994 12:44:22 -0500
Organization: Doctoral student, Industrial Administration, Carnegie Mellon, Pittsburgh, PA
Lines: 39
Message-ID: <YhFzpqy00WB90nqp4q@andrew.cmu.edu>
NNTP-Posting-Host: po5.andrew.cmu.edu

I was running 386bsd until about a few days back when I decided to
upgrade/change to FreeBSD. I ftped the binary distribution files using
slip on to my machine. While extracting the binary distribution it bums
out with the following message after extracting /usr/bin/vacation

tar: skipping to next file header ...

Next I put the whole binary distribution on diskette and loaded it using
load_fd. Now the same thing happens but at a different point during the
extraction process. 

Even doing a 

cat bin* | gunzip | tar tvf - | more 

bums out somewhere in between. Doing a 

cat bin* > distbin.tgz 

and then doing

gunzip distbin.tgz

bums out with a message saying there is some crc error.

Doing a 

cat bin* | gunzip | tar tvf - | more 

works fine on the machine from which the binary distribution was ftped from. 

Here is my hardware: 486dx33, 12M ram, 340 Meg IDE HD (WD 2340)
partitioned as 80Megs for DOS and the rest for FreeBSD. 

I have no idea as to why this is happening. Any help on solving this
problem will be greatly appreciated. Thanks in advance.

Natraj.