Guess I'll join the mailing list. Big thanks to Dave for the advice. Jason
On Mon, Jul 21, 2008 at 10:45 PM, Jason Frank <duckhead92 at gmail.com> wrote: > Thanks, it'll be just opposite the work I've always done building SVR4 > packages. It will be interesting to see it from the other side. I never > thought I'd need those skills again. > > First, the addition of my particular driver to the standard CD is covered > here: http://opensolaris.org/jive/thread.jspa?messageID=202410 > > And, a generic tool to add in ITU's to the Live CD is covered here: > http://www.opensolaris.org/jive/message.jspa?messageID=256966 . I think > this sounds wonderful, but it does assume you've already gotten a solaris > box available, which I don't in my case... > > I tried to do my research, unfortunately, everything I could have used was > just not quite ready for my use. > > So, I guess my requests would boil down to an option to add memory to the > initial / ramdisk for the LiveCD to the GRUB command line, something like > extra_ramdisk_size=+50m. That way, I could just pkgadd the package and be > done. And, I couldn't accidentally request a ramdisk that's too small > either. It would be nice to have 2 more GRUB options to skip the keyboard > and lang questions also. > > Then there is also a request to ask for a driver disk at time of the kernel > loading (for people that dont like to muck with the .iso's) That should of > course, extend to thumbdrives, CD's and whatever else. > > I'll get both of those entered in bugzilla tomorrow. > > I don't like the idea of sacrificing 2 of the 24 slots in my chassis to a > boot disk mirror (and I never run singles), which is why I was trying to > avoid that alternative (since that reduces my available disk space by almost > 10%.) I figured I could just use a CF card for that, and save the drive > bays. But, I don't see another choice right now. So, I guess I'll just go > that route. > > Sometime off in the future, it would be really neat to be able to build a > BE out on a raidz array, and then zfs send that out to a boot device > (kernel, drivers, miniroot, etc). Then, the vfstab in the miniroot would > point to my raidz array, and we go from there. Near as I can tell, that > should be possible, but you'd need a place to build that BE all by itself, > and do the cloning. That would at least involve changes to the IPS tools, > and bedadm (and probably 100 other things) to support it. That way, I could > have removed my snv 89 CF Card, put the 93 BE on another Card, and booted up > under that one. > > Thanks for the feedback, I'm looking forward to getting back to Solaris, > and I'm impressed already with the community's quality. > > Jason > > > > On Mon, Jul 21, 2008 at 7:28 PM, Dave Miner <Dave.Miner at sun.com> wrote: > >> 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 >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/install-discuss/attachments/20080721/88dad28c/attachment.html>
