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
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.
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.
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.
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.
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.
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.
The Adaptec Ultra devices are supported by the cadp driver and they support PCI hot-plugging.
Should read as follows:
Solaris 8 Reference Manual Collection adp(7D) and cadp(7D)
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:
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.
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.
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.
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 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.
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.
Several corrections apply to this section:
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.
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).
Change the default to 1. Ignore the comment about the directory name caching.
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.
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.
Delete the nfsreadmap symbol entry.
Change the default description: Defaults to 1024.
Delete the authkerb_cachesz symbol entry.
Delete the authkerb_win symbol entry.
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.
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.