Chapter 5 Documentation Issues
This chapter describes known documentation problems. The following documentation issues have been added to this chapter since this document was published on the Solaris 8 6/00 Documentation CD and in the Installation Kiosk on the Solaris 8 6/00 Installation CD.
Note -
The name of this product is Solaris 8 6/00, 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
Document Affected: "Full Backup Commands" in Solaris 8 (SPARC Platform Edition) Installation Guide
The commands in Table 3-3 in "Full Backup Commands" in the 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 |
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:
- Traffic Class - 8 bit traffic class field.
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.
-
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.
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:
-
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 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:
-
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.
-
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:
-
Change the default description: Defaults to 1024.
-
Delete the authkerb_cachesz symbol entry.
-
Delete the authkerb_win symbol entry.
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.
Document Affected: sdtgwm(1) man page (4330198)
The -w option described in the man page sdtgwm(1) is not supported in the Solaris 8 6/00 operating environment.
Document Affected: Solaris Smart Cards Administration Guide (4296336)
The ocfserv daemon start and stop commands described in the Solaris Smart Cards Administration Guide do not exist.
To restart the ocfserv daemon, follow these steps.
-
Stop the inetd daemon.
# pkill inetd
-
Stop the ocfserv daemon.
# pkill ocfserv
-
Verify ocfserv daemon is stopped.
# pgrep ocfserv
-
Restart the inetd daemon.
# inetd -s
Document Affected: Solaris Smart Cards Administration Guide (4326607)
The Solaris Smart Cards Administration Guide supplies the wrong name for the Sun Smart Card Reader I for the smartcard -j option:
-j com.sun.opencard.terminal.scm.SCMstc.SCMStcCardTerminalFactory |
The Sun Smart Card Reader I for the smartcard -j option should read as follows:
-j com.sun.opencard.terminal.scm.SCMStc.SCMStcCardTerminalFactory |
Document Affected: "To Create a Boot Server on a Subnet" in Solaris 8 Advanced Installation Guide (4327931)
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" section of the Solaris 8 Advanced Installation Guide, skip Steps 6 through 15.
Documents Affected: "Improved Removable Media Management" in Solaris 8 System Administration Supplement and "Removable Media" in Solaris 8 User Supplement
The "Improved Removable Media Management" section of the Solaris 8 System Administration Supplement and the "Removable Media" section of the Solaris 8 User Supplement do not sufficiently describe how working with removable media has changed since the Solaris 8 release.
These sections should read as follows:
In the Solaris 8 6/00 release, volume manager (vold) actively manages all removable media devices. This means any attempt to access removable media with device names such as /dev/rdsk/cntndnsn or /dev/dsk/cntndnsn will be unsuccessful.
CDE's Removable Media Manager or the volume manager pathnames such as /cdrom0, /floppy, /rmdisk, /jaz0, or /zip0 are the only way to access the devices as long as volume manager (vold) is running.
You can also access removable media by their entries in the /vol/dev directory. For example:
/vol/dev/rdiskette0/volume-name for a floppy disk, or
/vol/dev/rdsk/cntndn/volume-name for a CD-ROM or removable hard disk
If a removable media device contains a removable medium, its alias appears in the /vol/dev/aliases directory as a symbolic link to its path in the /vol/dev directory. For example, if there's a floppy disk labeled test in floppy drive 0 and a CD labeled test in the CD-ROM drive at /dev/rdsk/c2t1d0, you will see the following output:
$ ls -l /vol/dev/aliases lrwxrwxrwx 1 root root 30 May 11 12:58 cdrom0 -> /vol/dev/rdsk/c2t1d0/test lrwxrwxrwx 1 root root 30 May 11 12:58 floppy0 -> /vol/dev/rdiskette0/test |
If you are unsure which device name to choose, use the eject -n command to display device names for all removable media devices. For example, use the device name on the right side of eject -n output to determine which device name to use with the fsck, mkfs, or newfs commands.
Accessing Jaz or Zip Drives
You can determine whether accessing your Jaz or Zip drives changes from previous Solaris releases depending on whether you upgrade or install the Solaris 8 6/00 release:
-
If you are upgrading to the Solaris 8 6/00 release from a previous Solaris release, you can continue to access your Jaz and Zip drives the same way as previous releases.
-
If you are freshly installing the Solaris 8 6/00 release, you will not be able to access your Jaz and Zip drives the same way as previous Solaris releases.
Follow the procedure below if you want to access your Jaz and Zip drives the same way as previous Solaris releases.
- © 2010, Oracle Corporation and/or its affiliates