This chapter contains release notes that apply to Tru64 UNIX Version 4.0F documentation. It discusses the following topics:
The following notes apply to the Installation Guide.
In both Sections 12.7 and 12.8, Step 7 shows the following incorrect path
for invoking the
wwinstallupdate
script:
%
/mnt/ALPHA/WORLDWIDE/wwinstallupdate
The correct path for invoking the
installupdate
script is as follows:
%
/mnt/Worldwide_Language_Support/kit/wwinstallupdate
The following section is an addition to Appendix E.
UniCensus
The
unicensus
directory contains the
UNICEN301
software subset.
UniCensus is a tool for Tru64 UNIX that you can use to collect and archive
system configuration information. UniCensus uses
sys_check(8)
to produce a HTML report showing system configuration information, revision
levels, storage subsystem configuration and other information. UniCensus is
typically configured to collect configuration information on a periodic basis
for archiving and transport to Compaq Services. It can also be configured to
run on system reboot.
The following notes describe additional information for the System Administration guide.
The description of the
printcap
entries for Advanced Printing Software is inaccurate.
When setting up Advanced Printing Software, you should set the following print symbols:
rm
- specify
@dpa
to indicate that jobs submitted to this printer should be directed to the
Advanced Printing Software inbound gateway. The inbound gateway submits
the job to an Advanced Printing Software spooler.
rp
- specify the name of the Advanced Printing Software logical printer
The Logical Partitions feature is supported on the AlphaServer GS140 system. An AlphaServer 8400 (upgraded to a GS140 by replacing the processor modules) is also supported.
XMI hardware may be used with Logical Partitions. However, XMI controllers and devices must be configured into partition zero (0). This is a console firmware restriction.
The minimum requirement for a partition is one IOP module. A partition may include a second IOP module. The maximum number of IOP modules for the entire system (the sum of all partitions) is three.
The restriction of a graphics device to windowing software (cannot
be the console device) applies only to secondary partitions. A
supported graphics device can be the console for the primary partition
(partition 0). To use a graphics console, set the
console
environment variable to
BOTH
before initializing partitions. For example:
P00>>>
set console BOTH
The instructions for setting the IO port mask (
lp_io_mask)
do not take in to account a partition with two IOP module. For this case, the
lp_io_mask
is formed by combining (logical or) the masks for individual IOP modules slots.
For example, to assign IOP modules in slots 7 and 8 to partition 1,
lp_io_mask1
would be 180.
When assigning IOP modules to secondary partitions, it is important to remember that one of the IOPs assigned to the partition must be connected to a DWLPB with a KFE72 option installed. The KFE72 provides the console serial port for secondary partitions.
The Tru64 UNIX
Installation Guide
recommends setting the
boot_reset
console environment variable to ON. This setting is not compatible with Logical
Partitions. The
boot_reset
console EV must be set to OFF.
While setting the interleave mode to none, the console may echo a series of Y characters to the console display screen (there could be several lines of Y characters). This is not an error and can be ignored.
The normal sequence of commands is as follows:
P00>>>
set lp_count
n
(where n is the number of partitions)
P00>>>
init
(initialize the primary partition)
P00>>>
lpinit
(start secondary partitions)
P00>>>
boot
(boot primary partition)
P##>>>
boot
(boot secondary partitions)
Improper operation results if the
lpinit
command is omitted. The console firmware prevents this by automatically
executing the
lpinit
command if the
lp_count
is nonzero and a
boot
command is issued on the primary partition's console terminal.
On startup, each secondary partition displays configuration information (similar to the message in Section E.4.3.1). It is possible for this message to be proceeded by a series of Y characters. This is not an error and can be ignored.
The operating system can be installed from a CD-ROM or over the network from a Remote Installation Server (RIS). It may not always be practical to configure a CD-ROM drive on all partitions and/or a RIS server may not be available. One alternative (assuming a local network is available) is to install the operating system to one partition from a CD-ROM, then configure that partition as a RIS server for the other partitions. Refer to Sharing Software on a Local Area Network for instructions on setting up a Remote Installation Server.
The
Assembly Language Programmer's Guide
(Chapter 5) should include a description of the
.rconst
directive.
This directive instructs the assembler to add subsequent data into the
.rconst
section.
This behavior is similar to the
.rdata
directive, except that the entries cannot be relocatable.
Sections 2.1.5 and 2.1.6 of the Programming with ONC RPC guide are correct only for a system running Tru64 UNIX or earlier version of the operating system. The code may not be portable to other UNIX systems.
If the client machine is not running Tru64 UNIX or earlier version of the operating system, copy the source code to the client. Check that the header calls are appropriate for the programming conventions on the client operating system and then compile the code locally.
References to the
Gate Daemon Configuration Guide
in the
Technical Overview
and possibly other books are obsolete because this document has been
removed from the
Tru64 UNIX 4.0F Documentation
CD-ROM. Information from the
Gate Daemon Configuration Guide
has been incorporated into the following
reference pages:
gated.conf(4),
gated.control(4),
gated.proto(4),
gated_intro(7),
and
gated(8).
In prior releases, reference information about kernel subsystem attributes was
found in Appendix B of the
System Configuration and Tuning Guide.
Starting with Version 4.0F, reference information about subsystem
attributes resides in the reference pages. See
sys_attrs(5)
for more information.
Note that the current set of reference pages for subsystem attributes includes more subsystems than were formerly covered in the book appendix; however, there are still subsystems with attributes that do not have reference pages. This omission will be addressed in a future release of the product.
The following errors exist in the
sys_attrs_ufs(5)
reference page:
inode-hash-size
attribute is listed as 2048. The correct default value is 512.
ufs-blkpref-lookbehind
attribute is listed as 16. The correct default value is 8.
The following information should be included in the Guide to Preparing Product Kits.
If you are developing an Asynchronous Hardware kit for Version 4.0F,
you must ship symbolic links from the
/sys/BINARY
directory to every kernel module in your kit.
In Version 4.0F, the kernel build process searches only the
/sys/BINARY
directory. As a result, symbolic links from the
/sys/BINARY
directory to your kernel module must be shipped in the same subset.
The following corrections should be made to Appendix A of the Guide to Preparing Product Kits.
Step 3 of the instructions lists the incorrect paths:
%
/usr/bin/mkisofs -D -R -a -d -o \
/spare/consolidate_digital_unix.cdfs /cdimage/
The correct paths are as follows:
%
/usr/sbin/mkisofs -D -R -a -d -o \
/spare/consolidated_digital_unix.cdfs /cdimage/
Step 4 of the instructions lists the incorrect paths:
%
/usr/bin/mkisofs -D -R -a -d -o \
/spare/consolidate_digital_unix.cdfs /cdimage/
The correct paths are as follows:
%
/usr/sbin/mkisofs -D -R -a -d -o \
/spare/consolidated_digital_unix.cdfs /cdimage/
The notes in this section refer to problems with the online help volumes.
The Help viewer has the following known problems:
For example, the first time a quick help dialog box displays a reference page, the Backtrack button may be enabled even though there is no place to which to backtrack. If the dialog box is closed and then opened again, the Backtrack button is dimmed.
The following known problems occur in the online help:
In the Archiver, License Manager, and System Information applications, there is an Appearance item on one of the menus. The item should offer three options: Text Only, Large Icon, and Small Icon. In some help volumes, not all of these are documented.
There are a few links from one help volume to another that appear in a new help viewer window. In some situations, a distracting proliferation of help viewer windows can result.
You can get a new view when you want one using the New Window item on the File menu in the help viewer.
The SysMan configuration applications on-item help does not work on the items in the menu bar.
In all the SysMan applications, the keyboard method of getting on-item help does not work on the Help menu.
The update installation path shown in the installation online help is not correct. The Preinstall Review List in the installation online help should state:
Your system must be running operating system Version 4.0D or 4.0E to update to Version 4.0F.
The following problems apply only to help in specific applications:
The Kernel Tuner application records its changes immediately,
so if a system failure occurs while the Kernel Tuner is
running, any boot-time changes will take effect the next
time the system boots. If the
/etc/sysconfigtab
file contains invalid values,
you can enter the following command at the boot prompt to boot
with default values:
boot -fl c
The help volume for Display Window has opening instructions that show how to access the application from the CDE Application Manager. These should show that the Display Window icon appears in two groups.
The names of the
gated,
joind,
routed,
and
rwhod
daemons
are misspelled in the online help volume.
In the Configuring Interfaces dialog box, the fields under To Obtain IP Address are relevant for all interfaces.
In the Local Printer Settings dialog box and the Remote Printer Settings dialog box, the aliases in the Printer Aliases field must be separated by vertical bars because spaces are allowed in an alias.
The
/usr/sbin/shutdown
command now sends the Shutdown Message
each time a reminder is sent of the time remaining before
the system is shut down.
The
/etc/nologin
file is not created until immediately before the shutdown occurs.
System shutdown messages are sent to all users that are locally or remotely logged in to the system being shut down. Additionally, if the "Broadcast to NFS Clients" option is selected, shutdown messages are broadcast to all hosts that are NFS clients of the system being shut down.
The following corrected definitions replace the definitions in the glossary for Disk Configuration.
A deviation from a reference direction, either by design or in response to lateral forces.
On a disk, the sector skew per track. The skew is the angle that sector 0 of the track changes from an imaginary radius line, due to a nonuniform number of sectors per track.
The following corrected definitions replace the definitions in the glossary for BIND Configuration:
A system that queries a BIND server for host name and address information, interprets the responses, and passes the information to requesting applications.
An authoritative source for information about one or more zones. It either maintains the master copy of the hosts database for the zone or obtains the information required to serve the hosts database from another server.
Distributed Computing Environment. The capabilities of DCE are defined by the Open Software Foundation (OSF).
A logical group of systems that share services offered by DCE.
The server in a DCE cell.
In BIND Configuration, the available service types are BIND client and BIND server. The service type determines whether a system is configured to be a BIND client or a BIND server.
There are no changes to the Device Driver documentation for Version 4.0F.
Compaq maintains an online technical update page that contains any new information about the Device Driver Kit since the product was released. To view this document, go to the following URL:
http://www.unix.digital.com/faqs/publications/pub_page/ddk_update.html