Text Installer via AI

Heads-up: Text Installer is Now Part of AI Client Images

If you don't use AI, installadm, or the Text Installer, you may ignore this message.

With the integration of:

6971585 Solaris Next text installer should support network boot/data storage

It is now possible to complete an interactive text installation when network booted off of AI client images. This functionality is enabled by default when using AI client images on builds 157+. In order to access this functionality, follow these steps:

1. Download the AI client image (build 157+) and create a service based on that image. This functionality is compatible with older AI servers*
2. Boot a client over the network without using the "install" flag:
   • On SPARC, from OBP enter: boot net:dhcp (As opposed to boot net:dhcp - install)
   • On x86, choose Text Installer and command line from the Grub Menu*
3. Upon booting, users of the Text Installer will see the familiar "menu of choices," from which it is possible to start the Text Installer, drop to a shell prompt, select the terminal type, etc.
4. If necessary, use the proper menu option to change the terminal type.
5. Start the Text Installer, and follow the prompts to complete installation.

* When using an AI server on build 156 or earlier, the Grub Menu selection for x86 will be "<release> boot image". However, if the AI client image is 157 or later, selecting that option will still lead to the Text Installer.

Caveats and Additional Information

• As mentioned above, for AI servers on build 156 or earlier, the Grub Menu when booting is not updated.
• The resultant installation will contain an even more limited set of packages than the full Text Installer CD image. Specifically, the packages installed are those contained on the AI client (the contents of pkg:/auto_install). After rebooting the system, pkg(1) may be used to add/remove software as normal.
• Bugs may be filed against Bugster category solaris/install/textui for problems during/after installation, and solaris/install/services for problems encountered during booting of the AI client.
• When diagnosing AI client issues prior to build 157, a common pattern was to boot without the "install" flag, investigate the system, and then re-enable the "auto-installer" service. An additional step is now needed after getting to the shell - the "manifest-locator" service should be enabled first, then the "auto-installer" service.