Installation Overview

Issues for the three phases of software migration are the same, whether you migrate the entire environment at once or just a small portion of it. There are differences in the tasks you will perform based on the type of system on which you are installing software. Those differences are detailed in SPARC: Installing

Solaris Software, along with steps to perform the actual installation. Read this chapter before referring to SPARC: Installing Solaris Software so you understand the migration-related issues before you start.

Here is an outline of the three-phase process for a migration to the Solaris computing environment:

• What to do before you install Solaris software

  · Save configuration information; know the current layout of the disk and file systems.

  · Save the file system information such as the mapping between file system names and device names.

  · Decide which files to save, including applications, unbundled software products, and administrative files that SunOS release 4.x needs to re-create its environment and recognize its files and applications.

  · Perform backups.

• Installing Solaris software

  Install SunOS release 5.5 using installation instructions from SPARC: Installing Solaris Software.

• What to do after you install Solaris software

  · If the system is a server, set up a NIS+ master name server and prepare the server for SunOS release 4.x clients (see Chapter 10, "Setting Up a Solaris 2.5 Server to Support SunOS Release 4.x Diskless/Dataless Clients").

  · Restore SunOS release 4.x user and system data.

  · If the system will serve both Solaris clients and SunOS release 4.x clients, you will need to run programs to prepare the server (see Chapter 10, "Setting Up a Solaris 2.5 Server to Support SunOS Release 4.x Diskless/Dataless Clients").

Note that this chapter covers the installation process for different types of systems: servers, standalone systems, and dataless clients.

What's New in Installation and Configuration

SunOS release 5.5 installation introduces a number of changes in the way administrators install software on existing systems and add new systems to the network.

• SunOS release 5.5 is distributed on compact disc (CD) only. This means you must have access to a CD-ROM drive before you can install the software. However, you can set up a system that has a CD-ROM drive to act as an install server for systems without local CD-ROM drives on the network.
• SunOS release 5.5 is bundled into modules called packages. You can select packages relevant to your system and control the amount of space each installation requires or specify the applications to be available on an individual system.

  SunOS release 5.5 packages are grouped into clusters. This means that you can select a set of related packages without having to select each package separately.

• SunOS release 5.5 installation also provides a set software groups, which are groups of packages and clusters for typical users. You can select a software group to get systems running without selecting individual packages and clusters. This can be useful when you are first installing SunOS release 5.5 in a limited environment for testing. You can add or remove packages later as you gain more experience with the system.
• SunOS release 5.5 includes architecture-specific kernels, rather than the generic kernel configuration provided in earlier SunOS software releases. You will find the installed kernel in /kernel/unix instead of /vmunix.

What to Do Before You Install Solaris Software

Converting a SunOS release 4.x system to a Solaris 2.5 system involves more than just running the installation programs and loading the software. Usually, there is data on the SunOS release 4.x system that needs to be transferred to a Solaris 2.4 system. This data may be full file systems, such as /home, or locally customized system files, such as /etc/hosts or /etc/passwd.

No matter how you plan to handle the data transfer, you should back up all disk partitions by doing full dumps before you begin the installation process, just in case something should happen to any of the data. You should be cautious when installing Solaris 2.5 software. Because the device naming conventions are different in the Solaris 2.5 operating environment, it is possible to become confused and inadvertently choose the wrong disk when you install the Solaris 2.5 software. Backing up the file systems before you begin the installation procedure offers some protection should this sort of accident occur.

---

Note - Before you do anything else, back up all disk partitions.

---

Note about file system formats:

• If the Solaris 2.4 Extended Fundamental Types (EFT) are not used, the file system format used in SunOS release 4.x is upwardly compatible with and, in some cases, identical to that used in Solaris 2.4 software.
• If you are running SunOS 4.1.1 with QuickCheck or Backup Copilot installed or SunOS 4.1.2, the file system formats are identical.
• If you are running SunOS 4.1.1 without QuickCheck or Backup Copilot, SunOS 4.0.x or SunOS 4.1, the file systems are upwardly and backwardly compatible, although not identical in all cases.

Saving Disk Partition Information

Before you begin the installation process, you should save a hard copy (that is, on paper) of the system's existing disk partitions. If this information is saved online, it may be overwritten during installation. Saving the existing disk partition information serves as a reference for many decisions that are made about configuring the Solaris 2.4 system. The following procedure is one way to obtain the disk partition information.

1. Obtain the names of the disks attached to the system.

   To obtain the names of the disks attached to the system, use the format(8) command, as in the following example.

# /usr/etc/format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. sd0 at esp0 slave 24 sd0: <Quantum ProDrive 105S cyl 974 alt 2 hd 6 sec 35> 1. sd1 at esp0 slave 8 sd1: <Quantum ProDrive 105S cyl 974 alt 2 hd 6 sec 35> Specify disk (enter its number): ^D #

