Solaris 8 (Intel Platform Edition) 4/01 Release Notes Update

Chapter 5 Documentation Issues

This chapter describes known documentation problems.

The following documentation issues have been added to this chapter since this document was published on the Solaris 8 4/01 Documentation CD and in the Installation Kiosk on the Solaris 8 4/01 Installation CD.

Note –

The name of this product is Solaris 8 4/01, but code and path or package path names may use Solaris 2.8 or SunOS 5.8. Always follow the code or path as it is written.

Documentation Errata

Document Affected: “Video Display Devices” in Solaris 8 (Intel Platform Edition) 1/01 Hardware Compatibility List

The “Video Display Devices” in Solaris 8 (Intel Platform Edition) 1/01 Hardware Compatibility List incorrectly lists support for the ATI RAGE 128 and NVIDIA TNT2 M64 video devices. These devices are not supported in the Solaris 8 1/01 and 4/01 operating environments.

Workaround: After you install, or upgrade, apply patch 109401 to add support for the ATI RAGE 128 and NVIDIA TNT2 M64 video devices.

Document Affected: “What's New at a Glance” in Solaris 8 System Administration Supplement

The “What's New at a Glance” in Solaris 8 System Administration Supplement on the Solaris 8 4/01 Documentation CD describes Web Based Enterprise Management (WBEM) feature enhancements in the 10/00 and 1/01 updates, but omits a description of WBEM feature enhancements made in the 4/01 update release. For a description of the 4/01 WBEM feature enhancements, see the Solaris 8 4/01“What's New for System Administrators” in Solaris 8 4/01 What's New on http://docs.sun.com.

Document Affected: Solaris Smart Cards Administration Guide in the Solaris 8 System Administrator Collection

The latest revised version of the Solaris Smart Cards Administration Guide was inadvertently left out of the Solaris 8 System Administrator Collection on the English distribution of the Solaris 8 4/01 Documentation CD. The collection is shipping with the Solaris 8 1/01 version of the Solaris Smart Cards Administration Guide. For the latest revised version, see the Solaris Smart Cards Administration Guide in the Solaris 8 System Administrator Collection on http://docs.sun.com.

Document Affected: Localized New Features List (4389948)

The localized New Features List are not contained in the Installation Kiosk.

Workaround: For a localized list, see “What's New at a Glance” in Solaris 8 Desktop User Supplement, Solaris 8 System Administration Supplement, Solaris 8 Software Developer Supplement, Solaris 8 Installation Supplement.

Document Affected: CDE User's Guide in AnswerBook2 (4356456)

Some graphics in the CDE Users's Guide in AnswerBook2 are unreadable in the Spanish, Italian and German locales.

Workaround: Refer to the CDE User's Guide on http://docs.sun.com for readable graphics.

Documents Affected: AnswerBook2 Help Collection

The AnswerBook2 software has been upgraded to Version 1.4.3, but the documentation still refers to Version 1.4.2. Aside from the number issue, the documentation is correct.

Documents Affected: “Adaptec AHA-2940AU, 2940U, 2940U Dual, 2940UW, 2940UW Dual, 2940U2, 2940U2B, 2940U2W, 2944UW, 2950U2B, 3940AU, 3940AUW, 3940AUWD, 3940U, 3940UW, 3944AUWD, 3950U2B HBAs” in the Solaris 8 (Intel Platform Edition) Device Configuration Guide, adp(7D) and cadp(7D) in the Solaris 8 Reference Manual Collection, and What's New in the Solaris 8 Operating Environment

Current statement:

The Adaptec Ultra devices are supported by the cadp driver and they support PCI hot-plugging.

Should read as follows:

The Adaptec Ultra SCSI devices:

AHA-2940AU
AHA-2940U
AHA-2940U Dual
AHA-2940UW
AHA-2940UW Dual
AHA-2944UW
AHA-3940AU
AHA-3940AUW
AHA-3940AUWD
AHA-3940U
AHA-3940UW

are now supported by the adp driver instead of the cadp driver as stated in the following documents:

Solaris 8 Reference Manual Collection adp(7D) and cadp(7D)
What's New in the Solaris 8 Operating Environment
Solaris 8 (Intel Platform Edition) Device Configuration Guide

PCI hot-plugging is not supported for these Ultra SCSI devices. However, the Ultra 2 SCSI devices supported by the cadp driver support PCI hot-plugging.

Document Affected: Solaris 8 (Intel Platform Edition) Device Configuration Guide

The ninth and tenth bulleted items in the “Known Problems and Limitations” section of the “Adaptec AHA-2940AU, 2940U, 2940U Dual, 2940UW, 2940UW Dual, 2940U2, 2940U2B, 2940U2W, 2944UW, 2950U2B, 3940AU, 3940AUW, 3940AUWD, 3940U, 3940UW, 3944AUWD, 3950U2B HBAs” in the Solaris 8 (Intel Platform Edition) Device Configuration Guide should read as follows:

