Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!ira.uka.de!news.dfn.de!urmel.informatik.rwth-aachen.de!acds.physik.rwth-aachen.de!kuku
From: kuku@acds.physik.rwth-aachen.de (Christoph Kukulies)
Newsgroups: comp.os.386bsd.bugs
Subject: NetBSD install1.fs1 chokes
Date: 30 Apr 1993 10:56:14 GMT
Organization: I.Physikalisches Institut RWTH-Aachen
Lines: 26
Distribution: world
Message-ID: <1rr0ke$snp@urmel.informatik.rwth-aachen.de>
Reply-To: kuku@acds.physik.rwth-aachen.de
NNTP-Posting-Host: acds.physik.rwth-aachen.de
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
I expressed my reservation earlier about the appearance of a 'second thread' as
NetBSD seems to become, but I could not resist trying to picture out how it
really behaves. My first experience is the following:
I dl'd the whole NetBSD to my server machine, took install1.fs1 and
install2.fs and produced two diskettes by doing a
dd if=install1.fs1 of=/dev/rfd0a obs=7680
Trying to boot it yields the typical messages that appear when no kernel
is being found (like ...trying boot, trying 386bsd.old, .alt, vmunix etc..)
There is a README telling that the install disks are broken but why are they
standing still around?
Is there a replacement? Or a fix? A patch to patch the patch?
--
--Chris
Christoph P. U. Kukulies
kuku@acds.physik.rwth-aachen.de
*** Error code 1
Stop.