This chapter contains release notes that apply to the operating system documentation. It provides information on the following:
Changes to the SPD (Section 8.1)
Netscape problem with the Search by Keyword feature (Section 8.2)
AltaVista search (Section 8.3)
Online help (Section 8.8)
8.1 Software Product Description (SPD) Replaced by QuickSpec
With this release of the operating system, the Software Product Description
(SPD) has been replaced by the Tru64 UNIX QuickSpec.
For a description of
this release of Tru64 UNIX and information about its capabilities and the
hardware it supports, see the QuickSpec.
8.2 Netscape Problem with the Search by Keyword Feature
Netscape on Tru64 UNIX does not handle JavaScript forms correctly. When you use the Reference Pages Search by Keyword feature on the Documentation CD-ROM, the search can fail.
To work around the problem, click in any other window and return to the search window.
This problem does not occur with Netscape or Microsoft Internet Explorer
on a Windows PC or Macintosh.
8.3 AltaVista CD-ROM Search Might Not Work Correctly with Netscape Communicator
When
the Tru64 UNIX
Software Documentation
CD-ROM
is used on a PC for which Internet Explorer is the default browser, the CD-ROM
search capability works as documented in the instructions window.
This window
automatically pops up when you click on the Search button that is available
from the main page of the documentation library.
The instructions tell you
to open Windows Explorer, double click on the icon for the CD-ROM drive,
and then double click on
search.exe, which automatically
loads the search query entry form into the Internet Explorer window.
When the documentation CD-ROM is used on a PC for which Netscape Communicator is the default browser, these instructions might work, but sometimes do not. Problems observed when trying to use AltaVista CD-ROM Search with Netscape Communicator (Version 4.5 or higher) include the following:
An attempt to load the search query entry form (InitPage.html) results in a "browser not found" error.
The search query entry form comes up in a window different from the Netscape browser window.
If the search query entry form does come up in the Netscape browser window, the first search query consistently hangs.
If you encounter one or more of these problems, use the following procedure to work around them:
After launching the AltaVista Search Dispatcher (search.exe), invoke Netscape manually if it is not already running.
Use the
File Open
option in the Netscape
window to find and open the
InitPage.html
file on the
CD-ROM drive.
Alternatively, you can type the URL to this
file in the Netscape browser's Location: field.
If your first search query takes more than 30 seconds to execute, click on the Stop icon and re-enter the query.
8.4 Command and Shell User's Guide
Table 3-1 in the
Command and Shell User's Guide
contains an error
for the
ls
command option.
The following description for
the
-R
option is incorrect:
-RLists all entries including
hidden files.
Without this flag, the
ls
command does not
list the names of entries that begin with a dot (.), such as
.profile,
.login, and relative pathnames.
This is the description of the
-a
option.
Therefore, the line in Table 3-1 should read as follows:
-aLists all entries
including hidden files.
Without this flag, the
ls
command
does not list the names of entries that begin with a dot (.), such as
.profile,
.login, and relative pathnames.
The information
in Section 19.10.2 of the
Security
manual describing
the binary audit log record format is incomplete and potentially misleading.
Do not use this information as a basis for any code.
8.6 Kernel Debugging
The Kernel Debugging manual was not updated for this release. Therefore, the following text replaces the existing text in Section 2.2.3.17, Displaying the Namecache Structures:
The
namecacheextension displays the per-processor namecache structures on the system, and has the following format:
namecache[-h|-help]|[-neg|-all -p cpu] [-v pid|-d dvpid|-n name]
In the following example, the -h flag displays a list of flags, with brief explanations, and it also provides some usage tips:
(kdbx) namecache -h namecache - print the namecache \ Usage : namecache [options] \ (no options) print the namecache entries on primary cpu \ -h prints help message including tips \ -p <cpu> show namecache entries on processor <cpu> \ -v <v_id> search for a vnode with <v_id> \ -d <v_id> show all the directory entries in directory <v_id> \ -n <name> search for a namecache entry with <name> \ -neg prints negative hit in global negative namecache \ -all show ALL namecache entries including negative hits \ The Hash # column has three numbers: \ 1st: hash chain (bucket) number \ 2nd: namecache entry position within the hash chain \ 3rd: index of namecache array of the namecache entry \ \ To see an actual namecache entry, specify the 1st and 3rd numbers: \ kdbx> p processor_ptr[<cpu>].namecache[<1st>*NCHSIZE+<3rd>] \ Currently, NCHSIZE is set to 15. \ \ To see all the negative entries, use "namecache -v 0 -all". \
The following example shows the default output of the
namecacheextension:(kdbx) Namecache entries on processor 0 Number of hash chains: 4096 Hash # vp vpid dvpid time ln name =========== =========== ======== ========= ======== == ================== 3 0 0 k0x0ff03440 3681 1025p 89t 7 lat.mod 4 0 0 k0x8581fd40 4229 3249p 135t 13 secconfig.mcl 8 0 0 k0x9a1ccd80 526 253p 96t 6 dsk16b 11 0 0 k0x040c3440 1026 5p 89t 3 sys 12 1 0 k0x1afd4000 4030 209p 134t 7 console 15 1 0 k0x0daa3200 2936 2926p 137t 8 updadmin 17 0 1 k0x04d75d40 1520 580p 93t 5 crash 1 0 k0x9a192480 20 6p 30t 7 inittab 18 0 0 k0x0da998c0 3011 2934p 137t 16 secconfig.cb.tcl 22 0 0 k0x0d688480 2831 2818p 78t 8 CQMGHOST 27 0 0 k0x04d57680 1434 1423p 47t 7 sys.evt 32 0 0 k0x051c4000 1812 218p 142t 6 routes 38 0 0 k0x0daa2000 2931 2926p 137t 9 mailsetup 39 0 0 k0x04c5a480 216 1087p 44t 2 .. 42 0 1 k0x044af680 660 618p 64t 1 6 1 0 k0x044aad80 684 618p 64t 2 30 43 0 0 k0x0d675b00 3025 2940p 137t 11 auditconfig 55 0 0 k0x24d886c0 6353 2696p 411t 6 master 58 0 0 k0x044aab40 685 618p 64t 2 31 60 0 0 k0x04516b40 1052 1051p 2854t 7 libc.so 1 1 k0x04d64900 1393 1423p 47t 2 .. 67 0 1 k0x0dab2fc0 3237 3073p 137t 13 setldd.cb.tcl 69 0 0 k0x1f0ae480 5020 2890p 143t 9 xlate.tcl 72 0 0 k0x05873b00 231 5p 2794t 3 tmp 79 0 1 k0x87448000 4524 218p 140t 12 printcap.bak
.
.
.
The following example displays all directory entries on processor 1 in directory 253:
(kdbx) namecache -p 1 -all -d 253 Searching for all entries in directory with v_id 253 ... Namecache entries on processor 1 Number of hash chains: 4096 Hash # vp vpid dvpid time ln name =========== =========== ======== ========= ======== == ================== 8 0 0 k0x9a1ccd80 526 253p 39t 6 dsk16b 25 0 0 k0x9a1cdb00 528 253p 96t 6 dsk16c 41 1 0 k0x9a1cd680 530 253p 39t 6 dsk16d 57 0 0 k0x9a1cdd40 532 253p 39t 6 dsk16e 63 0 0 NULL 0 253p 39t 8 floppy0g 73 0 0 k0x9a1ce900 534 253p 39t 6 dsk16f 89 1 0 k0x9a1ce480 536 253p 106t 6 dsk16g 105 0 0 k0x9a1cf200 538 253p 106t 6 dsk16h 222 1 0 k0x06432d80 316 253p 39t 5 dsk2h 2 1 k0x9a1bdd40 420 253p 39t 5 dsk9e 224 3 0 k0x06433d40 322 253p 39t 5 dsk3c 231 1 0 k0x9a1b6d80 372 253p 39t 5 dsk6d 233 1 1 k0x06061200 272 253p 39t 5 dsk0b 249 0 0 k0x9a1ced80 540 253p 106t 6 dsk17a 265 0 0 k0x9a1cfb00 542 253p 39t 6 dsk17b 281 0 0 k0x9a1cf680 544 253p 39t 6 dsk17c 297 0 0 k0x9a1cfd40 546 253p 39t 6 dsk17d 313 0 0 k0x9a1d0900 548 253p 39t 6 dsk17e 319 0 0 NULL 0 253p 39t 8 floppy0h 329 0 0 k0x9a1d0480 550 253p 39t 6 dsk17f
.
.
.
The following sections in Chapter 6 of the
Logical Storage Manager
manual contains
errors in the steps that describe the
voldisk -f init <disk>
command:
6.4.3--Recovering Unstartable Nonredundant Volumes, step f
6.4.5.1--Recovering a RAID 5 Plex from Multiple Disk Failures, step f
6.4.5.2--Recovering a RAID 5 Log Plex, step f
6.5.5.1--Replacing a Failed Disk, step 6
In these sections, the steps involving the
voldisk
command do not cover the case of simple disks, sliced disks with a
puboffset, or simple disks with a
privoffset.
This release note contains the revisions to the relevant step in these sections.
The Logical Storage Manager manual will be corrected for the next release of Tru64 UNIX.
Step f in sections 6.4.3, 6.4.5.1, and 6.4.5.2, and step 6 in section 6.5.5.1 should read:
[f. | 6.] Label and initialize the new disk.
To use the default values for a new disk, do the following:
Apply a default disk label to the new disk:
# disklabel -rwn disk_access_name
Initialize the new disk for LSM:
# voldisksetup -i disk
If you have a customized disk label (Section 4.1.3) that you want to apply to the new disk, do the following:
Apply the disk label to the new disk:
# disklabel -R disk_access_name file
Initialize the disk for LSM, using the disk access name in the form of either
dskn
(for the entire disk) or
dsknp
(for a partition of the disk).
For a nopriv disk, enter:
# voldisk -f init disk_access_name
For a standard sliced disk, enter:
# voldisk -f init disk_access_name puboffset=16
Make sure the
puboffset
you specify is the same as
it was on the failed disk.
For a simple disk that occupies a partition that begins at
block 0 of the disk (for example the
a
or
c
partition), enter:
# voldisk -f init disk_access_name \
privoffset=16
For a simple disk that occupies a partition that does not
begin at block 0 of the disk (for example the
b
or
d
partition), enter:
# voldisk -f init disk_access_name
The following notes apply to the online help.
8.8.1 SysMan Menu
The notes in this section apply to the online help for the SysMam Menu
application.
8.8.1.1 Title Bar Is Incorrect
When you use the SysMan Menu's online help in the Common Desktop Environment (CDE), the title bar for the help window always displays the name of the first application for which you requested help.
Ignore the title bar.
The correct help volume is displayed in the help
window and the Volume label at the top of the window correctly identifies
the help volume.
8.8.1.2 Help on Item Sometimes Fails
The SysMan Menu's Help On Item buttons provide online help for the selected menu item. When running the SysMan Menu from a PC, from a web browser, or from the SysMan Station, Help On Item for certain tasks fails with an error when trying to access a URL such as the following:
http://your_machine:2301/SYSMAN/suitlet_help/html/en_US.ISO-8859-1/help_application/help_task.html
To avoid this problem, launch the specific task and select the online
help within the task itself.
You can also run the SysMan Menu on a terminal
or on an X11 display (for example,
sysman -display host:0.0)
and the help is displayed properly.
8.8.2 System Management Station
The notes in this section apply to the online help for the System Management
Station (SMS).
8.8.2.1 Online Help Window Does Not Maximize Automatically
If you open an
SMS online help window and minimize it, it does not automatically maximize when
you reselect Help from the SMS session.
You must manually maximize the Help
window to view the new help information.
8.8.3 Insight Manager
The introductory paragraph in the online help for the Compaq Insight Manager Configuration is incorrect; it should read as follows:
Use Compaq Insight Manager Configuration to enable or disable the Compaq Insight Manager agent daemon on your system.
The additional sentence currently in the online help regarding specifying passwords is not appropriate in this release.