Sorry, it would work. I just didn't think of this possibility because I find it confusing.
Why is it confusing? If one has a set of disks that compose a root pool, all of those disks should be bootable.
In a mirrored setup, grub-setup does what user expects (copiing core.img to each disk). In a non-mirrored array, user could think grub-setup will do the analogous (interleaving core.img), but this wouldn't work, so what you propose is to do something different which would work but is probably not what user expects.
I wouldn't think that interleaving core.img is the right thing to do -- even if there's a firmware implementation of zfs that can read from the device, for redundancy, core.img should be written to each disk.
Not that this matters a lot (in the end user can boot), but I can't see any advantage in providing two ways to do the same thing, specially when it isn't obvious they are equivalent.
What is the alternative? core.img would need to be installed on each disk in turn in both cases.
--S _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
