Solaris 8 (Intel Platform Edition) 7/01 Release Notes

Chapter 5 Documentation Issues

This chapter describes known documentation problems.


Note –

The name of this product is Solaris 8 7/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

“OCF Client Properties Overview” in Solaris Smart Cards Administration Guide

The following text from the “Valid and Default Card Types for Client Applications” section is incorrect and should be ignored:

For example, suppose you specify iButton, Cyberflex, and CardA as the validcards properties for Application B. Then you specify Cyberflex as the defaultcard property. If Application B accepts only its default card and the user tries to log in to Application B with CardA, then the system displays the message:


Waiting for Default Card 
Login to Application B is blocked until the user inserts a Cyberflex card into the reader.

“Setting Up a Smart Card (Tasks)” in Solaris Smart Cards Administration Guide

The “Example--Creating User Information on a Smart Card (Command Line) ”section has a property named username. The property name is incorrect. The property should read user.

“OCF Client Properties Overview” in Solaris Smart Cards Administration Guide and“Additional Client Configuration Tasks” in Solaris Smart Cards Administration Guide

The following note is missing from the “OCF Client Properties Overview” and “Additional Client Configuration Tasks” section :


Note –

Do not set the Re-authentication timeout to zero.


“Setting Up a Smart Card (Overview)” in Solaris Smart Cards Administration Guide

The following note is missing from the “Setting Up a Smart Card (Overview)” chapter:


Note –

Payflex cards do not support multiple profiles. Do not use Payflex cards in cases where a user needs to login to the desktop and one or more secure applications.


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 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:

are now supported by the adp driver instead of the cadp driver as stated in the following documents: 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:

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:

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.

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:

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:

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.