- Overview
- Identifying the Master Machine
- Creating and Administering Archives
- Additional Profile Keywords
- Using Flash in an Example
- Summary
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Using Flash in an Example
This section details a complete example of a Flash installation. The major steps of this procedure are these:
Identify the master machine and create the Flash archive.
Add the installation client (if necessary) on the JumpStart server and edit the appropriate sysidcfg, profile, and rules files.
Initiate the installation on the client.
Creating the Flash Archive
We create the Flash archive on www01, an Ultra Enterprise_ 220R server acting as a Web server, and then make it available to the JumpStart server, server01, by the ftp command.
www01# pwd /var/tmp www01# uname -a SunOS www01 5.8 Generic_108528-07 sun4u sparc SUNW,Ultra-60 www01# flarcreate -n "Solaris 8 web server image" \ > -a "j.s.howard@Sun.COM" \ > -R / \ > -x /var/tmp \ > /var/tmp/S8-webserver.archive Determining which filesystems will be included in the archive... Determining the size of the archive... The archive will be approximately 699.92MB. Creating the archive... Archive creation complete. www01# ftp server01 Connected to server01.EE_Lab.Sun.COM. 220 server01 FTP server (SunOS 5.8) ready. Name (server01:root): blueprints 331 Password required for blueprints. Password: 230 User blueprints logged in. ftp> cd /jumpstart/FlashArchives 250 CWD command successful. ftp> bin 200 Type set to I. ftp> put S8-webserver.archive 200 PORT command successful. 150 Binary data connection for S8-webserver.archive (10.1.1.8,34653). 226 Transfer complete. local: S8-webserver.archive remote: S8-webserver.archive 733880662 bytes sent in 67 seconds (10738.38 Kbytes/s) ftp> quit 221 Goodbye. |
Adding the Installation Client
We add the installation client, www26 (a Netra_ t1 105 server) in this example, as an installation client on the JumpStart server, server01 (www26 has already been added to the /etc/ethers and /etc/hosts files).
server01# cd /jumpstart/OS/Solaris_8_2001-04/Solaris_8/Tools server01# ./add_install_client \ > -p server01:/jumpstart/Sysidcfg/Solaris_8 \ > -c server01:/jumpstart \ > www26 sun4u updating /etc/bootparams |
The profile used for this example, S8-webserver-Flash.profile, is similar to profiles presented in previous chapters. However, with Flash, only the following profile keywords are valid:
install_type
partitioning, and only the keyword values of explicit or existing must be used
filesys, and the keyword value of auto must not be used
fdisk (valid for Intel Architecture only)
The following profile specifies that Flash is used as the installation type, flash_install. Additionally, the profile instructs that the Flash archive is accessed through NFS, from the location specified by the archive_location keyword.
install_type flash_install archive_location nfs://10.1.1.8/jumpstart/FlashArchives/S8-webserver.archive partitioning explicit # # 4GB / and 1GB swap on a 18GB disk # filesys rootdisk.s0 free / filesys rootdisk.s1 1:449 swap |
NOTE
Since name_service=NONE is specified in the following sysidcfg file, an IP address is used for the archive_location in the profile.
The rules entry used for this example is as follows:
model SUNW,UltraSPARC-IIi-cEngine \
- \
Profiles/S8-webserver-Flash.profile \
Finish/EE_Lab-Flash.fin
|
The sysidcfg file used is as follows:
system_locale=en_US
timezone=US/Pacific
network_interface=primary {netmask=255.255.255.0
protocol_ipv6=no}
terminal=vt100
security_policy=NONE
root_password=QH311oG13nnTU
name_service=NONE
timeserver=localhost
|
NOTE
A root password is specified in the sysidcfg file. This specification overrides the root password contained within the Flash archive in /etc/shadow.
After we have created or edited the preceding files, we verify the rules file, being certain to use the check script from the Solaris 8 OE 4/01 (Update 4) CD-ROM.
server01# cd /jumpstart server01# ./check Validating rules... Validating profile Profiles/S8-webserver-Flash.profile... The custom JumpStart configuration is ok. |
The finish script used for this installation is:
#!/bin/sh
# EE_Lab-Flash.fin
# Finish script for default EE_Lab setup, JumpStart Flash
#
# clean up after flash archive install
#
for i in /a/var/adm/messages* /a/var/adm/utmpx \
/a/var/adm/wtmpx /a/var/adm/lastlog
do
cp /dev/null ${i}
done
mkdir /a/var/tmp
chown root:sys /a/var/tmp
chmod 1777 /a/var/tmp
|
NOTE
The /var/tmp directory needs to be created by the finish script because it was excluded when the archive was created with the flarcreate command.
The boot net - install command is then issued on the installation client.
ok boot net - install Resetting ... screen not found. keyboard not found. Keyboard not present. Using ttya for input and output. Netra t1 (UltraSPARC-IIi 360MHz), No Keyboard OpenBoot 3.10.24 ME, 512 MB memory installed, Serial #11699811. Ethernet address 8:0:20:b2:86:63, Host ID: 80b28663. Executing last command: boot net - install Boot device: /pci@1f,0/pci@1,1/network@1,1 File and args: - install SunOS Release 5.8 Version Generic_108528-07 64-bit Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved. whoami: no domain name Configuring /dev and /devices Using RPC Bootparams for network configuration information. Configured interface hme0 Using sysid configuration file 10.1.1.8:/jumpstart/Sysidcfg/Solaris_8/sysidcfg The system is coming up. Please wait. Starting remote procedure call (RPC) services: sysidns done. Starting Solaris installation program... Searching for JumpStart directory... Using rules.ok from 10.1.1.8:/jumpstart. Checking rules.ok file... Using profile: Profiles/S8-webserver-Flash.profile Using finish script: Finish/EE_Lab.fin Executing JumpStart preinstall phase... Searching for SolStart directory... Checking rules.ok file... Using begin script: install_begin Using finish script: patch_finish Executing SolStart preinstall phase... Executing begin script "install_begin"... Begin script install_begin execution completed. Processing default locales - Specifying default locale (en_US) Processing profile - Opening Flash archive - Validating Flash archive - Selecting all disks - Configuring boot device - Using disk (c0t0d0) for "rootdisk" - Configuring / (c0t0d0s0) - Configuring swap (c0t0d0s1) Verifying space allocation NOTE: 1 archives did not include size information Preparing system for Flash install Configuring disk (c0t0d0) - Creating Solaris disk label (VTOC) Creating and checking UFS filesystems - Creating / (c0t0d0s0) Beginning Flash archive extraction Extracting archive: Solaris 8 workgroup server image Extracted 0.00 MB ( 0% of 699.88 MB archive) Extracted 1.00 MB ( 0% of 699.88 MB archive) Extracted 2.00 MB ( 0% of 699.88 MB archive) . . output deleted for brevity . . Extracted 698.00 MB ( 99% of 699.88 MB archive) Extracted 699.00 MB ( 99% of 699.88 MB archive) Extracted 699.88 MB (100% of 699.88 MB archive) Extraction complete Customizing system files - Mount points table (/etc/vfstab) - Network host addresses (/etc/hosts) Cleaning devices Customizing system devices - Physical devices (/devices) - Logical devices (/dev) Installing boot information - Installing boot blocks (c0t0d0s0) Installation log location - /a/var/sadm/system/logs/install_log (before reboot) - /var/sadm/system/logs/install_log (after reboot) Flash installation complete Executing JumpStart postinstall phase... Executing finish script "Finish/EE_Lab-Flash.fin"... Finish script Finish/EE_Lab-Flash.fin execution completed. The begin script log 'begin.log' is located in /var/sadm/system/logs after reboot. The finish script log 'finish.log' is located in /var/sadm/system/logs after reboot. |
Just as with a "classic" JumpStart software installation, after the Flash installation completes, the specified finish script executes. If we had specified a begin script, it would have executed before the installation began. The Flash mechanism does not change the JumpStart framework, but Flash does change the manner in which the Solaris OE (and software) is installed. Flash does not do an individual installation of each software package, as suninstall does. The Flash mechanism simply writes the archive on the disk and then customizes the on-disk image to the hardware it was just installed on.
Also, keep in mind that the Flash archive is literally a snapshot of an installed system. If the archive was created on a system that has been in production or use, there may be additional clean-up that the finish scripts need to perform. Temporary files such as those found in /var/tmp and log files such as /var/adm/messages, /var/adm/utmpx, and /var/adm/wtmpx should be removed or zeroed out (as appropriate) after a Flash installation from an archive created on a production system. In this example, these files were zeroed out by the finish script.