When setting up a SCSI bus configuration, avoid connecting wide devices to a narrow bus. However, if you have such a configuration, add the following entry to the cadp.conf file:
target<n>-scsi-options=0x1df8
where <n> is the target ID of the wide device on the narrow bus. This entry disables wide negotiation for the specified target. Also ensure that the upper 8 bits of the bus are properly terminated at both ends of the SCSI chain.
If you experience installation problems on systems with Intel 440BX/440GX motherboards, upgrade the motherboard BIOS with the latest revision.

Document Affected: “IPv6 Header Format” in System Administration Guide, Volume 3

The 4-bit Priority field description reflects RFC 1883, which has been obsoleted by RFC 2460 (Solaris 8 implements RFC 2460). Consequently, the Priority field has been replaced by an 8-bit Traffic Class field. The IPv6 Header Format figure should identify the Traffic Class field in place of the Priority field. The Priority bullet on this page should also be replaced by the following Traffic Class description:

Traffic Class - 8 bit traffic class field.

This new value also reduces the number of bits allocated to the "Flow Label" field to 20 bits.

Document Affected: “Priority Values” in System Administration Guide, Volume 3

The 4-bit Priority field description reflects RFC 1883, which has been obsoleted by RFC 2460 (Solaris 8 implements RFC 2460). Consequently, the Priority field has been replaced by the 8-bit Traffic Class field. The Priority section should be replaced by the following Traffic Classes section.

Traffic Classes

Originating nodes and forwarding routers can use the 8-bit Traffic Class field in the IPv6 header to identify and distinguish between different classes or priorities of IPv6 packets.

The following general requirements apply to the Traffic Class field.

The service interface to the IPv6 service within a node must provide a means for an upper-layer protocol to supply the value of the Traffic Class bits in packets originated by that upper-layer protocol. The default value must be zero for all 8 bits.
Nodes that support a specific use of some or all of the Traffic Class bits can change the value of those bits in packets that they originate, forward, or receive, as required for that specific use. Nodes should ignore and leave unchanged any bits of the Traffic Class field for which they do not support a specific use.

Document Affected: “Implementing IPsec” in System Administration Guide, Volume 3

Step 10c in this procedure incorrectly omits the addition of the up parameter required in the line added to the /etc/hostname.ip.tun0 file. Consequently, the up parameter must be added at the end of the line entry in this step.

Document Affected: “NFS Parameters for the nfs Module” in System Administration Guide, Volume 3 (4299091)

Several corrections apply to this section:

For the nfs_32_time_ok symbol:
- Change the symbol name to: nfs_allow_preepoch_time.
- Change the description to: This symbol controls whether the NFS client or server allows file time stamps that precede 1970.
- No change to the default description.
- Delete the nfs_acl_cache symbol entry.
Add an nfs_disable_rddir_cache symbol entry.
- Description: Some servers do not properly update the attributes of the directory when changes are made. To allow interoperability with these broken servers, set this variable to disable the readdir cache.
- Default: Set to off(0).
For the nfs_lookup_neg_cache and nfs3_lookup_neg_cache symbols:
- Change the default to 1. Ignore the comment about the directory name caching.
For the nrnode symbol:
- Change the default description to: set to ncsize. By setting the variable to 1 you are effectively disabling the cache, not because there is an explicit check to see whether or not it is 1 but because you are creating a very small cache.
For the nfs_write_error_interval symbol:
- Change the description: This symbol controls how often NFS ENOSPC and EDQUOT write error messages are logged. Its units are in seconds.
- No change to the default description.

Document Affected: “NFS Parameters for the nfs Module” in System Administration Guide, Volume 3 (4299091)

Delete the nfsreadmap symbol entry.

Document Affected: “NFS Parameters for rpcsec Parameters” in System Administration Guide, Volume 3 (4299091)

For the authdes_cachesz symbol:

Change the default description: Defaults to 1024.
Delete the authkerb_cachesz symbol entry.
Delete the authkerb_win symbol entry.

Document Affected: “Mobile IP Mobility Agent Status” and “Displaying Mobility Agent Status” in Mobile IP Administration Guide

Current statement:

Use the mipagentstat(1M) command's -b option to display the home agent's binding table.

Should read as follows:

Use the mipagentstat(1M) command's -h option to display the home agent's binding table.

Document Affected: “Managing Mobile IP” and “Deploying Mobile IP” in Mobile IP Administration Guide

The Address Section in the Mobile IP configuration file has a parameter named Default-Node. This parameter name is incorrect. Node-Default is the correct parameter name.

Document Affected: “To Create a Boot Server on a Subnet" in “Creating an Install Server and a Boot Server” in Solaris 8 Advanced Installation Guide (4327931)

The instructions to create a boot server over a subnet incorrectly direct you to use the Solaris 8 Software 2 of 2 CD and the Solaris 8 Languages CD. If you follow these instructions, the following error message is displayed.

An existing install server cannot be found at /image_name.
  This tool can only add packages to an install server that already exists.

When following the instructions "To Create a Boot Server on a Subnet" in the“Creating an Install Server and a Boot Server” in Solaris 8 Advanced Installation Guide, skip Steps 6 through 15.