Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!gmi!zombie.ncsc.mil!news.mathworks.com!udel!gatech!howland.reston.ans.net!Germany.EU.net!zib-berlin.de!irz401!narcisa.sax.de!not-for-mail
From: j@narcisa.sax.de (J Wunsch)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: BUGS: and what to do ?
Date: 20 Mar 1995 10:39:43 +0100
Organization: Private U**x site, Dresden.
Lines: 25
Message-ID: <3kjigv$838@bonnie.tcd-dresden.de>
References: <3ka5a1$ght@nntpd.lkg.dec.com> <3kafp3$kaf@park.uvsc.edu>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Terry Lambert <terry@cs.weber.edu> wrote:
>jenkinsj@oils.ozy.dec.com (Jon Jenkins) wrote:
>] I have found (and reported here)
>] a bug in disklable which prevents
>] writing new boot sectors to the hard
>] disk. ...
>Try posting to questions@freebsd.org or hackers@freebsd.org; this
>is not a very reliable propagation medium.
...or bugs@freebsd.org. You can use send-pr(8) as well.
I think (from the few lines i've seen in this thread), it's actually
the same as another problem report i've already filed. I'm not even
sure if it's disklabel(8) that fails, at least for the problem as i've
seen it, i rather suspect the disklabel editor of sysinstall entering
bogus values. Fixing those values by running disklabel -e made my
disklabel(8) accept everything and finally write the new bootstrap.
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)