Bug#41298: acknowledged by developer (bootdisk: the rescue disk should include the sformat utility)
On Sat, Sep 02, 2000 at 03:14:28PM -0400, Adam Di Carlo wrote:
> > Dominik Kubla <firstname.lastname@example.org> writes:
> > And how do you propose to fix a bad scsi-disk on a system without a
> > controller bios to format the drive (eg. on non-x86 platforms like
> > the alpha: it happened to me on my multia and i had to cook up a second
> > rescue disk with sformat on it). There is no need to offer that option
> > in the installation menu, just put it on for the odd event when you
> > need it.
> The answer is to use the software/hardware provided by the vendor.
> Joey is right -- this will not be changing for potato.
Maybe you should reread what i wrote? If there is no software provided
by the hardware vendor you have to use scsiformat. Period.
> > What is your position on the "badblocks -w" test during installation.
> > Lots of people, myself included, don't mind the extra time just to
> > be sure their harddisk has no badblocks. Call me paranoid if you like
> > but i have seen quite a few harddisk which checkout ok with a read-only
> > test only to produce errors later on as soon as data was written to
> > those blocks.
> Our position is that we let users use it but do not set that as teh
Maybe you should reread what i wrote? I am not asking for it to be
the default, i am simply asking for it to be available at all. I am
not talking about the read-only badblocks test which is invoked when you
start mke2fs with the "-c" option. I am talking about the destructive
pattern-writing test you will only get when invoking badblocks directly.
Networking Group, Hospital of Johannes Gutenberg-University
Obere Zahlbacher Straße 69, 55101 Mainz, Germany
Tel: +49 (0)6131 17-7193 FAX: +49 (0)6131 17-477193
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org