Home > Articles

  • Print
  • + Share This
This chapter is from the book

This chapter is from the book

The Solaris WebStart Installation Method

As discussed earlier, the Solaris WebStart installation provides both GUI and CLI (Command Line Interface).

Table 3.3 describes hardware requirements for each interface type:

Table 3.3 Hardware Requirements for GUI and CLI

Requirements

GUI

CLI

DVD/CD-ROM Drive

Local/Remote

Local/Remote

Network Connection

Yes (for remote DVD/CD-ROM Drive)

Yes (for remote DVD/CD-ROM Drive)

Disk Space

Refer to table for software group.

Refer to table for software group.

Video Adapter

Yes

Yes

Keyboard

Yes

Yes

Monitor

Yes

Yes

Ram

Min—96Mb Recommended—128Mb or above. (For high-end servers, sizing should be done accordingly)

Min –96Mb Recommended—128Mb or above (For high-end servers, sizing should be done accordingly)


The software requirements for the Solaris WebStart GUI and CLI are as follows:

  • If you have a DVD ROM drive on you system, you require the Solaris 9 SPARC Platform Edition DVD.

  • If you have a CD-ROM drive on your system, then you require the following:

    • Solaris 9 Installation SPARC Platform Edition CD

    • Solaris 9 Software 1 of 2 and 2 of 2 SPARC Platform Edition CD

    • Solaris 9 Languages SPARC Platform Edition (For Language Support)

Automating the Pre-Installation Tasks

You can automate the installation program to enable it to provide information such as IP address, subnet mask, time zone, and so on, dynamically. To automate the installation program, provide all the relevant information in the sysidcfg file or in the Name Server Database. The installation program reads information first from the sysidcfg file and then from the Name Server Database before prompting you for information.

NOTE

You can automate the installation for SunInstall and Custom JumpStart using the sysidcfg file or the Name Server database.

The following are the advantages of automating the installation program:

  • Saves time

  • Simplifies the installation process

  • Enables unattended hands-free installation

  • Minimizes the system administration tasks

  • Reduces the overall cost of ownership

Using sysidcfg File

You must create sysidcfg files based on your need for pre-configuring different systems. You have the option of using a single sysidcfg file for all the systems you configure. However, you may want to avoid entering information such as hostname, IP address, subnet mask, or root password each time you perform installation. Therefore, it is advisable to use a unique sysidcfg file for different systems.

You can place the sysidcfg file in one of the following:

  • NFS file system—If you put the sysidcfg file in a shared NFS file system, then use the following command while booting from the network:

  • Ok>add_install_client –p

    The -p flag specifies the location of the sysidcfg file when you install the Solaris 9 software.

  • UFS or PCFS (FAT) disk—Place the sysidcfg file in the root (/) directory on the disk.

Remember the following rules while creating the sysidcfg file:

  • Keywords are not case-sensitive.

  • You can list the keywords in any order.

  • There are two types of keywords that you can use in sysidcfg file: dependent and independent. The dependent keywords are defined within the independent keywords. Note that dependent keywords are unique within the independent keywords. The dependent keywords should be enclosed within curly braces.

You can provide the following information in the sysidcfg file:

  • Name service

  • Domain name

  • Name server

  • Network interface

  • Hostname

  • IP address

  • Netmask

  • DHCP

  • IPv6

  • Root password

  • Security policy

  • Locale

  • Time zone

  • Date and time

  • Terminal type

  • Power management

A sample sysidcfg file follows:

system_locale= de_DE.UTF-9
timezone=wet
terminal=sun-cmd
timeserver=localhost
name_service=NIS {domain_name=corp.mydomain..com name_server=myserver(172.17.20.50)}
network_interface=primary {protocol_ipv6=no netmask=255.255.255.129}
security_policy=none
 root_password=expre$$

NOTE

To create the sysidcfg file, use any text editor, input the required values, and save it as the sysidcfg file.

Using Name Database Server

Perform the following steps to preconfigure settings using the Name Database Server:

  1. Log in as superuser on your NIS server.

  2. Add a local map to your /var/yp/makefile.

  3. The /var/yp/makefile comprises various procedures. Look for the variable.time procedure. Below this procedure, create a local.time procedure.

  4. NOTE

    If you are new to shell scripting, a template procedure is available at http://docs.sun.com.

  5. Within the /var/yp/makefile look for a string all. The string all is preceded by variables such as passwd group host and so on. At the end of these variables, add a string locale. It should look like this:

  6. all:passwd group host ethers ..............auto.home locale 
  7. Add the line local:local.time at the end of the file.

  8. Create a file called /etc/locale and create an entry for each domain or system. If your domain name is mycomp.com, your /etc/locale file should look like this:

  9. Locale mycomp.com

    The default locale for the domain mycomp.com is Greek. If your system name is mysys, then /etc/locale should look like this:

    el.sun_eu_greek mysys

    This means Greek is the default locale for system mysys.

  10. Make the maps, using the make command.

  11. #make /var/yp

NOTE

If you have an NIS+ domain, use nistbladm to create a locale and add entries to it. For options, use the man command, # man nistbladm.

Installing Solaris Using the WebStart Method

The WebStart installation is an interactive installation program, which provides a GUI. It installs Solaris and all co-packaged software by default. However, the user can customize the installation by selecting the desired co-packaged software. The main advantage of the WebStart installation is that it installs additional software in one session. It is simple to use because of its enhanced user interface.

NOTE

Co-packaged software refers to the software packages that are distributed with Solaris. For example, Netscape and StarOffice, which are not part of the OS and distributed with Solaris, are referred to as co-packaged software.

The WebStart installation procedure is as follows:

  1. Boot the system using the following commands.

  2. If you are installing from the network, type the command:

    ok boot net

    If you have a local DVD/CD-ROM, type the command:

    ok boot cdrom
  3. You are prompted to enter system configuration. If you did not preconfigure any information in the sysidcfg file or the Name Server Database, then you are required to provide all the configuration information at this prompt.

  4. If you opt for GUI, after you have provided the correct system configuration information, the Solaris WebStart Installation Kiosk and Welcome to Solaris dialog box appears. If your system has insufficient memory, Kiosk does not display.

  5. Click Next on the Welcome screen to proceed with the installation. The Installer screen appears, prompting you for information. At this point, decide whether you want to reboot the system and eject the disc automatically after the installation is complete.

  6. The Select Media screen appears next. Select the media you will be using to install Solaris, such as CD or DVD, Network, HTTP, or local tape. After selecting the appropriate device, click Next.

  7. Specify whether the installation is a fresh installation or an upgrade to Solaris 9. The Solaris WebStart program checks for the following conditions to check whether your system meets the minimum requirements needed to upgrade. You must have a Solaris root (/) file system partition available. Also, if you are upgrading using the Solaris 9 Installation CD, then you must have a 512-MB slice.

  8. The installation program provides the relevant instructions on the screen for you to install the Solaris software and any additional software for your system. After the installation is complete, WebStart installation program reboots your system automatically or prompts you to reboot manually.

  9. After the installation is done, you can verify installation by viewing the installation logs in the following directories:

  10. /var/sadm/system/logs
    /var/sadm/install/logs
  • + Share This
  • 🔖 Save To Your Account