3 Installation Notes

The notes in this chapter discuss the following topics:

General information about installation (Section 3.1)

Layered product considerations (Section 3.2)

Full installation (Section 3.3)

Update installation (Section 3.4)

RIS installation (Section 3.5)

Do not attempt to install the operating system without first reading the notes in this chapter and in Chapter 4 that are appropriate to your processor. Failure to read these notes can result in installation problems. Also, before you start your installation process, be sure to review the hardware documentation that came with your system.

3.1 General Information About Installation

The following notes apply to the installation process in general.

3.1.1 Disk Space Requirements

The minimum disk size requirement for single-disk installations is now 1 GB. It is possible to perform single-disk installations on disks with less than 1 GB of disk space, however, performance may be degraded and it is not recommended. If you attempt a single-disk installation on a disk smaller than 1 GB, you will receive a warning message.

Although the minimum disk space for installing the operating system is a 1 GB disk, we recommend that systems have at least two 2 GB disks to ensure sufficient disk space for swap, patches, and storage.

For more information about disk space requirements, see Appendix A, which lists the size requirements for each subset.

3.1.2 Firmware Revision

The proper firmware for your system is included on the Alpha Systems Firmware Update CD-ROM that came with your kit. The Release Notes Overview included with the firmware CD-ROM provides all the information you need to install the proper firmware.

Alternatively, you can obtain this information from the Internet by using the following URL with a Web browser:

http://ftp.digital.com/pub/Digital/Alpha/firmware/readme.html You can also obtain this information from the Internet by using the following address to access the firmware using FTP:

ftp.digital.com/pub/Digital/Alpha/firmware

On most systems, you can determine the current level of the firmware entering the following command:

# consvar -v -l | grep "Firmware Rev"

If this command is not supported on your system, you can use the following command:

# uerf | grep "Firmware revision:" | tail -1

3.1.3 Files Left in /tmp Directory After Installation

After you install the operating system, a number of temporary work files may remain in the /usr/tmp directory. These files are necessary for the Tru64 UNIX installation proceedure, and are named stltmpnnnn.

It is safe to delete these files after the installation is complete. You can use the following command to delete the temporary files:

# rm -r /usr/tmp/sltmp*

3.1.4 Installing Tru64 UNIX on Disks Containing Linux disklabels

There is a known problem when installing Tru64 UNIX on disks that have disklabels that were created on Linux systems.

The workaround for this problem requires using BSD style disklabels on your Linux systems. Boot your Linux system and run the fdisk utility. At the prompt, enter b. This command rewrites the disklabel in a format that Tru64 UNIX requires. You may then install Tru64 UNIX on the disk with the BSD style label.

Alternatively, you can use the dd utility to clear the disklabel. Enter the following command at the console prompt:

>>> dd if=/dev/zero of=rdsk -bs=1024 count=1024

3.1.5 Reloading Subsets with setld

Some layered product subsets check when they are installed to see if the subsets are already on the system. If they are, they prevent you from reinstalling them. This introduces an error into the software management database, after which the setld -i command reports that the subset is not installed, even though all of its files are present on the system.

To avoid this problem, use the setld -d command to delete a subset before using the setld -l command to reinstall it.

If you try to delete a subset but you cannot, you can correct the problem by using the touch command and then the setld -d command. For example, to delete the DFARTL388 subset, you would do the following:

# touch /usr/.smdb./DFARTL388.lk
# setld -d DFARTL388

Afterwards, you can reinstall the subset using the setld -l command.

3.1.6 setld Failures Caused by Temp Files

Messages similar to the following may be displayed when using the setld utility to install subsets on a running system:

setld: Temp directory /var/tmp/stltmp2870 already in use
setld: error in Dirs()

To correct this problem, remove the temporary stl* files in the /usr/tmp directory:

# rm -r /usr/tmp/sltmp*

3.1.7 IMAP and POP

In order to use the Internet Message Access Protocol (IMAP) and Post Office Protocol (POP) servers after performing an update installation or installing the OSFINET (Additional Networking Services) subset, you need to do the following:

