This chapter discuss the following topics:
Do not attempt to install Tru64 UNIX Version 4.0F without first reading the notes appropriate to your processor in Chapter 3. Failure to read these notes can result in installation problems. Also, before you start your installation, be sure to review the hardware documentation that came with your system.
To update your operating system software to
Version 4.0F, you must use the
installupdate
utility or the full installation procedure as described in the
Installation Guide.
Version 4.0F supports update installations from
Version 4.0D and Version 4.0E. See
Appendix B
for more information about disk space requirements before executing
the
installupdate
utility.
Note that the
-i
flag for the
installupdate
command will be retired in a future version of Tru64 UNIX. See
Section 8.28
for more information.
During an installation update from Version 4.0D or Version 4.0E to Version 4.0F, a number of system configuration files on the system are updated with new information. The changes to these configuration files are incorporated into the existing files on the installed system as part of the update processing. The changes are merged into the existing files after the system is rebooted and running the new Version 4.0F generic vmunix kernel.
Depending on the hardware configuration and the content of the existing system configuration files, the new Version 4.0F generic vmunix kernel may fail to boot and run the final merge. This can occur when there are entries in the existing files on the installed system that are incompatible with the new kernel.
If the new Version 4.0F generic vmunix kernel fails to boot and complete the
configuration of the updated system software, retry the boot using the
c
flag. At the SRM console prompt, issue the following command:
>>>
boot -flag c
Do not supply any other arguments. The
c
flag causes the booted kernel to use default values instead of the values
contained in the old configuration files. After the new Version 4.0F generic vmunix
kernel boots and completes merging the updates to all of the system files, the
system should boot the
/genvmunix
kernel successfully without using the
c
flag.
On a system with more than four Tulip-style network devices, a user is limited to installation from the first four.
The install kernel is built knowing only of
devices
tu0
through
tu3.
With recent network cards such as the DE504 (four network devices per card),
it will become increasingly likely that a user will attempt installation from
a higher numbered device. The boot will progress to the point where
it attempts to mount the root device (console
ewn0,
where
n
is e or further in the alphabet),
and fail.
The workaround is to install from console devices
ewa0,
ewb0,
ewc0,
or
ewd0.
If your system provides Dynamic Host Configuration Protocol (DHCP),
Remote Installation Services (RIS), or Dataless Management Services
(DMS) services to to other systems, you
must update the database files for the
join
daemon after you complete the installation. See
Section 4.4.11
for additional information.