On Thu, 9 Jul 2009, Karen Tung wrote: >> How would it work? >> ------------------ >> >> DC would be changed such that all x86 images created >> are bootable. The choices of a media based boot, network >> based boot (no AI) and network based boot with AI would be provided in >> the GRUB menu. > All x86 based images, including the current AI image, is already bootable.
The current AI image is bootable by itself, only as far as booting into the microroot. For further bringup, the image counts on a server being available from where to fetch solaris.zlib/solarismisc.zlib. So, really the current AI image isn't bootable when booted standalone. >> Media based boot would be the default selection. At the time the AI image >> is setup on the AI server using installadm, network based boot (no AI) >> would be made the default selection. >> If a hands off installation is intended, the "default" >> parameter in the GRUB menu.lst on the AI server can be tweaked to >> indicate network based boot with AI as the default [1]. > I think that when DC creates the image, only 1 option should be added to > the GRUB menu. > The option is to boot from media. > When the image is used for setting up the GRUB menu, > the installadm command need to alter the GRUB menu anyway. > At that time, it can add the 2 other network boot entries. > I think this is more clear, because if we include the 2 GRUB > network boot entries when we build the AI image, and people just > boot the image from media and choose the 2 network entries, > things won't work, and it will be more confusing. That is a good point. Thinking through it some more, the error case would be quite displeasing. I will modify the proposal account for this suggestion. Alok
