*BSD News Article 76713


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!asstdc.scgt.oz.au!nsw.news.telstra.net!act.news.telstra.net!psgrain!usenet.eel.ufl.edu!news.mathworks.com!newsfeed.internetmci.com!swrinde!cs.utexas.edu!math.ohio-state.edu!jussieu.fr!oleane!plug.news.pipex.net!pipex!hole.news.pipex.net!pipex!news.ftech.net!xara.net!emerald.xara.net!usenet2.news.uk.psi.net!uknet!usenet1.news.uk.psi.net!uknet!dispatch.news.demon.net!demon!awfulhak.demon.co.uk!awfulhak.d
emon.co.uk!awfulhak.demon.co.uk!not-for-mail
From: brian@awfulhak.demon.co.uk (Brian Somers)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Anything wrong with 960323-SNAP?
Date: 21 Aug 1996 17:04:35 +0100
Organization: Coverform Ltd.
Lines: 29
Message-ID: <4vfc2j$9d@anorak.coverform.lan>
References: <nwIHdXt@quack.kfu.com>
NNTP-Posting-Host: localhost.coverform.lan
X-NNTP-Posting-Host: awfulhak.demon.co.uk
X-Newsreader: TIN [version 1.2 PL2]

Nick Sayer (nsayer@quack.kfu.com) wrote:
: The 960323-SNAP installation I have here at work (since I don't use it
: for anything but CD worm burning, I haven't booted it up much) seems to
: have crapped all over its root partition. I had to boot the fixit
: setup, fsck (which threw away an awful lot of the root fs), and replace a
: bunch of missing stuff (including the kernel!). It's sort of back on its
: feet now, but I can't for the life of me figure out what happened. Was
: there anything in 960323-SNAP that was seriously wrong? I would think I
: would have seen any notices about it, but...

: The machine is a Compaq Deskpro XE 560. The drive is an IDE but it also
: has a AHA 1520 SCSI card for the worm burner. I was trying to set up
: a SCSI disk as a premastering volume. I halted the machine normally and
: then it started failing to boot (the spinning baton would freeze loading
: the kernel text). Solaris 2.5.1 works just fine on this machine.

: So much of /sbin got cleaned out I'll probably have to upgrade it to
: 960801 anyway (I fetched lots of files from home, which is running
: 960501)...

I've been running 960323 on my laptop since it came out.  Works fine
except for the nasty 3com NIC interrupt problems.

I did shaft the entire /usr/lib directory at one point, but as I remember
it was because I was playing....

--
Brian <brian@awfulhak.demon.co.uk>
Don't _EVER_ lose your sense of humour....