Documentation Notes

• Instructions for international edition of AFS are obsolete

  As noted in Summary of New Features, the OpenAFS Administration Guide and OpenAFS Administration Reference distinguish between United States and international editions of AFS, because the documents were produced before a relaxation of United States government export restrictions. AFS 3.6 includes just one edition. AFS customers in any country can ignore the documented distinction between editions and use the United States instructions if they choose.

• Clarification on obtaining technical support

  The AFS documents refer you to the AFS Product Support group for technical assistance with AFS problems and questions. This is intended to be a generic term. To learn how to obtain technical support, consult your AFS license agreement or other materials from your AFS vendor.

• Change to OpenAFS Quick Beginnings instructions for enabling AFS login on AIX machines

  If version 4.3.3.0 or higher of the AIX bos.rte.security fileset is installed (usually true on a machine using the AIX 4.3.3 kernel), edit the /usr/lib/security/methods.cfg file instead of the /etc/security/login.cfg file as documented in OpenAFS Quick Beginnings. The change affects Step 3 in the section titled Enabling AFS Login on AIX Systems in each of two chapters in OpenAFS Quick Beginnings: Installing the First AFS Machine and Installing Additional Client Machines. The corrected text follows.

  Create or edit the DCE and AFS stanzas in one of two files on the local disk:

  • The /usr/lib/security/methods.cfg file, if version 4.3.3.0 or higher of the AIX bos.rte.security fileset is installed on the machine (usually true on a machine using the AIX 4.3.3 kernel)

  • The /etc/security/login.cfg file, if an earlier version of the fileset is installed

  Edit the stanzas as follows:

  • In the DCE stanza, set the program attribute as indicated. If you use the AFS Authentication Server (kaserver process):

    DCE: program = /usr/vice/etc/afs_dynamic_auth

    If you use a Kerberos implementation of AFS authentication:

    DCE: program = /usr/vice/etc/afs_dynamic_kerbauth

  • In the AFS stanza, set the program attribute as indicated. If you use the AFS Authentication Server (kaserver process):

    AFS: program = /usr/vice/etc/afs_dynamic_auth

    If you use a Kerberos implementation of AFS authentication:

    AFS: program = /usr/vice/etc/afs_dynamic_kerbauth

• Change to OpenAFS Quick Beginnings instructions for replacing Solaris fsck program

  In two sections of OpenAFS Quick Beginnings, there are instructions for editing the /sbin/mountall script on Solaris machines as part of replacing the standard fsck program. The two sections are Configuring the AFS-modified fsck Program on Solaris Systems in the chapter about the first AFS machine and Getting Started on Solaris Systems in the chapter about additional server machines. If you use Solaris 7 and apply SunSoft Patch 10654, it replaces the /sbin/mountall script. In the replacement script, the appearance of one of the sections of code that you must alter is different than in the original script and as specified in OpenAFS Quick Beginnings, which is as follows:

  # For fsck purposes, we make a distinction between ufs and # other file systems # if [ "$fstype" = "ufs" ]; then ufs_fscklist="$ufs_fscklist $fsckdev" saveentry $fstype "$OPTIONS" $special $mountp continue fi

  In the replacement script, the code is instead similar to the following:

  # For fsck purposes, we make a distinction between ufs and # other file systems. Here we check that the file system is # not mounted using fsck -m before adding it to the list to # be checked # if [ "$fstype" = "ufs" ]; then /usr/sbin/fsck -m -F $fstype $fsckdev >/dev/null 2>&1 if [ $? != 33 ]; then ufs_fscklist="$ufs_fscklist $fsckdev" saveentry $fstype "$OPTIONS" $special $mountp continue else echo "$fsckdev already mounted" continue fi fi

  You still need to change the first if statement (the one directly after the comment) to check for both the UFS and AFS file system types, as specified in OpenAFS Quick Beginnings:

  if [ "$fstype" = "ufs" -o "$fstype" = "afs" ]; then

• Correction to OpenAFS Quick Beginnings instructions for accessing AFS documents

  The section of OpenAFS Quick Beginnings titled Storing AFS Documents in AFS (in the chapter about the first AFS machine) incorrectly describes the organization of the top-level Documentation directory on the AFS CD-ROM. It states that there is a subdirectory for each document format. Instead, there is a subdirectory for each language in which the documents are available, named using the following codes:

  • de_DE for German

  • en_US for United States English

  • es_ES for Spanish

  • ko_KR for Korean

  • pt_BR for Brazilian Portuguese

  • zh_CN for Simplified Chinese

  • zh_TW for Traditional Chinese

  In each language directory is a subdirectory for each available document format. In each format directory is a subdirectory for each document. For example, the path on the CD-ROM to the English-language HTML version of the OpenAFS Quick Beginnings is Documentation/en_US/HTML/QkBegin. Assuming that you want to install the documentation for one language only, substitute the following text for Step 5 in the instructions in Storing AFS Documents in AFS:

  Copy the AFS documents in one or more formats from the CD-ROM into subdirectories of the /afs/cellname/afsdoc directory. Repeat the commands for each format.

  # mkdir format_name # cd format_name # cp -rp /cdrom/Documentation/language_code/format .

  If you choose to store the HTML version of the documents in AFS, note that in addition to a subdirectory for each document there are several files with a .gif extension, which enable readers to move easily between sections of a document. The file called index.htm is an introductory HTML page that contains a hyperlink to each of the documents. For online viewing to work properly, these files must remain in the top-level HTML directory (the one named, for example, /afs/cellname/afsdoc/HTML).

• Revised reference page for NetRestrict files

  The OpenAFS Administration Guide and OpenAFS Administration Reference incorrectly state that the value 255 acts as a wildcard in IP addresses that appear in the NetRestrict file (client or server version). Wildcarding does not work and is not supported. For corrected documentation, see NetRestrict (client version) and NetRestrict (server version).

• Revised reference pages for backup commands and configuration file

  The OpenAFS Administration Guide and OpenAFS Administration Reference do not document the interoperation of the AFS Backup System and the Tivoli Storage Manager (TSM), because support for TSM was added after the documents were produced. For a complete description of the new TSM-related features and configuration procedures, see Support for Backup to TSM and the indicated reference pages:

  • backup deletedump

  • backup dumpinfo

  • backup status

  • CFG_tcid

• Revised reference page for vos delentry command

  The OpenAFS Administration Guide and OpenAFS Administration Reference incorrectly state that the vos delentry command accepts the name or volume ID number of any type of volume (read/write, read-only, or backup). In fact, it accepts only a read/write volume's name or ID. Because a single VLDB entry represents all versions of a volume (read/write, readonly, and backup), the command removes the entire entry even though only the read/write volume is specified. For complete documentation, see vos delentry.