![[Return to Library]](BOOKSHELF.GIF)
![[Contents]](TOC.GIF)
![[Previous Chapter]](REW.GIF)
![[Next Section]](NEXT.GIF)
![[Next Chapter]](FF.GIF)
![[Index]](INDEX.GIF)
![[Help]](HELP.GIF)
The notes in this chapter discuss the following topics:
Note
Do not attempt to install Digital UNIX Version 4.0 without first reading in Chapter 2 the notes appropriate to your processor. Failure to read these notes can result in serious installation problems.
The following notes apply to the installation process in general.
![[Previous Section]](PREV.GIF)
In this release, kernel object files are not needed for installation or kernel building. Only kernel modules are needed. The individual kernel object files are only needed for kernel development work. See Section 1.4.7 for instructions on when and how to load these objects if they are needed.
The installation procedure automatically detects the disk(s) on a system, and asks you to specify the system (root) disk. If the disk label indicates that the a partition starts at a non-zero offset, the disk may not be detected by the installation procedure. This problem most commonly occurs with disks which have previously been used by LSM. LSM modifies the a partition to start at offset 16.
If all disks on the system cannot be detected because of this problem, the installation procedure will exit to a shell prompt #. If one or more disks are detected, while others are not, the undetected disks will not be presented to the user as devices where Digital UNIX can be installed.
You can correct this problem as follows. If the installation procedure does not automatically exit to the shell prompt, exit manually. In the graphical interface, click the UNIX Shell button, and click "OK" in the dialog box that appears. In the character-cell interface, press CTRL/C.
When you see the shell prompt, enter these commands:
#
cd /dev
#
./MAKEDEV <device>
where <device> is replaced by the actual device name such as rz3. If more than one disk is not detected by the installation procedure, enter a MAKEDEV command for each undetected disk.
Enter the following commands to restart the installation procedure:
#
cd /
#
restart
This note applies to all hardware configurations that do not have an attached graphics device. If the OSFXC2SEC350 subset is installed on a system that does not have a graphics controller installed on it, the following errors may be seen:
setld: Error installing "Graphical System Administration Utilities" (OSFXADMIN400) This subset requires following subset(s) to operate correctly:
"Graphical Base System Management Utilities" (OSFXSYSMAN400) setld: Please install required subset(s) first.
These errors are caused by subset dependency ordering and if the errors occur, the following subsets will not be properly installed onto your system.
OSFXC2SEC400 OSFXSYSMAN400 OSFCDEMIN400 OSFXADMIN400 OSFTKBASE400
The following error message may be displayed during the installation of the Worldwide subsets:
/usr/sbin/setld: /usr/lbin/depord: arg list too long
The installation procedure will abort. This error may happen if the shell has too many environment variables and runs out of memory during installation.
This problem can be corrected by starting a new shell and removing the unused environment variables.
After changing the Install Type field (default to custom, or custom to default) and entering an invalid password, an error dialog box will be displayed but may not be in focus. An invalid password is one which is less than six characters long or contains only lowercase characters. Pressing Return to dismiss the dialog box when it is not in focus may cause you to be temporarily locked out of all editable fields. To avoid this situation after entering an invalid password, ensure the error dialog is in focus and either press Return or click on OK with the mouse to dismiss it. This will correctly clear the error dialog box and allow re-entry of the password.
If you encounter this temporary lock-out situation, you can work around the problem by setting focus to a non-editable field in the Installation Setup window (i.e., clicking on a menu or button) and then setting focus back to the desired entry field. You can also set focus outside the Installation Setup window and back to it.
On booting, the Qlogic driver attempts to set the Data Overrun Recovery mode to that supported by Digital UNIX. If the operation fails, the driver will print a warning message on the system console:
isp<n>: WARNING - Data Overrun Recover Mode could NOT be set!
Where <n> is the number of the Qlogic controller encountered during system probe.
Digital recommends that the Qlogic ISP1020 or ISP1020A firmware be at a minimum revision level of 2.10. This is the minimum revision of Qlogic firmware required to implement reliable data overrun error detection and recovery.
An address conflict occurs between ISA serial devices configured as COM4 and ATI Mach64 graphics controllers. Both ISA GX and PCI ATI Mach64 CX/GX/CT products use the address range of 2EC-2EF. This is the same address range assigned to COM4 devices. Consult the hardware documentation for more information.
The installation process displays the following message during the installation of some subsets:
Broken Pipe
The installation will complete successfully and the message can be ignored.
The versions of the layered products shown in Table 1-1 are compatible with, or were specifically developed to take advantage of new Digital UNIX features. They may also provide new hardware support or resolutions to problems. The table shows the correct layered product versions to use with this release.
| Layered Product | Digital UNIX Version 3.2 | Digital UNIX Version 3.2C | Digital UNIX Version 4.0 |
| POLYCENTER AdvFS Utilities | Version 3.2 | Version 3.2 | Version 4.0 |
| DECsafe Available Server | Version 1.2 | Version 1.2A | N/A |
| Logical Storage Manager | Version 1.2 | Version 1.2 | Version 4.0 |
| System V Environment | Version 3.2 | Version 3.2 | Version 4.0 |
| DECnet | Version 3.0 | Version 3.0 | Version 4.0 |
| SNA Peer | None | Version 1.2 | Version 1.2 with ECO 1 |
DEC FUSE Version 2.1A and prior versions are not supported under Digital UNIX version 4.0. DEC FUSE Version 3.0 is supported under Digital UNIX version 4.0.
Digital UNIX Digital UNIX Version 4.0 does not currently support DECnet/OSI. Any existing DECnet/OSI releases will not work with this release of Digital UNIX.
Hardware releases based on Digital UNIX Version 4.0 may not install the OSFBASE400.lk file; however, they will install a OSFBASE4??.lk lock file.
If you want to tie your product with Digital UNIX Version 4.0 you should use wildcards to check for the OSFBASE4??.lk file instead of OSFBASE400.lk file.
If you hard code the test for the OSFBASE400.lk into your subset control programs (SCP) it will fail to find the lock file when run on a system with a Version 4.0-based hardware release installed.
This policy has always been in place; however, until now, not following it had not caused any problems.
If you wish to restrict your product from installing on Version 4.0-based hardware releases, you can hardcode the OSFBASE400 string in your SCP.
A installation (default or custom) will overwrite any customization on your system.
If your system is installed with the AdvFS file system, save a copy of the /etc/fdmns directory before doing a full installation. The installation process causes this directory to be overwritten, resulting in the potential loss of configuration data contained in the directory.
If your system has Logical Volume Manager (LVM) volumes configured on it, save a copy of the /etc/lvmtab file before doing a full installation. The installation process causes this file to be overwritten, resulting in the potential loss of all data under LVM control.
If your system has LSM volumes configured on it, save a copy of the /etc/vol/volboot file before doing a full installation. Doing a full installation overwrites the /etc/vol/volboot file, resulting in the potential loss of data under LSM control.
If your system has Prestoserve configured on it, save a copy of the /etc/prestotab file before doing a full installation. The installation process causes this file to be overwritten, resulting in the potential loss of configuration data contained in this file.
See Section 3.4.1 for information on restrictions when using the Disk Configuration Manager.
The following notes apply to the update installation procedure.
This note applies to all hardware configurations that do not have an attached graphics device. If the OSFXC2SEC350 subset is installed on a system that does not have a graphics controller installed on it, the following errors may be seen:
setld: Error installing "Graphical System Administration Utilities" (OSFXADMIN400) This subset requires following subset(s) to operate correctly:
"Graphical Base System Management Utilities" (OSFXSYSMAN400) setld: Please install required subset(s) first.
These errors are caused by subset dependency ordering and if the errors occur, the following subsets will not be properly installed onto your system.
OSFXC2SEC400 OSFXSYSMAN400 OSFCDEMIN400 OSFXADMIN400 OSFTKBASE400
When lightweight wiring is used with granularity hints, the system can experience the following panic message:
panic: lw_remove: light weight wiring(s) found
This panic can occur on any hardware configuration, but will generally only occur on large systems using large amounts of shared memory.
Before updating your system, remove the line in /etc/sysconfigtab containing gh-chunks. Lightweight wiring is enabled by default in Digital UNIX version 4.0. Removing gh-chunks from the /etc/sysconfigtab file will ensure that granularity hints is disabled after the update installation, and that both granularity hints and lightweight wiring are not enabled simutaneously.
If granularity hints is required, lightweight wiring must be disabled by setting new-wire-method=0 in /etc/sysconfigtab. The system must then be rebooted for the change to take effect.
Before beginning your update installation from Version 3.2C, Version 3.2D-1, or Version 3.2D-2, you should refer to Appendix F.2 in the Digital UNIX Version 4.0 Installation Guide (supplied with your Version 4.0 software distribution kit). Ensure that your system meets the minimum additional disk capacity requirements to successfully update to Version 4.0. If it does not, you may need to remove some optional software subsets in addition to unnecessary core dump files, kernels, or other unrequired files, prior to starting the update procedure.
If you have already begun an update installation that exited due to insufficient additional disk space, the installation procedure will list which file systems require additional space, and how much space is required.
To identify base and layered product subsets that are currently installed, execute the following command as root:
#
setld -i | grep installed
This command will list all potential candidates for deletion.
The left column lists the subset identifier, and the right column gives a brief text description of the subset.
Next, refer to Appendix E of the Version 3.2C Installation Guide. This appendix lists the disk space required per subset for the root, /usr, and /var file system. If you have Version 3.2D-1 or Version 3.2D-2 installed, you will need to add the additional amount of space required per file system that these releases add to Version 3.2C (this information is contained in the Version 3.2D-1 and Version 3.2D-2 release notes). Next, determine which subsets can be removed to satisfy the file system space requirements of the update installation.
For example, a Version 3.2C to Version 4.0 update installation exits, requiring an additional 1 MB of space in the root file system. The optional subsets OSFATMBASE350, OSFCOMAGENT350, and OSFC2SEC350 are installed but are not being used. Referring to Appendix E in the Version 3.2C Installation Guide, the total of the root file system component (in 512-byte blocks) for these subsets is:
OSFATMBASE350 431.76 OSFC2SEC350 1513.77 OSFCOMAGENT350 182.79 -------------- ------ Total 2128.32 (512-byte blocks) Total 1.04 (MB)
Therefore, removing these three optional subsets should reclaim enough space for the update procedure to complete:
#
setld -d OSFATMBASE350 OSFC2SEC350 OSFCOMAGENT350
The update installation process does not convert the extended user profiles and ttys information to the new database format. This can be done manually after the update installation completes with the following command:
#
/tcb/bin/convauth
During an update installation, the system clock (TOY, time of year) may lose a short amount of time possibly up to 3 minutes. This may happen when you update your system from any version preceding Version 4.0, to Version 4.0 or later.
During the boot process, a message will be printed to the console indicating the condition as follows:
over 5 years since last boot - CHECK AND RESET THE DATE Setting time to last shutdown time stamp
the alternative message will be:
WARNING: preposterous time in TOY -- CHECK AND RESET THE DATE
The time will be set to the previous shutdown timestamp.
On some systems, similar behavior will occur everytime the systems transition between a version preceding Version 4.0 and version Version 4.0 or later. For example, consider a system which has one disk with Digital UNIX Version 3.2C installed and another disk with Digital UNIX Version 4.0 installed:
The problem will occur on the following systems:
| DEC_3000 series | DEC_8000 |
| DEC_4000 | DEC_10000 |
| DEC_7000 | AXPVME64 |
Note that systems running ntp should not be affected by this problem, with the exception that a warning message may be printed to the console as the system boots. Open 3D is not supported for update installations in this release. Use the setld command to remove all Open 3D subsets before updating your system.
During an update installation, the following message from the system swapon utility may appear at the start of some update installations:
swapon: /dev/rz10b: already a swap device
The swap device specified in the message may be different than the example. You can ignore this message.
After the Digital UNIX Version 4.0 update installation is complete you can remove kernel object files from your system to reclaim disk space. Kernel object files are only necessary if you are going to perform kernel development work on your system. If your system is not being used for kernel development work and you want to reclaim approximately 25 meg of disk space, use the following command to determine if any of the following subsets are loaded on your system:
#
setld -i
OSFBINOBJECT400 OSFHWBINOBJECT400 OSFADVFSBINOBJECT400 OSFATMBINOBJECT400 OSFLSMBINOBJECT400
Use the following command to delete these subsets to reclaim additional disk space:
#
setld -d
The installupdate command may select the wrong distribution media when multiple distribution media are mounted on mount points with similar names. For example, if the following devices are mounted prior to beginning an update installation and you issue a /sbin/installupdate /mnt command, installupdate will incorrectly select /dev/rz4c as the distribution media:
/dev/rz0a on / type ufs (rw) /proc on /proc type procfs (rw) /dev/rz0g on /usr type ufs (rw) /dev/rz4c /mnt1 /dev/rz11c /mnt
The workaround for this problem is to mount only the intended distribution media prior to beginning the update.
This section provides information on installing Digital UNIX Server Extensions.
If you install the Chinese subsets from a RIS server, the following error may occur:
Common Chinese Unicode Support Copying from hanax1 (inet) setld: cannot access server mapping (rcp: ris3.alpha/rp_mapping: No such file or directory) setld: Load from hanax1 failed, subset IOSZHUCSBASE400 Verifying setld: There were verification errors for "Common Chinese Unicode Support (IOSZHUCSBASE400)
This error causes the system to abort the installation process. The problem may happen in other Chinese subsets also.
The error occurs because of the number of subsets in the Worldwide kit.
To avoid this problem, create a RIS area with fewer subsets or Chinese subsets only. To do this, choose option 1 from the following menu when installing subsets to the RIS area:
Choose one of the following options:
1) Extract software from [kit location] 2) Create symbolic link to [kit location]
Enter your choice:
The subset size tables have been moved to a permanent location in the Installation Guide for this release. If you want to add optional subsets after you install Digital UNIX Version 4.0, use the df command to determine free disk space in blocks.