2. Save the disk partition information.

   In the previous example, the system is configured with two disks: sd0 and sd1. Now that you know the disks on the system, you can obtain the partition information encoded on each of the disks, using the dkinfo(8) command. You can pipe the output to a printer or to a file that you can save to another system as in the following example.

# /etc/dkinfo sd0 sd1 | lpr

---

Note - Using the previous command provides you with information only on the configured partitions. All nonconfigured partitions are displayed with the message: "No such device or address."

---

Making a List of System Components to Save

Make a list of all the system components in the existing SunOS release 4.x environment and decide which are critical to the user's system. Consider:

• Locally developed applications
• Any unbundled software products
• Third-party applications
• Third-party peripheral devices and drivers (8 mm tape drives and SBus cards, for example)

Saving File System Information

Make a list of all the locally mounted file systems that you want to transfer to the Solaris 2.5 operating environment.

1. Save file system information.

   The mappings between file system names (for example, /usr, /home) and device names (for example, /dev/sd0g) reside in the configuration file /etc/fstab. You should make a printed copy of this file before proceeding. This helps you construct the Solaris 2.4 version of the file /etc/vfstab.

Make a printed copy of the file system information as in the following example.

# lpr /etc/fstab

2. Look at the fstab file and record all file systems with a third field (the file system type) of 4.2. Here is a sample /etc/fstab file.

# cat /etc/fstab /dev/sd0a / 4.2 rw 1 1 /dev/sdod /export 4.2 rw 1 3 /dev/sd1h /home 4.2 rw 1 4 /dev/sd0g /usr 4.2 rw 1 2 /dev/sd0e /export/swap 4.2 rw 1 5

Making a List of Files and File Systems to Save

Use the following guidelines to make the list of file systems to save:

• As a general rule, do not transfer file systems containing "system" files (for example, the /usr or / file systems) in their entirety.
• Do not save temporary file systems, such as /tmp.
• Do extract and transfer the data files that have changed locally or those on which the server depends for administrative data such as some /etc files (for example, /etc/hosts), exported file systems (use the exportfs command to list them), and /tftpboot directory, which you should save as a safety precaution.
• Do completely preserve file systems containing only locally generated data, such as spool and user home directories.
• Be sure to save file systems that contain information about clients if you are migrating a server for SunOS release 4.x clients. Typically, /export would be such a file.

Saving Metadevice Configuration Information

Use this section only if you are upgrading a system running the SPARCServer^(TM) Manager or Solstice^(TM) DiskSuite^(TM) unbundled products. (These products are used to mirror, concatenate, or stripe multiple disks.)

If you want to upgrade your system without this product, you will have to modify your multiple-partition configurations to use single partitions. In particular, a concatenated or striped file system must be reorganized onto a single disk, and partitions and mirrors can no longer be used.

If the system is running SPARCserver Manager or Solstice DiskSuite, you should save the metadevice configuration information before installing Solaris 2.4 software. This enables you to recover the state of the metadevices when you install Solaris 2.4 software, and serves as a reference as you construct the list of disks attached to your system.

1. Use the metastat(8) command to save information as in the following example.

# /etc/metastat -p | lpr

2. Save the output of the metadb(8) command.

   For example.

# /etc/metadb -i | lpr

The output of metadb tells you the state database configuration information. This information is necessary to reconstruct the state databases if you reinstall Solstice DiskSuite.

Deciding the Order of Installation for Networks

If you are migrating a network, decide the order of the systems on which you will install Solaris 2.5 software to maximize convenience for the users. For example, you might want to upgrade all client systems before you upgrade any servers. The first system you upgrade should be a standalone system with a locally attached CD-ROM drive.

For a while, you will probably manage a network consisting of both SunOS release 4.x and Solaris 2.5 systems, and part of your planning should involve determining priorities. For example, you may want to upgrade one domain and use it for system administration testing and for porting internally developed applications before you upgrade the entire network environment.

Backing Up the File Systems

You can use standard commands and procedures given in SunOS release 4.x documentation to do backups. The exact command you use depends on whether the tape drive is local or remote.

To simplify the restore, you should use a separate tape for each file system's backup. If you do place more than one dump on a tape, you should include information on the label identifying the file position (sequence number) of each dump (for example, 1. /, 2./usr, 3. /home). The first dump on each tape should be numbered 1.

Saving SunOS Release 4.x System Data

After you have backed up all your file systems, make a separate tar(1) tape of the system configuration files.

1. Create a file with names of the files, directories, or file systems you want to back up.

   You can use the example list on the next page to help select system configuration files you want to save. Make one entry per line in the file with the relative path name in front as in the following example.

