Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!hobbes.physics.uiowa.edu!math.ohio-state.edu!cs.utexas.edu!swrinde!network.ucsd.edu!news.cerf.net!crash!warelock From: warelock@crash.cts.com (Tom Zacharoff) Subject: Re: bad144 problem? Organization: CTS Network Services (crash, ctsnet), El Cajon, CA Date: 16 Aug 93 18:07:51 PDT Message-ID: <1993Aug16.180751.16931@crash> References: <9322908.27770@mulga.cs.mu.OZ.AU> Lines: 15 Jan Jaeger (janj@acci.com.au) wrote: : : You will need to have the badsect flag in you disklabel set before : wd.c will even look at the bad sector table. Depending on what : configuration you run (a 386BSD partition or full disk) you : will also have to ensure that the table ends up in the right spot : else you won't be able to ipl your system. Also, I have had a few : problems with running disklabel on a 0.2.4 system where there was : no label yet. How do I set the badsect flag in my disklabel? Is it a function of the disklabel program? I have a full disk configuration. Where does the table have to be? How do I get it there? What does it mean that I won't be able to ipl my system?