From owner-freebsd-hackers Mon Jan 15 21:53:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA14191 for hackers-outgoing; Mon, 15 Jan 1996 21:53:25 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA14184 for ; Mon, 15 Jan 1996 21:53:16 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA02316; Tue, 16 Jan 1996 16:49:09 +1100 Date: Tue, 16 Jan 1996 16:49:09 +1100 From: Bruce Evans Message-Id: <199601160549.QAA02316@godzilla.zeta.org.au> To: bde@zeta.org.au, miff@spam.frisbee.net.au Subject: Re: location of bad144 table Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org Precedence: bulk >It would appear that the bad144 program still uses the 'c' partition, or No. >divines the end of the disk in a fashion different from the kernel code. Maybe. It attempts to screw up by always reading the label directly off the disk (like the -r option to disklabel), but this is supposed to be handled by modifying the label sector as it is read and written. >At least, bad144 runs without a slew of error messages, whilst attempting >to read the disklabel once bad144 has been run results in much unhappiness. ^^^^^^^^^ bad sector table? Can bad144 read what it wrote? Bruce