Return to BSD News archive
Xref: sserve comp.periphs:3766 comp.sys.ibm.pc.hardware:55790 comp.unix.bsd:12075 comp.os.386bsd.questions:2892 comp.os.386bsd.misc:428 Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!kuhub.cc.ukans.edu!caen!uwm.edu!cs.utexas.edu!swrinde!gatech!howland.reston.ans.net!agate!doc.ic.ac.uk!pipex!bnr.co.uk!bnrgate!nott!cunews!revcan!latour!mcr Newsgroups: comp.periphs,comp.sys.ibm.pc.hardware,comp.sys.ibm.hardware,comp.unix.bsd,comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Re: Installing NetBSD on WD1007 ESDI drive Message-ID: <1993Jun5.054017.2724@Sandelman.OCUnix.on.ca> From: mcr@Sandelman.OCUnix.on.ca (Michael Richardson) Date: Sat, 5 Jun 1993 05:40:17 GMT References: <1993May28.011157.19632@gandalf.ca> Organization: Sandelman Software Works, Debugging Department, Ottawa, ON Keywords: WD1003,ESDI,BSD Lines: 50 In article <1993May28.011157.19632@gandalf.ca> dejones@gandalf.ca (David E. Jones) writes: >This step appears to proceed without error. We are then to re-boot and >copy the kernel onto the hard disk. If I try to do so, the kernel cannot >find the DiskLabel information. Funny thing is, the disklabel command has >no problem, and the values it reports are the values we used when installing. More particulars (since I was sitting at the throttle for most of the install): -> the kernel had problems getting a valid bad sector map. I believe that it did find the disklabel. -> trying to reset the bad sector map intialized with bad144 lost badly. >Any info from someone who has successfully installed NetBSD on a WD1007 ESDI >system would be appreciated. Please email responses, as I don't read these >groups. Fortunately... I do :-) Other things: -> if you get a bad disklabel or partition table on your disk you may not be able to boot. The problem is that the kernel tries to find a swap partition and gets confused. I reported this when I installed. Hopefully, later this weekend when I get finish building RCS and CVS for NetBSD I'll get a chance to take a look at this code. (I'm so into CVS that I hardly ever even try to build something without first checking it in... :-) Solution? Somehow wipe the info out. low level format works nicely :-) -> the question at the end of the install sequence that asks if NetBSD should overwrite a DOS partition was a little vague. I believe that if you want to have DOS somewhere on your disk and have already partitioned things nicely under DOS, that you should say no. We said yes, and this blew away DOS. I said no to MessyDrugs to start with, so I am not sure. The NetBSD that David and I were trying to load is also supposed to serve occasionally as a DOS testbench, but we would up blowing DOS away anyway... small loss. -- :!mcr!: | The postmaster never | So much mail, Michael Richardson | resolves twice. | so little time. HOME: mcr@sandelman.ocunix.on.ca Bell: (613) 798-0698 SCHOOL: mcr@physics.carleton.ca