./etc ./var/spool/mail ./.cshrc ./.login . . .

---

Note - The list contains suggestions. You should study the items carefully and add to or delete paths depending on the configuration at your site. For example, if you have special files in directories from third-party software vendors, you may need to save them.

---

If the system is an NIS master server, you should save all the files that reside in the NIS master directory (for example, /etc). Additionally, save any other master files that you added to NIS. The suggestions for files to back up include:

• ./.cshrc
• ./.profile
• ./.login
• ./.logout
• ./.rhosts
• ./etc (if the system is an NIS client or has no name service)
• ./var/spool/calendar
• ./var/spool/cron
• ./var/spool/uucp
• ./var/nis (if the system is an NIS master server)
• Boot programs in ./tftpboot

2. Save the system configuration information.

   You may want to use a tape rather than a diskette because diskettes are limited to only 1 megabyte of data. Type the following commands to make the tar tape.

# cd / # tar cvf tapedrive -I filename

In the previous example, tapedrive is the name of the drive where you have inserted the tape for the tar command (for example, /dev/rst0). filename is the name of the file you created in step 1 of this section.

Installing Solaris Software

Install Solaris 2.5 software on the server or standalone system using software installation procedures given in SPARC: Installing Solaris Software.

---

Note - SunOS release 5.x does not support NIS. Clients that use the NIS or DNS naming service must either use the NIS binary compatibility package or continue to use a SunOS release 4.x NIS or DNS server.

---

Restoring Data

This section describes issues related to restoring the user and system data you backed up before installing the Solaris 2.5 software. If the system will serve both Solaris 2.5 clients and SunOS release 4.x clients, also see Chapter 10, "Setting Up a Solaris 2.5 Server to Support SunOS Release 4.x Diskless/Dataless Clients."

Restoring SunOS Release 4.x User Data

It is relatively easy to convert most SunOS release 4.x user data to run under a SunOS release 5.5 system. Many shell scripts will work as they are, although you should look at the next subsection for guidelines on restoring them.

Binary executable files should be recompiled for maximum efficiency. If they cannot be recompiled, they may run in binary compatibility mode if the Binary Compatibility Package is installed.

The names of the tape drives are different in Solaris 2.5. For instance, /dev/nrst0 is now /dev/rmt/0n. In addition, the restore(8) command is now named ufsrestore(1M) and resides in /usr/sbin/ufsrestore. See "Device Naming Conventions" on page 61 if you need help with Solaris 2.5 device names.

Converting the Environment Initialization Files

The SunOS release 4.1 environment initialization files, such as .login, .cshrc, and .profile, can be copied directly to the SunOS release 5.3 system software to set up the working environment. However, some SunOS release 4.x commands have been renamed or moved in SunOS release 5.5. Before running them, examine the files and replace any incompatible SunOS release 4.x commands with their SunOS release 5.5 counterparts. Appendix A, "Commands Reference Table," shows which SunOS release 4.x commands are no longer available.

To use the SunOS release 4.x initialization files to set up the SunOS release 5.5 work environment, select the same login shell in the SunOS release 5.5 environment that was used in SunOS release 4.x.

Restoring File Systems From Separate Tapes

If you created a separate dump tape for each file system containing data, run the following commands for each file system you want to restore.

# /usr/sbin/newfs device_name # mkdir -p filesystem_name # /etc/mount -F ufs device_name file_system_name # cd filesystem_name # /usr/sbin/ufsrestore rf tape_device_name

In the previous command sequence, the device_name is the name of the disk slice where the file system resides (for example, /dev/dsk/c0t3d0s7, which was /dev/sd0h under SunOS release 4.x). See "Device Naming Conventions" on page 61 for help understanding device names. filesystem is the mount point for the file system you are restoring (for example, /export/home).

---

Note - Check in advance to ensure that the target slice is large enough to accommodate the file system being restored.

---

Restoring File Systems From a Single Tape

If you did not create separate dump tapes for each file system, you can use a similar command sequence to that listed previously, but you need to position the tape to the tape file mark corresponding to the dump you want to restore. Do this using the following command.

# mt -f tape_device_name fsf count

Proceed with the steps listed in the last section. See the mt(1M) man page for additional information.

---

Note - After the user data is restored on the Solaris 2.4 system, you may need to merge the /etc/fstab information from the SunOS release 4.x system into the SunOS release 5.5 /etc/vfstab so it is automatically checked and mounted at boot time. The following subsection explains how.

---

Restoring SunOS Release 4.x System Data

This section describes how to restore the archive of system data created using instructions from the first part of this chapter. First, you must restore the information to a temporary directory on the Solaris 2.4 system.

