![[Return to Library]](BOOKSHLF.GIF)
![[TOC]](TOC.GIF)
![[PREV]](REW.GIF)
![[NEXT]](FF.GIF)
![[INDEX]](INDEX.GIF)
![[Help]](HELP.GIF)
If you want to update a system that has worldwide language support installed, use the update procedures shown in Chapter 10. The wwinstallupdate program deletes worldwide support subsets, invokes installupdate to update the base operating system software subsets, and then updates worldwide support subsets and merges the saved system files. Note
The goal of this chapter is to provide the information necessary for you to perform the user actions shown in Table 2-1.
| After reading this chapter, you will ... |
|---|
| Perform prerequisite tasks before starting the update. |
| Decide whether to use CD-ROM or the network as the distribution media. |
| Perform prerequisite tasks based on the media you choose. |
| Start the update installation from CD-ROM or RIS. |
| Respond to prompts during the early phase of the update. |
| Use the Update Administration Utility to perform postinstallation tasks. |
| Run the catman -w command to update the whatis reference page database. |
Table 2-2 provides the steps to get you started quickly.
| If you have experience performingupdate installations... | FollowInstructions In: |
|---|---|
| Perform prerequisite tasks. | Section 2.5 |
| Start the update installation from CD-ROM. | Section 2.6 |
| Start the update installation from RIS. | Section 2.7 |
| Manually merge files if necessary. | Section 2.10 |
| Perform file administration tasks using the Update Administration Utility. | Section 2.15 |
Table 2-3 provides the steps necessary to perform successive updates.
| If you are currently using... | Update the operating system to.. |
|---|---|
| Version 3.2, 3.2A, or 3.2B | Version 3.2C by using the installupdate command |
| Version 3.2C, 3.2D-1, or 3.2D-2 | Version 4.0 by using the installupdate command |
| Version 3.2E-1, 3.2E-2, or 3.2F | Version 3.2G by using setld -l |
| Version 3.2G | Version 4.0A by using the installupdate command |
| Version 4.0 or 4.0A | Version 4.0B by using the installupdate command |
An update installation preserves disk partitions, file systems, file customizations, your print and network configuration, user accounts, user files, and any other system setup you may have done on a system that is running Version 4.0 or 4.0A of the Digital UNIX operating system. Preserving this data is an advantage over a full installation, because a full installation creates new file systems and swap areas that overwrite any existing data on the disk partitions where the file systems and swap areas are to be installed.
# setld -i | grep ^OSF
You cannot install additional optional software subsets during an update installation. Additional optional software subsets can be installed by using the setld command when the update installation is complete. Refer to Chapter 8 for more information about using the setld command.
Layered products are not updated by the update installation process. To update layered products, it may be necessary to delete the existing version and reinstall the new version after the base update installation process completes. Refer to the installation instructions provided with the layered product.
The update installation does not delete any user files (that is, files that have been created by system users that were not shipped as part of the Digital UNIX operating system). The files that the update installation affects are the following:
An inspection of your system will show a number of files labeled with .new.. prefixed to the file name. These files are special to the Digital UNIX update installation. The .new.. prefix lets a file be delivered to the system without overwriting the existing, and possibly customized, version of the file. One example of a protected file is the /etc/hosts file that is shipped as /etc/.new..hosts. The existing /etc/hosts file is considered the configured version of the file and typically contains customizations that are not present in the /etc/.new..hosts file. Only the configured version of protected system files should be customized. The .new.. version of a file should never be customized.
Similar to the .new.. prefix, the .proto.. prefix also exists for all protected system files. Every .new.. file has a corresponding .proto.. file. The .proto.. files have special significance for Dataless Management Services (DMS) environments where a centralized server maintains the root, /usr, and /var file systems for client systems. DMS server System Administrators provide site-wide customizations in the .proto.. files before the configured versions are used by the server's dataless clients.
A benefit of performing an update installation is that customizations to protected system files are preserved. The mechanism for preserving customizations is the merge process. The update procedure detects whether customizations exist by comparing the existing .new.. file against the configured version. If customizations have been made, new functionality is merged into the configured file. In the event of a failure, the customized version of the file is saved with a *.PreMRG extension before the merge process.
There are other customized system files that may be on your system that are not merge protected by the update installation. Each file is saved to a .PreUPD extension and is recorded in the log file /var/adm/smlogs/upd_custom_files. You must manually merge your customizations into the new files when the update is complete.
Obsolete files are files that were shipped in Digital UNIX Version 4.0 or 4.0A, but are no longer part of Digital UNIX Version 4.0B. After an update installation you have an opportunity to save these obsolete files so that you can archive them or delete them from the operating system via the Update Administration Utility (updadmin).
The update installation is performed from single-user mode. You must be superuser or the user root to bring a system down to single-user mode. How you bring the system down to single-user mode depends on the following:
shutdowntime [message to users]
# halt >>> boot -flag s system_diskIn the previous example, system_disk is the disk where your current root file system resides. The system disk is usually the value specified by the bootdef_dev console variable.
The procedure to start the update from the command line depends on whether you are using CD-ROM or RIS as the source of the update. Section 2.6 describes how to start the update from CD-ROM, and Section 2.7 describes how to start the update from RIS.
Do not use the setld -l command to update from Digital UNIX Version 4.0 or 4.0A to Digital UNIX Version 4.0B. The only method to update your system other than performing a full installation is to use the /sbin/installupdate program that is described in this chapter. Caution
Digital recommends that you back up your operating system before beginning an update installation. If there are any interruptions when the update process is loading software subsets, it is unlikely that the update will complete successfully. Should this happen, you must restore the original version of Digital UNIX that was previously installed on your system before you can attempt another update. Refer to System Administration for information about backing up your current system.
Some layered products must be deleted before the update installation can proceed. Section 2.8.2.1 shows an example of the messages you will see if these layered products are detected during the update process. The software subsets associated with the following layered products halt the update installation and must be deleted before beginning the update:
Use the setld command to delete the software subsets associated with these layered products. Section 2.8.2.1 describes how to delete layered products.
If your file systems have less space available than the amount shown in Section G.2, consider using the setld command to delete unnecessary software subsets before you begin the update. You should also remove all unnecessary kernel files and core files that are consuming space. Refer to Chapter 8 for more information about using the setld command.
Use the df command to check your current disk usage. Refer to Section G.2 for information on the disk space requirements for the update installation of Digital UNIX Version 4.0B.
To run Digital UNIX Version 4.0B, your system might require a firmware update. Firmware updates are located on the Alpha Systems Firmware CD-ROM Version 3.8 CD-ROM that is included with your Digital UNIX software distribution kit. Update your system's firmware before beginning the update installation. Section 1.4.6 provides the minimum firmware revision for each supported processor.
After you have completed all prerequisite tasks, proceed to Section 2.6 if you are using the Digital UNIX CD-ROM to perform the update. Proceed to Section 2.7 if you are using RIS to perform the update.
If you do not know the CD-ROM device name, use the file command specifying the raw device to find it. (You must be root to run the file command.) CD-ROM devices are prefixed with the letters RRD. Using the | (pipe) command to filter the output of the file command to the grep command to search for RRD ensures that only your CD-ROM devices are output in the result of the command. Enter a command similar to the following; you must be logged in as root:
# file /dev/rrz*c | grep RRD /dev/rrz4c: character special (8/4098) SCSI #0 RRD44 disk #32 (SCSI ID #4)
In the previous example, the CD-ROM device is RRD44 on device /dev/rz4c. If you have more than one RRD device connected to your system, specify the device where the CD-ROM will be mounted.
Standard device names begin with rz for the block special file and rrz for the raw (character) special file. The result of the file command displays the raw device name, but you must specify the block special file when mounting the CD-ROM device.
Before beginning the update installation, be aware that the process takes from 90 to 150 minutes to complete. Actual time depends on your processor type, the speed of your CD-ROM drive, and the number of software subsets to be updated. Note
# su - password: # shutdown +10 Please log outIn the previous example, +10 shuts down the system in ten minutes and sends the message Please log out to all logged in users.
>>> boot -flag s system_diskIn the previous example, system_disk is the value specified by the bootdef_dev console variable.
INIT: SINGLE-USER MODE #
Enter the following command to activate LSM before running bcheckrc (in Step 4):
# /sbin/lsmbstartup
# /sbin/bcheckrcThe bcheckrc command also runs fsck to check the file system. If fsck finds a problem with the root (/) partition, the system shuts down and reboots.
/sbin/installupdate[-i] cdrom_device
The cdrom_device parameter is the device special file name of the CD-ROM drive. For example, to invoke /sbin/installupdate with an interactive kernel build from CD-ROM device rz4c, enter the following command:
# /sbin/installupdate -i /dev/rz4c
/sbin/installupdate[-i] mount_point
The mount_point parameter specifies the mount point of the CD-ROM device in the /etc/fstab file. For example:
# /sbin/installupdate -i /cdromIn the previous example, /cdrom is the mount point specified in the /etc/fstab file.
Pressing Ctrl/c during the update installation causes installupdate to exit. However, if you press Ctrl/c while software subsets are loading, serious operating system corruption can occur that may render the operating system unusable. In that case, you may have to restore the backed-up version of the operating system before you can attempt another update. Caution
Proceed to Section 2.8 to continue the update installation.
16.141.113.221 system9.dec.com system9The hosts entry in /etc/svc.conf must allow for local resolution of host (Internet) addresses, for example: hosts=local,yp. You can invoke the svcsetup command to modify hosts to local or edit the /etc/svc.conf file. Refer to Network Administration if you need more information about obtaining network status. Refer to Sharing Software on a Local Area Network if you need more information about RIS.
# /sbin/ping -c2 ris_server_nameSuccessful output of the /sbin/ping command is similar to the following:
# ping -c2 system9 PING system9 (16.59.l24.96): 56 data bytes 64 bytes from 16.59.l24.96: icmp_seq=0 ttl=255 time=1 ms 64 bytes from 16.59.l24.96: icmp_seq=1 ttl=255 time=0 ms ----system9 PING Statistics---- 2 packets transmitted, 2 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/0/1 msIn the previous example, system9 is the name of the RIS server. Your system is not able to communicate with the RIS server if you obtain the following results from the /sbin/ping command:
Before beginning the update installation, be aware that the process takes from 90 to 150 minutes to complete. Actual time depends on your processor type, the speed of your CD-ROM drive, and the number of software subsets to be updated. Note
# su - password: # shutdown +10 Please log outIn the previous example, +10 shuts down the system in ten minutes and sends the message Please log out to all logged in users.
>>> boot -flag s system_diskIn the previous example, system_disk is an entry such as DKA0.
INIT: SINGLE-USER MODE #
Enter the following command to activate LSM before running bcheckrc (in Step 3):
# /sbin/lsmbstartup
# /sbin/bcheckrcThe bcheckrc command also runs fsck to check the file system. If fsck finds a problem with the root (/) partition, the system shuts down and reboots to multiuser mode.
# route flushSuccessful completion of the route flush command looks similar to the following:
default 16.70.223.135 done 16.70.143 16.70.223.198 done
/sbin/installupdate[-i] ris_server_name:
The optional -i flag invokes an interactive kernel build where you can select kernel options from a menu and edit the configuration file to include any kernel customizations that you had in the previous kernel that your system may require.
For example, to run /sbin/installupdate from a RIS server named system9 with an interactive kernel build, enter a command similar to the following:
# /sbin/installupdate -i system9:The RIS server name must be appended with a colon (:).
Pressing Ctrl/c during the analysis phase of the update installation causes installupdate to exit. However, if you press Ctrl/c while software subsets are loading, serious operating system corruption can occur that may render the operating system unusable. In that case, you may have to restore the backed-up version of the operating system before you can attempt another update. Caution
Proceed to Section 2.8 to continue the update installation.
The number of software subsets installed on your system and the type of installation media used affects the time required for an update. You are required to enter information during the early phases of the update. You do not need to monitor the update under most circumstances. However, if an error occurs, messages notify you and offer options for proceeding.
The phases of the update installation include the following:
The following sections describe the information displayed on your screen during each phase of the update.
The Digital UNIX Version 4.0B (Rev. xxx) Update Installation will
update the following Digital UNIX products:
Digital UNIX V4.0
Digital UNIX V4.0A
Digital Equipment Corporation recommends that you perform complete
system software backups before proceeding. At this point, the update
procedure also checks for certain layered products that may be incompatible
with update installations. If these products are found on your system, warning
messages are displayed as described in Section 2.8.2.
If the layered product messages are not displayed, and you are satisfied with
the state of your system backup, you can proceed with the update. A prompt
is displayed as follows: Do you want to continue the update installation? (y/n) [n]:
Enter y to proceed with the installation or n if you want to exit and back up your system.
If no layered products are found, proceed to Section 2.8.3 to continue the update installation.
In Digital UNIX Version 4.0B, installupdate checks if certain layered products are installed on your system. Layered products are products that are installed on top of the Digital UNIX operating system. If detected, these layered products may be affected by the update as follows:
-----------------------------------------------------------------
This system cannot be updated with the following layered products
installed on it. Please remove these products from your system
before attempting an update installation:
DECnet/OSI
DEC Open3D
DECsafe Available Server Environment
Kubota Workstation Software
Multimedia Services
Distributed Computing Environment
System V Environment
Worldwide Language Support
------------------------------------------------------------------
Press <RETURN> to review message again. If this message appears,
the update installation cannot proceed and you must exit at the following
prompt: Enter 'stop' and press <Return> to stop:When you enter a character and press Return, your system is returned to its original state, that is, the state your system was in before the update procedure.
Follow these steps to delete the layered product that is preventing the update installation from continuing:
# setld -i | grep -i decnet | grep installed
DNABASE410 installed DECnet/OSI Base Components
(DECnet/OSI Standard Run-time
Environment)
DNADLI410 installed DECnet/OSI Datalink Components
(DECnet/OSI Standard Run-time
Environment)
DNAMOP410 installed DECnet/OSI MOP Utilities
(Optional DECnet/OSI
Components)
DNANETMAN410 installed DECnet/OSI Network Management
(DECnet/OSI Standard Run-time
Environment) The output of the setld and grep commands show that DNABASE410, DNADLI410, DNAMOP410, and DNANETMAN410 are the installed DECnet/OSI software
subsets that must be deleted.
# setld -d DNABASE410 DNADLI410 DNAMOP410 DNANETMAN410
When the update installation is complete, use the setld command to reinstall the version of the layered product that is compatible with Digital UNIX Version 4.0B.
----------------------------------------------------------------
The following layered products may require re-installation after
the update installation has completed:
Product A
.
.
.
Product Z
----------------------------------------------------------------
Press <RETURN> to review message again. You have the option to
exit from the installation procedure at this point and the following prompt
is displayed: Do you want to continue the update installation? (y/n) [n]:Enter y to proceed with the update installation or n if you want to exit the update installation and remove the layered products before restarting the update.
If you decide to proceed without removing these layered products, test the layered product when the update is finished. Digital recommends that you reinstall any layered products that are critical to the use of the updated operating system. Go to Section 2.8.3 to continue the update installation.
A Working... message displays approximately once every two minutes while system status is checked. These messages are similar to the following:
****** Checking current state of system
Depending on the system configuration, this may take
up to 10 minutes...
Working....Fri Dec 13 12:10:27 EDT 1996
Working....Fri Dec 13 12:11:52 EDT 1996
Working....Fri Dec 13 12:13:59 EDT 1996 During this phase
of the update, the update procedure does the following:
Digital UNIX system file types can be files, directories, symbolic links, block devices, or pipes. The update installation procedure expects to find system file types currently installed as they were shipped with the base operating system. The status of each file type is verified during the system status check. For example, if a file is shipped as type symbolic link in Digital UNIX Version 4.0 or 4.0A and you later customize it to a type directory, when the same file ships as type symbolic link in Digital UNIX Version 4.0B, the update installation detects the difference and exits.
When file system types are modified as part of a system customization, the update installation cannot proceed. This is intended to preserve the integrity of the software product about to be installed.
Messages display when file type conflicts are found. In the following sample message, /usr/tmp was shipped as a symbolic link and was changed to a directory:
The following directories on this system conflict with assigned file
types originally shipped in the Digital UNIX operating system. This
can be caused, for example, if a symbolic link is replaced with a
real directory.
These conflicts must be resolved before an update installation can be
performed on this system. Additional file status information can be
found in subset inventory files located in the /usr/.smdb. directory.
For later review, this message is also logged in
/var/adm/smlogs/update.log
The update procedure will exit and return the system to its original state
./usr/tmp should be Symbolic Link to ../var/tmp
You can review the list of file conflicts or exit as follows: Press <RETURN> to review message again. Enter any character and press <RETURN> to exit:When you exit from the update procedure, the following message is displayed:
Returning system to Pre-Update state...done. Exiting Update Installation.
You must resolve any conflicts shown in the message before you can restart the update installation. If you do not resolve the conflicts, you cannot perform an update installation.
This section describes what happens when your system has sufficient disk space and what happens when your system has insufficient disk space. It also provides guidelines on how to recover additional free disk space.
----------------------------------------------------------------- file system / needs 985 Kbytes more to install the software specified. ----------------------------------------------------------------- The Digital UNIX V4.0B (Rev. xxx) Update Installation has determined that there is not enough disk space to continue the installation. You will need to remove files and/or subsets from the file systems mentioned above and then attempt the update again. Returning system to Pre-Update state...done. Exiting Update Installation...
The system exits from the update installation process.
After the system exits from the update installation procedure, you will need to remove files and/or subsets from the file systems that require more space before attempting to run the update installation procedure again. Refer to Section 2.8.5.4 for information on how to obtain additional space.
-----------------------------------------------------------------
file system /usr needs 2631 Kbytes more to install the software specified.
file system / needs 985 Kbytes more to install the software specified.
-----------------------------------------------------------------
The Digital UNIX V4.0B (Rev. xxx) Update Installation has determined
that there is not enough disk space to continue the installation.
The update procedure has used some disk space to save unprotected
customized system files on your system to a '.PreUPD' suffix. If these
files are removed, the installation can proceed.
The unprotected customized system files are typically Digital UNIX
system files that have been customized by the user or by layered
products. These files will be overwritten once the update procedure
begins to install new subsets and are therefore saved to a '.PreUPD'
suffix to avoid any loss of data.
If you wish to backup the unprotected customized system files, you
can do so by choosing 'u' from the menu below, which will put you
into the Update Administration Utility.
If you choose to continue the update installation, by choosing 'c'
from the menu below, the '.PreUPD' files will be removed from the
system.
The current disk usage per file system for .PreUPD files is:
File System .PreUPD usage (Kbytes) Space Needed (Kbytes)
---------- ---------------------- ---------------------
/usr 7200 2631
/ 1055 985
Digital UNIX Update Installation Main Menu
------------------------------------------
(c) Continue the update installation
(q) Quit the update installation
(u) Update Administration Utility
(v) View error message again
Enter your choice:Enter one of the following:
The update installation process removes the unprotected customized files for you automatically and continues with the update installation process.
The Update Administration Utility lets you save the unprotected customized files to another file system and delete the files after they have been saved. After you recover the required disk space, return to the Digital UNIX Update Installation Main Menu and continue the update installation procedure.
-----------------------------------------------------------------
file system /usr needs 2631 Kbytes more to install the software specified.
file system / needs 985 Kbytes more to install the software specified.
-----------------------------------------------------------------
The Digital UNIX V4.0B (Rev. xxx) Update Installation has determined
that there is not enough disk space to continue the installation.
The update procedure has used some disk space to save unprotected
customized system files on your system to a '.PreUPD' suffix.
The unprotected customized system files are typically Digital UNIX
system files that have been customized by the user or by layered
products. These files will be overwritten once the update procedure
begins to install new subsets and are therefore saved to a '.PreUPD'
suffix to avoid any loss of data.
If you wish to backup the unprotected customized system files, you
can do so by choosing 'u' from the menu below, which will put you
into the Update Administration Utility. This utility will allow you
to save off and/or remove these .PreUPD files from the system.
Once you remove the .PreUPD files you will still need to free up
some additional disk space, since the current amount of disk space
you need is greater than the total disk space used by the .PreUPD
files, as indicated by the chart below.
The current disk usage per file system for .PreUPD files is:
File System .PreUPD usage (Kbytes) Space Needed (Kbytes)
---------- ---------------------- ---------------------
/usr 1500 2631
/ 350 985
Digital UNIX Update Installation Main Menu
------------------------------------------
(q) Quit the update installation
(u) Update Administration Utility
(v) View error message again
Enter your choice:Enter one of the following:
After the system exits from the update installation procedure, you will need to remove files and/or subsets from the file systems that require more space before attempting to run the update installation procedure again. Refer to Section 2.8.5.4 for information on how to obtain additional space.
The Update Administration Utility lets you save the unprotected customized files to another file system or delete the files manually. However, you will still need to exit from the update installation procedure after you move or delete the unprotected customized files. After the system exits from the update installation procedure, recover more disk space and run the update installation procedure again. Refer to Section 2.8.5.4 for information on how to obtain additional space.
If the old version of a file is removed without removing the entire subset in which it resides, the update installation will still put the new version on the system. In this situation, the full size of the new file will be allocated instead of the difference between the size of the original and new versions.
For example, if /genvmunix was 7MB and a new version of /genvmunix was 8MB, update would need to reserve 1MB of free space for the new version. If /genvmunix was deleted before the update, the disk space calculation would then reserve the full 8MB for the new file. So, although, 7MB was freed before the update, 7MB more would be reserved during the update, which would result in no difference in the amount of additional space needed to continue the update.
Refer to Appendix F, which lists the software subset sizes, to help you decide which subsets to remove.
If installupdate detects any unprotected customized system files as described in Section 2.2.2, an attempt is made to save them to a .PreUPD extension, for example, custom_file.PreUPD, so that you can decide what to do with them after the update is complete.
If for any reason unprotected customized files cannot be saved, the Update Administration Utility is invoked automatically and lets you view these files and save them to backup media. The file name of each unprotected customized file is also logged in the /var/adm/smlogs/upd_custom_files file as a reminder of the files that require recustomization.
Files that are successfully saved to the .PreUPD extension are listed as such in the file /var/adm/smlogs/upd_custom_files.
The following message is displayed if customized files are found and successfully saved:
Unprotected customized system files have been found on
this system and have been saved by renaming them with
'PreUPD' file name extension. A listing of the files
and their associated subset, can be found in
/var/adm/smlogs/upd_custom_files.
After the update installation has completed, you can use
the Update Administration Utility (/usr/sbin/updadmin)
to perform system administration tasks on these files. The following message from the Update Administration Utility is
displayed if customized files are found but could not be saved: **** Unprotected Customized System File Administration ****
There are unprotected customized versions of Digital UNIX
system files currently installed on your system that are in
danger of being overwritten by new Digital UNIX
Version 4.0B(Rev. xxx) versions of the files.
These files are typically customized by users for projects
they may be working on, or by layered product software
implementation.
If you haven't already backed up your system, save these files
to back up media at this time. You can restore these files back
onto your system after the update installation has completed.
Unprotected Customized System File Admin Menu
---------------------------------------------
s) Save files
d) Delete files
v) View list of files
x) Return to installation
Enter your choice: In the previous example, the Update Administration
Utility is invoked automatically, and the menu shows the available options.
The Update Administration Utility is described in Section 2.15.
If you choose to continue with the update, the following message is displayed: A listing of unprotected customized system files
found by the Update Installation has been logged
in /var/adm/smlogs/upd_custom_files.
After the update installation has completed, you can use
the Update Administration Utility (/usr/sbin/updadmin)
to perform system administration tasks on these files.
Pressing Ctrl/c while software subsets are loading causes serious operating system corruption can occur that may render the operating system unusable. You may have to restore the backed-up version of the operating system before you can attempt another update. Caution
While software subsets are being loaded, a series of messages similar to the following is displayed:
****** Updating system to Digital UNIX V4.0B (Rev.xxx)
43 subset(s) will be installed.
Loading 1 of 43 subset(s)....
Base System
Copying from system9 (inet)
Working....Fri Dec 13 15:21:01 EDT 1996
Verifying
Loading 2 of 43 subset(s)....
Base System - Hardware Support
Copying from system9 (inet)
Working....Fri Dec 13 15:23:28 EDT 1996
Verifying
Loading 3 of 43 subset(s)....
Compiler Back End
Copying from system9 (inet)
Working....Fri Dec 13 15:24:06 EDT 1996
Verifying
.
.
.
Loading 33 of 43 subset(s)....
Graphical Base System Management Utilities
Copying from system9 (inet)
Verifying
Loading 34 of 43 subset(s)....
Graphical System Administration Utilities
Copying from system9 (inet)
Verifying
Loading 35 of 43 subset(s)....
Graphical Print Configuration Application
Copying from system9 (inet)
Verifying
.
.
.
Loading 42 of 43 subset(s)....
Motif 1.1
Copying from system9 (inet)
Verifying
Loading 43 of 43 subset(s)....
Ref Pages: Admin/User
Copying from system9 (inet)
Working....Fri Dec 13 15:49:57 EDT 1996
Verifying
43 of 43 subset(s) installed successfully.Individual software subsets can fail to load if a network interrupt, hardware problem, or file verification error occurs during the load process:
# init 3Error messages describe the type of error that occurred. Fix the errors reported by the messages and restart the update installation process. Refer to Section 2.6 if you are running installupdate from a CD-ROM, or Section 2.7 if you are running installupdate from a RIS server.
If the update installation fails during the loading of mandatory software subsets, you must restore your operating system back to the previous version that was installed on your system and reattempt the update installation after the failure is corrected.
*** Merging new file ./.new..DXsession into
existing ./.proto..DXsession
Merge completed successfully.
*** Merging new file ./etc/.new..passwd into
existing ./etc/.proto..passwd
adding wnn entry
Merge completed successfully.
*** Merging new file ./etc/.new..rc.config into
existing ./etc/.proto..rc.config
Adding DHCP hooks
Merge completed successfully.
.
.
.
*** Merging new file
./usr/var/adm/sendmail/.new..sendmail.cf into
existing
./usr/var/adm/sendmail/.proto..sendmail.cf
adding local.users to sendmail.cf
adding Mlocal "F=u" flag in sendmail.cf
correcting Mlocal "F=r" flag in sendmail.cf
Merge completed successfully.
*** Merging new file
./usr/share/lib/kernel_options/.new..kernel_options .db into
existing
./usr/share/lib/kernel_options/.proto..kernel_options.db
modifying Asynchronous Transfer Mode option
deleting Local Area Transport option
adding Point-to-Point (PPP)
adding ACL Subsystem
adding NTP_TIME
Merge completed successfully.When all merges are complete, the following message is displayed:
Update Installation complete with loading of subsets. Rebooting system with Digital UNIX V4.0B (Rev. xxx) generic kernel for configuration phase... Exiting Update Installation...
A log file, /var/adm/smlogs/update.log, stores the results of software subset loading and merging for your reference.
Next, the update installation configures the software subsets. Proceed to Section 2.10.
# init 3Configuration refers to the process of tailoring the software subsets, setting the host name, root password, date and time, and time zone, system tuning, and building a kernel that is required to have your hardware operate correctly with the new operating system. The software configuration display is similar to the following:
*** SYSTEM CONFIGURATION ***
Configuring "Base System " (OSFBASE410)
*** Merging new file ./.new..DXsession into
existing ./DXsession
Merge completed successfully.
*** Merging new file ./etc/.new..passwd into
existing ./etc/passwd
adding wnn entry
Merge completed successfully.
*** Merging new file ./etc/.new..rc.config into
existing ./etc/rc.config
Adding DHCP hooks
Merge completed successfully.
.
.
.
Configuring "Base System - Hardware Support " (OSFHWBASE410)
Configuring "Compiler Back End " (OSFCMPLRS410)
Configuring "Kernel Header and Common Files " (OSFBINCOM410)
*** Merging new file
./usr/share/lib/kernel_options/.new..kernel_options.db into*
existing
./usr/share/lib/kernel_options/kernel_options.db
modifying Asynchronous Transfer Mode option
deleting Local Area Transport option
adding Point-to-Point (PPP)
adding ACL Subsystem
adding NTP_TIME
Merge completed successfully.
.
.
.
Configuring "Hardware Kernel Objects " (OSFHWBINOBJECT410)
Configuring "Motif 1.1 " (OSFMOTIF11410)
Configuring "Ref Pages: Admin/User " (OSFMANOS410)
After the update installation completes, a record of the software subset configuration
information is located in /var/adm/smlogs/it.log. Examine
this log closely to check for merge failures because you will have to manually
merge your customizations into these files. Manually merging means using the
text editor of your choice to cut and paste customizations from the old version
of a file into the new version. Refer to Section 2.14.2
for more information about manually merging files.
During the kernel build process, the system configuration file /sys/conf/ system_name is automatically saved to /sys/conf/ system_name.bck, and the following message is displayed:
Saving /sys/conf/KRAMER as /sys/conf/KRAMER.bckIn the previous example, KRAMER is the host name of the system. If you customized this file, one of the postinstallation tasks is to edit the new version, include your customizations, and rebuild a tailored kernel with the customized configuration file.
The kernel build proceeds with the following messages:
The system will now automatically build a kernel
and then reboot. This will take approximately 15
minutes, depending on the processor type.
*** PERFORMING KERNEL BUILD ***
Working....Fri Dec 13 13:25:43 EDT 1996
Working....Fri Dec 13 13:27:44 EDT 1996 After the kernel
builds successfully, you are prompted to log in to your system.
If your system also has devices not supplied by Digital, you must add these options or devices to the kernel configuration file. Refer to System Administration for kernel build instructions.
Unless you invoked the update installation with the -i option, which provides the option to edit the configuration file before the kernel build, you must use the doconfig command to rebuild a customized kernel with the special options. Refer to Section 5.20 for more information.
In this case, the system will reboot with the generic kernel. The update installation log file located in /var/adm/smlogs/it.log contains the reasons for the kernel build failure. After examining the log, use the setld command to deinstall the layered product that caused the failure and then use the setld command to reinstall the most recent version of the layered product. You should then be able to build a new customized kernel with support for the layered product by using the doconfig command.
What happens when you log in for the first time depends upon whether you have a graphics workstation or a text-based terminal without graphics capabilities:
Starting the Common Desktop EnvironmentWhen the desktop appears, the following windows are displayed:
After you successfully log in, the update installation procedure is complete; your system is fully updated to Digital UNIX Version 4.0B. Go to Section 2.14 for a description of the postinstallation tasks to perform. You can perform these postinstallation tasks only as the user root.
As an example, tape device tz13 is installed with device special file names *rmt0*. Then, tape device tz12 is installed and assigned device special file names *rmt1*. After an update installation, tape device tz12 is assigned device special file names *rmt0*, and tape device tz13 is assigned device special file names *rmt1*.
If no obsolete, customized, or failed merge files are detected during the update installation, the relevant log files do not contain any data.
Digital recommends that you examine the log files when the update is complete to ensure that all files merged successfully.
When the update is complete, check for any saved files in: /var/adm/smlogs/upd_custom_files. Edit the new version of each logged file to include your customizations.
Edit the system configuration file /sys/conf/system_name if you customized this file in the previous version of Digital UNIX. The saved version is located in /sys/conf/system_name .bck. You will then need to build a tailored kernel with the customized configuration file.
If any files failed to merge during the update, an error message is displayed on your screen. Failed merge errors are located in: /var/adm/smlogs/upd_mergefail_files. Check the log to identify any failed merges and manually edit any files that failed to merge by adding your customizations. The original version of the files is always preserved for your reference as: filename.PreMRG. Refer to Section 2.15 for information on how to access the original version of a file.
When all manual merges are complete, your system is ready to use. At this time you can install additional optional software subsets provided on the Digital UNIX Version 4.0B distribution media. Refer to Chapter 8 for information about installing optional software subsets.
Apart from managing system resources effectively, using this utility provides two important safeguards:
# /usr/sbin/checklist
If your system does not have graphics capabilities, use one of the following methods to invoke the Update Administration Utility:
# /usr/sbin/updadmin
# /usr/sbin/setupThe options displayed on the Setup menu vary depending on the software installed on your system. Choose the Update Administration option from this menu. The Update Administration Utility can be invoked only after an update.
Regardless of the manner in which you invoked the utility, the Update Administration Utility Main menu is displayed as follows:
The Update Administration Utility is used to perform administration
functions on a system that has been updated by /sbin/installupdate.
Please make a selection from the following menu.
Update Administration Utility Main Menu
---------------------------------------
c) Unprotected Customized File Administration
o) Obsolete System File Administration
p) PreMRG File Administration
x) Exit this utility To exit from the utility and return to the operating system prompt
at any time, choose the exit option as follows: # Enter your choice: xChoose the following options to perform file administration tasks (such as saving, viewing, or deleting files):
When you choose this option, the following information is displayed:
******* Unprotected Customized System File Administration ******** Unprotected customized system files are typically Digital UNIX system files that have been customized by users for projects they may be working on, or by layered product software implementation. Some of these customized files may no longer be compatible with the Digital UNIX Version 4.0B operating system.
When you choose this option, the following information is displayed:
*** Obsolete System File Administration *** There are Digital UNIX files currently installed on your system that are no longer shipped or supported in Digital UNIX Version 4.0B. Some of these Obsolete files may no longer be compatible with the Digital UNIX Version 4.0B operating system. You may want to back up these files and then delete them from your system to regain disk space. For your reference, the Obsolete files are listed in /var/adm/smlogs/upd_obsolete_files.
Premerge (PreMRG) files are copies of protected system files as they existed before any merge was attempted during the update installation. When you choose this option, the following information is displayed:
************* PreMRG System File Administration *************** There are .PreMRG files left over on your system from an update installation. PreMRG files are copies of system files as they existed prior to updating your system. They are left on the system after an update installation for reference purposes only. If any system file customization merges were not successful, you can reference the .PreMRG file to include those customizations in the post merged file now residing on the system. In most cases, PreMRG files can be deleted from the system.
The following examples show only Unprotected Customized File Administration. The administration process and the submenu options are exactly the same for Obsolete System File Administration and PreMRG File Administration.
To choose an option from any menu, enter the character displayed before each option and press the Return key. For example:
# Enter your choice: c [Return]
Unprotected Customized System File Admin Menu --------------------------------------------- s) Save files d) Delete files v) View list of files x) Return to previous menuThe type of the submenu depends on the option you chose from the Main menu. Enter x to return to the Main menu. The other options in this submenu are described in the following sections.
If you choose this option, another menu is displayed as follows:
Select a method of archiving your files:
----------------------------------------
d) Save files to directory on disk
i) Save files to tar image on disk
t) Save files to tape media device
Enter your choice from the menu above, or
press <RETURN> to go back to the previous menu:
Enter the name of the tape backup device (for example: /dev/nrmt0h) that you want to use to back up customized files, or press <RETURN> to go back to the previous menu:Enter the device name as follows:
....previous menu: /dev/nrmt0hThe save utility verifies the device and saves the files as follows:
Inspecting /dev/nrmt0h... Saving customized files to /dev/nrmt0h... done.
Enter the directory that you want to use to back up obsolete files, or press <RETURN> to go back to the previous menu:If the pathname that you specify does not already exist, you are asked to confirm if the directory or file should be created (in this example the /obsolete was specified and does not exist):
There is no /obsolete directory on this system.
Do you want to create one? (y/n) [y]: y Saving obsolete files to /obsolete Finished saving obsolete files.
If you choose this option, the following prompt is displayed:
Please confirm your intent to delete customized system files from the system. (y/n) [n]: yIf you confirm the deletion, a message is displayed as follows:
Removing customized files... Finished deleting customized files.When the deletion is complete, the File Admin Menu is displayed again.
If you choose this option, the list of files is displayed screen by screen and you can press Return to display each screen. At the end of the list you can display the complete list again or return to the File Admin Menu. A sample of the output follows:
./etc/zoneinfo/Australia/South.PreUPD ./sbin/named.PreUPD ./usr/sbin/screend.PreUPD Enter 'r' to review files again, or press RETURN to go back to the previous menu:
No customized file list exists. No obsolete file list exists. No PreMRG file list exists.
There is no <name> directory on this system. Do you want to create one? (y/n) [y]:
Cannot create <directory name>.
Checking system for .PreMRG files. Depending on the number of file systems mounted, this may take a few minutes...
Compressing the tar image will result in less disk space used. Do you want to compress the tar image? (y/n) [y]:
Unable to compress <tar file>
Back up of <file type> files not detected. If you have not backed up the <file type> files yet, please do so at this time by answering 'no' to the question below and selecting the 's' option from the previous menu. Please confirm your intent to delete obsolete system files from the system. (y/n) [n]:
You have already saved the <file type> files. Do you want to save them again? (y/n) [n]:
Cannot locate a special device named <device name>
Cannot write to <device name>
A file named <file name> already exists on this system. If this is a tar archive file you can append additional files to it. Otherwise, answer 'n' to the question below. Do you want to try appending to it? (y/n) [n]: