*BSD News Article 16926


Return to BSD News archive

Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!ucla-cs!ucla-mic!pita!scott
From: scott@pita.cns.ucla.edu (Scott Burris)
Subject: Re: more netbsd 0.8 woes
Message-ID: <scott.739562746@pita>
Nntp-Posting-Host: pita.cns.ucla.edu
References: <1993Jun7.182848.779@mic.ucla.edu> <CGD.93Jun7220808@erewhon.CS.Berkeley.EDU>
Date: 8 Jun 93 11:16:51 PDT
Lines: 49

cgd@erewhon.CS.Berkeley.EDU (Chris G. Demetriou) writes:


>if people want us to answer questions, they should send them to
>netbsd-help@sun-lamp.cs.berkeley.edu...  we're really too busy
>to be scanning news for bug reports...

I'll do that, my postings are mainly to help others starting work with
NetBSD from making the same mistakes.

>In article <1993Jun7.182848.779@mic.ucla.edu> scott@pita.cns.ucla.edu (Scott Burris) writes:
>>	   - halt doesn't seem to wait for a keypress

>was a bug in one of the distribution floppy sets; i've not made a new
>set yet...

>>	   - installing along with a DOS partition seems to be
>>	     an experience in itself  -- I've had the partition table get 
>>	     clobbered badly

>i didn't know this when i wrote the install notes, but it *really*
>is a good idea to have the partition you want to install NetBSD on
>be labeled with partition type a5...  the way you do this is
>is with DOS partition editor; i dunno any more than that.

Yes, it works OK if you prelabel the partition A5.  I use Norton Disk Editor.

>>	   - disk labelling after the initial install on a second drive
>>	     gives the boot doesn't leave room for partition table error

>do you have the latest version of the boot blocks from the install1
>disk?  read the various readmes in the directory with the
>installation disks; that should help...

>>   I haven't seen these:
>>	   - killing off syslogd causes the console to hang

>oh, you will...  8-)

I should have said: "I haven't seen these posted on the net".  I personally
did hit the syslogd problem.  I turned on the scsi_debug flag in the kernel
and decided to kill syslogd to get rid of its repetitive messages.  Instant
grief.  Oops.

-- 
----------
Scott Burris
UCLA Campus Network Services
cnetslb@oac.ucla.edu (310) 206-4860 - OR - scott@pita.cns.ucla.edu