Subject: Re: Boot device confusion
To: None <tech-kern@netbsd.org>
From: Christos Zoulas <christos@tac.gw.com>
List: tech-kern
Date: 06/20/2005 19:55:25
In article <20050620162858.GX7072@canolog.ninthwonder.com>,
Allen Briggs <briggs@netbsd.org> wrote:
[stuff deleted]
>There are four possible solutions that I see to this:
>
> * Pick the last device instead of the first
> However, there is a comment:
> * Use the first match anyway
> * because lower devices numbers are more likely to be the
> * boot device.
>
> * Compare the disk size with the label size
> This requires some method of getting the disk size from the
> disk device.
>
> * Teach the loader about these BIOS RAID things
> Then we have two places to add new formats--FreeBSD has
> a bunch of these.
>
> * Mark devices that should not be included in the findroot
> process. So the ld_ataraid bits would, in my case, mark
> wd0 and wd1 device structures when it attaches the ld
> made up of those two disks. This could presumably be a
> new dv_flag (DVF_MEMBER ?). If this could somehow be
> exposed to sysinst, it could remove the member units
> from the available installation media list, too (also
> useful for RAIDframe units).
>
>The last seems the least invasive. Or have I overlooked another
>reasonable approach?
I think marking raid component devices so that they do not participate
as standalone devices is the easiest solution.
christos