Make sure that the /etc/passwd file (local, yp, or NIS) contains entries for the IMAP and POP users. If it does not, create them. For example:
```
pop:*:13:6:POP Mail Service Account:/:
imap:*:14:6:IMAP Mail Service Account:/:
```
Substitute the values 13 and 14 with a user ID that is appropriate for your system. For more information, see passwd(4). Also, substitute the value 6 with the group ID of the mail group on your system; see group(4).

Enter the following command as root so that the IMAP and POP files and directories have the correct permission, owner, and group:
```
# setld -c OSFINET500 MAILSERVERSETUP
```

3.1.8 Configuration Failure Messages During System Boot

The following error messages may be displayed when your system boots. You can ignore these messages. Your system will boot and operate correctly.

failed configuring xpc subsystem
failed configuring ev7_ocla subsystem
 
Warning: subsystem xpc is neither new or old format, not configured
Warning: subsystem ev7_ocla is neither new or old format, not configured

3.1.9 Initial sendmail Warning Message

The first time you boot the system after a full installation, the following warning message is displayed as a result of starting sendmail:

warning: local host name (hostname) is not qualified;
fix $j in config file.

This indicates that the system does not have a qualified name because neither DNS (BIND) nor mail has been configured. However, sendmail will continue to operate.

3.1.10 The autopush Message Displayed During Boot

The following message is displayed on the console during system boot:

/usr/sbin/autopush: Can't push requested modules on STREAM for entry 39
/usr/sbin/autopush: Device (6,-1) already configured

You can ignore this message.

3.1.11 I/O Error Message

After the installation process has completed installing all of the requested subsets, you might see the following benign error message:

I/O error (errno 5) for block ( xxx , xxx ) on device xxx , x

You can ignore this message. The installation will complete successfully.

3.1.12 Ignore the error writing output file Message

During the installation of software subsets, ignore the error writing output file message. The error is harmless.

3.1.13 Persistent Reservation Errors

Under certain circumstances, you can encounter persistent reservation errors. If this problem occurs, see the Hardware Management manual.

3.2 Layered Product Considerations

The following notes apply to layered products for Tru64 UNIX.

3.2.1 Mounting the Associated Products CD-ROM

You can mount the Associated Products CD-ROMs (APCDs) with the mount command on Tru64 UNIX systems running Version 4.0E or higher, as follows:

# mount -r /dev/disk/cdrom0c /mnt

On releases prior to Version 4.0E, you must mount the APCDs with the following options:

# mount -r -t cdfs -o rrip /dev/rz4c /mnt

On versions prior to Version 4.0D, you might receive the following error message, indicating that compact disc file system (CDFS) support is not built in to the kernel that is currently running:

# mount -r -t cdfs -o rrip /dev/rz4c /mnt
/dev/rz4c on /mnt: No valid filesystem exists on this partition

If you receive this error, you need to build your kernel with the following option:

ISO 9660 Compact Disc File System (CDFS)

3.3 Full Installation

To perform a full installation on your system, see the instructions in the Installation Guide.

3.4 Update Installation

Version 5.1B supports update installations from Versions 5.1 and Version 5.1A.

To update your operating system software to Version 5.1B, you must use the installupdate utility as described in the Installation Guide.

The installupdate procedure checks to see if there is enough space on the disk you have selected to do the installation. If there are any conflicts, the installupdate procedure enables you to remove unecessary files to create space. For more information, see the Installation Guide.

3.5 RIS Installation

This following notes pertain to Remote Installation Services (RIS).

3.5.1 bootlink Restriction

This version of the operating system does not support RIS installation of a bootlink kernel.

CD-ROM installation using a bootlink kernel is supported.

3.5.2 Time Zone Restriction

New time zones were added in Version 5.1 of the operating system. Therefore, servers that might have indicated the US/Eastern time zone while running an earlier version of the operating system now indicate a time zone such as America/New York.

When you install a prior version of the operating system on a client from a RIS server running Version 5.1 or higher, the prior version of the operating system does not recognize the time zone and does not automatically set the time zone during the installation procedure. This occurs because the new time zones do not match those in the prior versions. Therefore, you must set the time zone manually after the installation.