Chapter 5 Documentation Issues

This chapter describes known documentation problems.

The name of this product is Solaris 8 10/01 , but code and path or package path names might 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 

"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 that is 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.

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.

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 is 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, or Solaris 8 Installation Supplement.

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

Some graphics in the CDE Users's Guide in the AnswerBook2 software 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. Except for 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

The current statement is incorrect.

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

This statement should read as follows.

The following Adaptec Ultra SCSI devices are now supported by the adp driver and not the cadp driver.

• AHA-2940AU

• AHA-2940U

• AHA-2940U Dual

• AHA-2940UW

• AHA-2940UW Dual

• AHA-2944UW

• AHA-3940AU

• AHA-3940AUW

• AHA-3940AUWD

• AHA-3940U

• AHA-3940UW

• 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

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 instead of the Priority field. The Priority bulleted item 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 that are 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 that were 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 that is required in the line that is added to the /etc/hostname.ip.tun0 file. Consequently, you must add the up parameter 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, do the following.

  • Change the symbol name to nfs_allow_preepoch_time.

  • Change the description to, "This symbol controls whether the NFS client or server allows file timestamps 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, do the following.

  • Change the default to 1. Ignore the comment about the directory name caching.

• For the nrnode symbol, do the following.

  • Change the default description to set to ncsize. By setting the variable to 1, you are effectively disabling the cache, not because an explicit check reveals whether or not the variable 1 but because you are creating a very small cache.

• For the nfs_write_error_interval symbol, do the following.

  • Change the description to, "This symbol controls how often NFS ENOSPC and EDQUOT write error messages are logged. The symbols 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, do the following.

• Change the default description to, "Defaults to 1024".

• Delete the authkerb_cachesz symbol entry.

• Delete the authkerb_win symbol entry.