Jason Frank wrote: [ tale of woe in attempting to add a driver ellided ] You gave it a good try, and if you wouldn't mind filing a bug on it at defect.opensolaris.org, that would be appreciated. We need to be able to support adding drivers to the live CD environment, but it hasn't been something we've spent any effort on so far.
Your best bet for now would be to take the driver package, manually pull the pieces out of it, and copy them into the file system. There should be an add_drv command in its postinstall script which will be necessary to run to get the driver known to the framework, but once you have done that it should be accessible. > > Another thing I don't quite get is how to handle this boot procedure. > In old school Solaris, I'd usually have a RAID1 mirror for /, and I'd > boot to that device (and if that failed, boot to the other). Can I > do the same thing with a raidz2 pool? I wouldn't think I could, so > I'd need to keep my kernel image on the CF, and boot from that with > root living on the raidz2 pool, but I'm evidently not figuring out > how to set that up. How do I get that working with the Indiana > installer? Do I have to go back to a Jumpstart config? That's going > to be annoying out here, since I'm just now introducing Solaris. > The installer doesn't provide any support for setting up such a configuration, nor does ZFS booting provide for your idea of booting from the kernel on one device with root elsewhere, as far as I know. You also can't boot directly from a raidz pool; you'll need to boot from a single-device pool or a mirrored pool. Assuming you can get the driver running, my best advice is to take part of two of the disks and create a mirrored root pool, and then use everything else for your raidz data pool. Dave
