>
> >In this case the bootfloppy has the advantage that if it is corrupt you can
> >quickly replace it with a new.
>
> This is why you'd have entries for all the disks in the lilo config files.
> You'd use lablel like Linux_d1, Linux_d2 ... or whatever. If loading the
> image from the first disk fails, you just have to enter the label of
> another kernel at the lilo prompt.
Hmm, you are right, floppy has security problem (but the customer in my case IS
root, and
there are no additional users)
I forget the fact that you can setup multiple labels,
but do you think that there is a possibility that the disk gets corrupted at a
point which,
LILO begins loading itself (prior kernel loading) and then stops due to disk I/O
error ?
thank you again for you infos,
best regards,
Benno.
>
>
> >Plus there is another additional work when a disk fails,using your solution:
> >
> >you have to set up the /bootn dir and rerun lilo.
>
> Since you must repartition and raidhotadd the new disk anyway I don't
> consider this to be much of a problem.
>
> >i plan to install software-RAID Linux PCs, where the user is a joe-average
> >user, so I think for my purposes I think I will consider the boot-floppy
> option.
>
> I don't particularely like booting off floppy for several reasons:
>
> * security problems - by booting with some sort of rescue disk you can get
> around any security on the system.
>
> * I've had more problems with dust-clogged or otherwise inoperative floppy
> disks than with failing harddisks - admittedly, this may not be typical.
>
> * additional single point of failure. If the floppy drive or controller
> breaks, you're down till you get a replacement.
>
> Bye, Martin
> --------------------------------------------------
> Martin Bene vox: +43-664-3251047
> simon media fax: +43-316-813824-6
> Andreas-Hofer-Platz 9 e-mail: [EMAIL PROTECTED]
> 8010 Graz, Austria
> --------------------------------------------------
> finger [EMAIL PROTECTED] for PGP public key
