Date: Fri, 05 May 2000 15:41:34 -0600 From: "Justin T. Gibbs" <gibbs@FreeBSD.org> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Greg Lehey <grog@lemis.com>, FreeBSD-arch@FreeBSD.ORG Subject: Re: Support for bootable Vinum file systems: please review Message-ID: <200005052141.PAA58901@caspian.plutotech.com> In-Reply-To: Your message of "Fri, 05 May 2000 23:22:17 %2B0200." <3175.957561737@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
>It looks good, but I think using devstat to find possible disks is >wrong. I agree. Another thing that is ugly about this is the kludge in the partition table. I'd rather see us finally bite the bullet and move to an extensible disklabel scheme. So, in order to have a bootable vinum RAID 1 volume, your partition entry might look like this: Section 0 Section Size XXX bytes Section Type BSD Parition Info BSD Parition Specific info ... Section 1 Section Size XXX bytes Section Type Vinum Info Partition is Part 0 of X parts type RAID 1 etc. Reserved Space for additional Sections Actual partition data.... So, the bootstrap doesn't need to know how to interpret anything other than Section 0 and how to skip over other sections to find the start of data. Once the kernel is loaded, a vinum interrupt driven configuration hook can scan all known disklabel entries for its sections and build its plexes on the fly. The only additional piece of magic required is stealing root away from the booted off partition, but I'm sure Greg has already dealt with that. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005052141.PAA58901>