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 commands in Table 3-3 in "Full Backup Commands" in Solaris 8 (SPARC Platform Edition) Installation Guide are incorrect. They should read as follows:Table 5-1 Backup Commands
To make a full backup on a
Use this command
Local cartridge tape drive
ufsdump 9ucf /dev/rmt/n files_to_backup
Remote cartridge tape drive
ufsdump 0ucf remote_host:/dev/rmt/n files_to_backup
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.
The -w option described in the man page sdtgwm(1) is not supported in the Solaris 8 10/00 operating environment.
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.