I could be off my rocker, but I believe the answer your looking for is the fact
that Lilo cannot correctly use a raid for booting. Typically I would imagine
you
would settup / as the mirror, and perhaps make a /boot that's it's own non-raid
partition for kernel images and such, thusly lilo would be able to handle the
images
correctly. This is something I have done for a Raid5 / partition and it works
fine.
I am not aware of any other direct limitation short of the aspect that lilo
simply doesn't
understand raid .. but as long as you can get the kernel loaded and the kernel
is patched
to auto-detect the raid arrayz then all should be fine.
Corse .. like I said .. I could be off my rocker and there might be a
limitation that I am not
aware of.
Mark F. [EMAIL PROTECTED]
Nortel Networks
Christopher A. Gantz wrote:
> Hello Everyone,
>
> First I'd like to apologize if this question has been asked before, however,
> I am trying to determine the specific reason why mirroring of the root (/)
> partition can not be done with software (i.e. host based) mirroring. I've
> read (In an FAQ) that it has something to do with what both Lilo and Loadin
> expect from a root (/) partition and/or the boot block. Therefore, I was
> hoping that someone could tell me the specifics of the problem as well as
> any other information about what can and can't be a mirrored partition.
>
> Also was wondering what was the status of providing RAID 1 + 0 functionality
> in software for Linux.
>
> Thanks in advance for any help
>
> -- Chris
>
> ////////////////////////////////////////////////////////////////////////////
> // //
> // Christopher A. Gantz, MTS email: [EMAIL PROTECTED] //
> // Lucent Technologies, Bell Labs Innovation //
> // Rm 37W07, 11900 N. Pecos St. voice: (303) 538-0101 //
> // Westminster, CO 80234 fax: (303) 538-3155 //
> // //
> ////////////////////////////////////////////////////////////////////////////
