I just recompiled again but without the initrd, but said yes to all block
raid choices as well as for my scsi adapter(2940). I just don't know!
On Thu, 20 Jan 2000, Eric Sisler wrote:
> Steve Borho <[EMAIL PROTECTED]> wrote:
>
> >> I was just getting ready to ask a similar question. I just installed 6.1
> >> on a testbed server and configured all the filesystems as RAID1, including
> >> / and /boot. I was wondering about the mechanics of this with a custom
> >> kernel. I'm guessing that initrd has been rewritten to include the various
> >> raid personalities support. My *guess* at this point is:
>
> >> The SCSI card drivers can be built-in or modularized.
> >> Whichever raid type you're using for / and /boot must be left as modules.
> >> You must build an initrd image, so it'll have the raid drivers.
>
> >If you're / is a software raid device, then you'll need to either compile
> >in that raid level into the kernel, or make it modular and create an
> >initrd.
>
> So what you're saying is that it works either way, just like SCSI card
> drivers.
>
> Either build the raid personality into the kernel and you don't need an
> initrd (assuming you don't need one for SCSI card drivers) -OR- Leave the
> raid personality as a module and build an initrd image.
>
> My question then is: How come this doesn't create a chicken & the egg type
> of problem, like leaving the SCSI card drivers modularized and not making
> an initrd image (been there, done that!). How is lilo able to access /boot
> if /boot is on a software RAID partition and there's no initrd image
> because the raid driver is built-into the kernel? Or am I just being
> dense, which is a possibility given the amount of sleep I've gotten lately...
>
> -Eric
>
>
> Eric Sisler
> Library Computer Technician
> Westminster Public Library
> Westminster, CO, USA
> [EMAIL PROTECTED]
>
> Linux - don't fear the Penguin.
> Want to know what we use Linux for?
> Visit http://gromit.westminster.lib.co.us/linux
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
>
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.