Use the following commands to restore system data to a temporary directory (called old in the example).

# mkdir /var/tmp/old # cd /var/tmp/old # tar xvf device_name

After the information is back on the system in the temporary directory, you need to make it available in the Solaris 2.5 operating environment. Some of the data can just be merged into the files, while some types of data must be converted to new formats. This subsection gives examples of both types of data.

The system's configuration defines which files you need to work with. Complete the restore by merging or converting files as follows:

• Systems with no name service: If the system has no name service, merge or convert all the relevant system files located in /etc and /var.
• Systems that are NIS clients: If the system is an NIS client, merge or convert only the local system configuration files located in /etc and /var that are not provided via the NIS name service.
• Systems that are NIS master servers: If the system is an NIS master server, merge or convert all the files that reside in the NIS master directory (for example, /etc). Additionally, update other local configuration files in /etc and /var.

Files to Merge

To make data from any of the following files available, merge the changes into the Solaris 2.4 version of the same file. Note, however, that not all of these files were modified on the SunOS 4.x system. Identify files that were changed on

the SunOS release 4.x system and merge these only. As you read the list, note that some of the file names are slightly different. For example, /etc/auto.* are now /etc/auto_*.

The following is an example list of the SunOS release 4.x files backed up using the instructions in the first part of this chapter. These files are candidates for merging into the Solaris 2.4 operating environment.

• All automounter maps, including /etc/auto.master and any others
• /etc/aliases
• /etc/bootparams
• /etc/ethers
• /etc/hosts
• /etc/format.dat
• /etc/inetd.conf
• /etc/netmasks
• /etc/networks
• /etc/protocols
• /etc/publickey
• /etc/rpc
• /etc/services
• /etc/hosts.equiv
• /etc/remote
• /.cshrc
• /.profile
• /.login
• /.logout
• /.rhosts
• /var/spool/cron
• /var/spool/mail
• /var/spool/calendar
• /var/spool/uucp

Files to Convert

Many system files, such as the /etc/fstab file, have been replaced and do not exist under the Solaris 2.4 operating environment. Information from these files must be extracted and manually converted in the Solaris 2.5 environment. For example, /etc/printcap entries must be typed into the Solaris 2.5 printer subsystem (see the lpadmin (1M) man page). See Appendix D, "System Files Reference Table," to examine SunOS release 4.x files for changes.

Do not restore operating system executable files (such as system commands in /usr/bin) from the SunOS release 4.x system to your system after installing the Solaris 2.5 software.

You must change the following files before merging the data onto the Solaris 2.5 system.

• /etc/uucp - There have been some changes to the UUCP system. The Config, Grades, and Limits files are new in the Solaris 2.4 operating environment. The files Devconfig, Devices, Dialcodes, Dialers, Permissions, Poll, Sysfiles, and systems are the same in the Solaris 2.4 operating environment as they were in SunOS release 4.x. These files can be merged together. There are also several SunOS release 4.x files that are not used in the Solaris 2.4 operating environment.
• /etc/group - The basic format of this file is the same as it was in the SunOS 4.1 and SunOS 4.1.x releases. However, previous releases used a group entry beginning with a plus sign (+) or minus sign (-) to selectively incorporate entries from NIS maps for group. See the group(4) man page if that compatibility is needed under the Solaris 2.4 operating environment.
• /etc/netgroup - There is no /etc/netgroup file in SunOS release 5.5.
• /etc/exports - File systems to be shared on the network under the Solaris 2.4 operating environment use the /etc/dfs/dfstab file instead of /etc/exports. The format of entries in this file follows.

share -F fstype -o options -d "text" pathname resource

See the dfstab(4) man page for additional information.

• /etc/fstab - File systems to be mounted under the Solaris 2.4 operating environment use the /etc/vfstab file instead of /etc/fstab. The format of entries in the /etc/vfstab file follows.

dev raw_dev mnt_pt fs_type fsck_pass auto_mnt mnt_option

Refer to the vfstab(4) man page for additional information.

• /etc/passwd - The format of the passwd file is the same as that under SunOS release 4.x. However, user passwords are now stored in the /etc/shadow file. Refer to the passwd(4) and the shadow(4) man pages for additional information.

• /etc/sendmail.cf - The format of sendmail.cf is the same as that under SunOS release 4.x. The location of the file is now /etc/mail/sendmail.cf.
• /etc/ttytab - Under SunOS release 4.x, ttytab was used to control serial ports and the characteristics of the terminals on those serial lines. Under the Solaris 2.4 operating environment, the Service Access Facility is used to configure this capability.
• /etc/printcap - Under the Solaris 2.4 operating environment, printers are configured using the System V Release 4 print services. See System Administration Guide, Volume II for additional information.