Current statement:
The ATI RAGE PRO TURBO is the same video chip as the ATI RAGE PRO.
Should read as follows:
The ATI RAGE PRO TURBO is the same video chip as the ATI RAGE PRO. The ATI RAGE PRO TURBO support covers ATI video chips intended for non-LCD desktop monitors. These chips are identified by the markings, "3D RAGE PRO" or "RAGE PRO TURBO", followed by a "215R3xxxxx" number. The support does not cover RAGE LT PRO chips, which are identifed by the markings "RAGE LT PRO" followed by a "215LTxxxxx" number.
Current statement:
The Video Display Devices section lists the ATI RAGE 128 device as being supported.
Should read as follows:
Remove the ATI RAGE 128 entry from the list of video display devices supported 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
Solaris 8 (Intel Platform Edition) Device Configuration Guide
Solaris 8 (Intel Platform Edition) Hardware Compatibility List
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.
"Installation and Management" in What's New in the Solaris 8 Operating Environment incorrectly states that you can upgrade to the Solaris 8 operating environment using the Solaris Web Start 3.0 installation program on the Solaris 8 Installation CD. Use the Solaris Software 1 of 2 CD to upgrade to the Solaris 8 operating environment.
The version of the What's New in the Solaris 8 Operating Environment available through the kiosk on the Solaris 8 Installation CD has been superseded. For the latest version of What's New in the Solaris 8 Operating Environment, refer to the Solaris 8 Documentation CD or to http://docs.sun.com.
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 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.
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:
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 a 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: Sset 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.
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.
Delete the nfsreadmap symbol entry.
For the authdes_cachesz symbol:
Change the default description: Defaults to 1024.
Delete the authkerb_cachesz symbol entry.
Delete the authkerb_win symbol entry.