</itemizedlist></para>
<para>You must make the following configuration decisions while installing the first AFS machine. To speed the installation
- itself, it is best to make the decisions before beginning. See the chapter in the <emphasis>IBM AFS Administration
+ itself, it is best to make the decisions before beginning. See the chapter in the <emphasis>OpenAFS Administration
Guide</emphasis> about issues in cell administration and configuration for detailed guidelines. <indexterm>
<primary>cell name</primary>
<para>These instructions configure the first AFS machine as a <emphasis>database server machine</emphasis>, the <emphasis>binary
distribution machine</emphasis> for its system type, and the cell's <emphasis>system control machine</emphasis>. For a
- description of these roles, see the <emphasis>IBM AFS Administration Guide</emphasis>.</para>
+ description of these roles, see the <emphasis>OpenAFS Administration Guide</emphasis>.</para>
<para>Installation of additional machines is simplest if the first machine has the lowest IP address of any database server
machine you currently plan to install. If you later install database server functionality on a machine with a lower IP address,
role="bold">/vicepa</emphasis> through <emphasis role="bold">/vicepz</emphasis>, the 27th one is mounted on the <emphasis
role="bold">/vicepaa</emphasis> directory, and so on through <emphasis role="bold">/vicepaz</emphasis> and <emphasis
role="bold">/vicepba</emphasis>, continuing up to the index corresponding to the maximum number of server partitions
- supported in the current version of AFS (which is specified in the <emphasis>IBM AFS Release Notes</emphasis>).</para>
+ supported in the current version of AFS (which is specified in the <emphasis>OpenAFS Release Notes</emphasis>).</para>
<para>The <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server
machine's root directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is
not an acceptable directory location).</para>
<para>You can also add or remove server partitions on an existing file server machine. For instructions, see the chapter
- in the <emphasis>IBM AFS Administration Guide</emphasis> about maintaining server machines.</para>
+ in the <emphasis>OpenAFS Administration Guide</emphasis> about maintaining server machines.</para>
<note>
<para>Not all file system types supported by an operating system are necessarily supported as AFS server partitions. For
- possible restrictions, see the <emphasis>IBM AFS Release Notes</emphasis>.</para>
+ possible restrictions, see the <emphasis>OpenAFS Release Notes</emphasis>.</para>
</note>
</listitem>
an AFS token as they log into the local file system. Using AFS is simpler and more convenient for your users if you make
the modifications on all client machines. Otherwise, users must perform a two-step login procedure (login to the local
file system and then issue the <emphasis role="bold">klog</emphasis> command). For further discussion of AFS
- authentication, see the chapter in the <emphasis>IBM AFS Administration Guide</emphasis> about cell configuration and
+ authentication, see the chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell configuration and
administration issues.</para>
</listitem>
</itemizedlist></para>
</listitem>
<listitem>
- <para><link linkend="HDRWQ26">Getting Started on Digital UNIX Systems</link></para>
- </listitem>
-
- <listitem>
<para><link linkend="HDRWQ31">Getting Started on HP-UX Systems</link></para>
</listitem>
<sect2 id="HDRWQ22">
<title>Loading AFS into the AIX Kernel</title>
- <para>The AIX kernel extension facility is the dynamic kernel loader provided by IBM Corporation. AIX does not support
- incorporation of AFS modifications during a kernel build.</para>
+ <para>The AIX kernel extension facility is the dynamic kernel loader
+ provided by IBM Corporation. AIX does not support incorporation of
+ AFS modifications during a kernel build.</para>
<para>For AFS to function correctly, the kernel extension facility must run each time the machine reboots, so the AFS
initialization script (included in the AFS distribution) invokes it automatically. In this section you copy the script to the
</sect2>
</sect1>
- <sect1 id="HDRWQ26">
- <title>Getting Started on Digital UNIX Systems</title>
-
- <para>Begin by either building AFS modifications into a new static kernel or by setting up to dynamically load the AFS kernel
- module. Then create partitions for storing AFS volumes, and replace the Digital UNIX <emphasis role="bold">fsck</emphasis>
- program with a version that correctly handles AFS volumes. If the machine is to remain an AFS client machine, incorporate AFS
- into the machine's Security Integration Architecture (SIA) matrix. <indexterm>
- <primary>incorporating AFS kernel extensions</primary>
-
- <secondary>first AFS machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm> <indexterm>
- <primary>AFS kernel extensions</primary>
-
- <secondary>on first AFS machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm> <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS kernel extensions</secondary>
-
- <tertiary>on Digital UNIX</tertiary>
- </indexterm> <indexterm>
- <primary>Digital UNIX</primary>
-
- <secondary>AFS-modified kernel</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm></para>
-
- <sect2 id="HDRWQ27a">
- <title>Loading AFS into the Digital UNIX Kernel</title>
-
- <para>The <emphasis role="bold">sysconfig</emphasis> program is the dynamic kernel loader provided for Digital UNIX
- systems.</para>
-
- <para>For AFS to function correctly, the <emphasis role="bold">sysconfig</emphasis> program must run each time the machine
- reboots, so the AFS initialization script (included on the AFS CD-ROM) invokes it automatically. In this section you copy the
- appropriate AFS library file to the location where the <emphasis role="bold">sysconfig</emphasis> program accesses it and then
- run the script.</para>
-
- <para>Mount the AFS CD-ROM for Digital UNIX on the local <emphasis role="bold">/cdrom</emphasis> directory. For instructions
- on mounting CD-ROMs (either locally or remotely via NFS), see your Digital UNIX documentation. Then change directory as
- indicated.</para>
-
- <programlisting>
- # <emphasis role="bold">cd /cdrom/alpha_dux40/root.client</emphasis>
-</programlisting>
-
- <para>Copy the AFS initialization script to the local directory for initialization files (by convention, <emphasis
- role="bold">/sbin/init.d</emphasis> on Digital UNIX machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
- extension as you copy the script.</para>
-
- <programlisting>
- # <emphasis role="bold">cp usr/vice/etc/afs.rc /sbin/init.d/afs</emphasis>
-</programlisting>
-
- <para>Copy the AFS kernel module to the local <emphasis role="bold">/subsys</emphasis> directory.</para>
-
- <programlisting>
- # <emphasis role="bold">cp bin/afs.mod /subsys/afs.mod</emphasis>
-</programlisting>
-
- <para>Set up the system to load the module at startup.</para>
-
- <programlisting>
- # <emphasis role="bold">/sbin/init.d/autosysconfig add afs</emphasis>
-</programlisting>
-
- <para>Reboot the machine to start using the new kernel, and login again as the superuser <emphasis
- role="bold">root</emphasis>.</para>
-
- <programlisting>
- # <emphasis role="bold">cd /</emphasis>
- # <emphasis role="bold">shutdown -r now</emphasis>
- login: <emphasis role="bold">root</emphasis>
- Password: <replaceable>root_password</replaceable>
-</programlisting>
- </sect2>
-
- <sect2 id="HDRWQ27">
- <title>Building AFS into the Digital UNIX Kernel</title>
-
- <para>Use the following instructions to build AFS modifications into the kernel on a Digital UNIX system. <orderedlist>
- <listitem>
- <para>Create a copy called <emphasis role="bold">AFS</emphasis> of the basic kernel configuration file included in the
- Digital UNIX distribution as <emphasis role="bold">/usr/sys/conf/</emphasis><replaceable>machine_name</replaceable>,
- where <replaceable>machine_name</replaceable> is the machine's hostname in all uppercase letters. <programlisting>
- # <emphasis role="bold">cd /usr/sys/conf</emphasis>
- # <emphasis role="bold">cp</emphasis> <replaceable>machine_name</replaceable> <emphasis role="bold">AFS</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Add AFS to the list of options in the configuration file you created in the previous step, so that the result
- looks like the following: <programlisting>
- . .
- . .
- options UFS
- options NFS
- options AFS
- . .
- . .
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Add an entry for AFS to two places in the file <emphasis role="bold">/usr/sys/conf/files</emphasis>. <itemizedlist>
- <listitem>
- <para>Add a line for AFS to the list of <computeroutput>OPTIONS</computeroutput>, so that the result looks like
- the following: <programlisting>
- . . .
- . . .
- OPTIONS/nfs optional nfs
- OPTIONS/afs optional afs
- OPTIONS/nfs_server optional nfs_server
- . . .
- . . .
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Add an entry for AFS to the list of <computeroutput>MODULES</computeroutput>, so that the result looks like
- the following: <programlisting>
- . . . .
- . . . .
- #
- MODULE/nfs_server optional nfs_server Binary
- nfs/nfs_server.c module nfs_server optimize -g3
- nfs/nfs3_server.c module nfs_server optimize -g3
- #
- MODULE/afs optional afs Binary
- afs/libafs.c module afs
- #
-</programlisting></para>
- </listitem>
- </itemizedlist></para>
- </listitem>
-
- <listitem>
- <para>Add an entry for AFS to two places in the file <emphasis role="bold">/usr/sys/vfs/vfs_conf.c</emphasis>.
- <itemizedlist>
- <listitem>
- <para>Add AFS to the list of defined file systems, so that the result looks like the following: <programlisting>
- . .
- . .
- #include <afs.h>
- #if defined(AFS) && AFS
- extern struct vfsops afs_vfsops;
- #endif
- . .
- . .
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Put a declaration for AFS in the <emphasis role="bold">vfssw[]</emphasis> table's MOUNT_ADDON slot, so that
- the result looks like the following: <programlisting>
- . . .
- . . .
- &fdfs_vfsops, "fdfs", /* 12 = MOUNT_FDFS */
- #if defined(AFS)
- &afs_vfsops, "afs",
- #else
- (struct vfsops *)0, "", /* 13 = MOUNT_ADDON */
- #endif
- #if NFS && INFS_DYNAMIC
- &nfs3_vfsops, "nfsv3", /* 14 = MOUNT_NFS3 */
-</programlisting></para>
- </listitem>
- </itemizedlist></para>
- </listitem>
-
- <listitem>
- <para>Mount the AFS CD-ROM for Digital UNIX on the local <emphasis role="bold">/cdrom</emphasis> directory. For
- instructions on mounting CD-ROMs (either locally or remotely via NFS), see your Digital UNIX documentation. Then change
- directory as indicated. <programlisting>
- # <emphasis role="bold">cd /cdrom/alpha_dux40/root.client</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS initialization script to the local directory for initialization files (by convention, <emphasis
- role="bold">/sbin/init.d</emphasis> on Digital UNIX machines). Note the removal of the <emphasis
- role="bold">.rc</emphasis> extension as you copy the script. <programlisting>
- # <emphasis role="bold">cp usr/vice/etc/afs.rc /sbin/init.d/afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS kernel module to the local <emphasis role="bold">/usr/sys/BINARY</emphasis> directory.</para>
-
- <para>If the machine's kernel supports NFS server functionality:</para>
-
- <programlisting>
- # <emphasis role="bold">cp bin/libafs.o /usr/sys/BINARY/afs.mod</emphasis>
-</programlisting>
-
- <para>If the machine's kernel does not support NFS server functionality:</para>
-
- <programlisting>
- # <emphasis role="bold">cp bin/libafs.nonfs.o /usr/sys/BINARY/afs.mod</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Configure and build the kernel. Respond to any prompts by pressing <<emphasis
- role="bold">Return</emphasis>>. The resulting kernel resides in the file <emphasis
- role="bold">/sys/AFS/vmunix</emphasis>. <programlisting>
- # <emphasis role="bold">doconfig -c AFS</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Rename the existing kernel file and copy the new, AFS-modified file to the standard location. <programlisting>
- # <emphasis role="bold">mv /vmunix /vmunix_noafs</emphasis>
- # <emphasis role="bold">cp /sys/AFS/vmunix /vmunix</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Reboot the machine to start using the new kernel, and login again as the superuser <emphasis
- role="bold">root</emphasis>. <programlisting>
- # <emphasis role="bold">cd /</emphasis>
- # <emphasis role="bold">shutdown -r now</emphasis>
- login: <emphasis role="bold">root</emphasis>
- Password: <replaceable>root_password</replaceable>
-</programlisting></para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>configuring</primary>
-
- <secondary>AFS server partition on first AFS machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS server partition</primary>
-
- <secondary>configuring on first AFS machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS server partition</secondary>
-
- <tertiary>on Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>Digital UNIX</primary>
-
- <secondary>AFS server partition</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ28">
- <title>Configuring Server Partitions on Digital UNIX Systems</title>
-
- <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
- server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
- <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
- role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
- directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
- directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific Procedures</link>.
- <orderedlist>
- <listitem>
- <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
- partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
- # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Add a line with the following format to the file systems registry file, <emphasis
- role="bold">/etc/fstab</emphasis>, for each directory just created. The entry maps the directory name to the disk
- partition to be mounted on it. <programlisting>
- /dev/<replaceable>disk</replaceable> /vicep<replaceable>xx</replaceable> ufs rw 0 2
-</programlisting></para>
-
- <para>The following is an example for the first partition being configured.</para>
-
- <programlisting>
- /dev/rz3a /vicepa ufs rw 0 2
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Create a file system on each partition that is to be mounted at a <emphasis
- role="bold">/vicep</emphasis><replaceable>xx</replaceable> directory. The following command is probably appropriate, but
- consult the Digital UNIX documentation for more information. <programlisting>
- # <emphasis role="bold">newfs -v /dev/</emphasis><replaceable>disk</replaceable>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Mount each partition by issuing either the <emphasis role="bold">mount -a</emphasis> command to mount all
- partitions at once or the <emphasis role="bold">mount</emphasis> command to mount each partition in turn.</para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>replacing fsck program</primary>
-
- <secondary>first AFS machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>fsck program</primary>
-
- <secondary>on first AFS machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>fsck program</secondary>
-
- <tertiary>on Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>Digital UNIX</primary>
-
- <secondary>fsck program</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ29">
- <title>Replacing the fsck Program on Digital UNIX Systems</title>
-
- <para>In this section, you make modifications to guarantee that the appropriate <emphasis role="bold">fsck</emphasis> program
- runs on AFS server partitions. The <emphasis role="bold">fsck</emphasis> program provided with the operating system must never
- run on AFS server partitions. Because it does not recognize the structures that the File Server uses to organize volume data,
- it removes all of the data. To repeat:</para>
-
- <para><emphasis role="bold">Never run the standard fsck program on AFS server partitions. It discards AFS
- volumes.</emphasis></para>
-
- <para>On Digital UNIX systems, the files <emphasis role="bold">/sbin/fsck</emphasis> and <emphasis
- role="bold">/usr/sbin/fsck</emphasis> are driver programs. Rather than replacing either of them, you replace the actual binary
- included in the Digital UNIX distribution as <emphasis role="bold">/sbin/ufs_fsck</emphasis> and <emphasis
- role="bold">/usr/sbin/ufs_fsck</emphasis>. <orderedlist>
- <listitem>
- <para>Install the <emphasis role="bold">vfsck</emphasis> binary to the <emphasis role="bold">/sbin</emphasis> and
- <emphasis role="bold">/usr/sbin</emphasis> directories. The AFS CD-ROM must still be mounted at the <emphasis
- role="bold">/cdrom</emphasis> directory. <programlisting>
- # <emphasis role="bold">cd /cdrom/alpha_dux40/root.server/etc</emphasis>
- # <emphasis role="bold">cp vfsck /sbin/vfsck</emphasis>
- # <emphasis role="bold">cp vfsck /usr/sbin/vfsck</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Rename the Digital UNIX <emphasis role="bold">fsck</emphasis> binaries and create symbolic links to the <emphasis
- role="bold">vfsck</emphasis> program. <programlisting>
- # <emphasis role="bold">cd /sbin</emphasis>
- # <emphasis role="bold">mv ufs_fsck ufs_fsck.noafs</emphasis>
- # <emphasis role="bold">ln -s vfsck ufs_fsck</emphasis>
- # <emphasis role="bold">cd /usr/sbin</emphasis>
- # <emphasis role="bold">mv ufs_fsck ufs_fsck.noafs</emphasis>
- # <emphasis role="bold">ln -s vfsck ufs_fsck</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
- linkend="HDRWQ30">Enabling AFS Login on Digital UNIX Systems</link>. Otherwise, proceed to <link
- linkend="HDRWQ50">Starting the BOS Server</link>.</para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>enabling AFS login</primary>
-
- <secondary>file server machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS login</primary>
-
- <secondary>on file server machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS login</secondary>
-
- <tertiary>on Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>Digital UNIX</primary>
-
- <secondary>AFS login</secondary>
-
- <tertiary>on file server machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>SIA (Digital UNIX)</primary>
-
- <secondary>file server machine</secondary>
- </indexterm>
-
- <indexterm>
- <primary>Security Integration Architecture</primary>
-
- <see>SIA</see>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ30">
- <title>Enabling AFS Login on Digital UNIX Systems</title>
-
- <note>
- <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
- proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
- </note>
-
- <para>On Digital UNIX systems, the AFS initialization script automatically incorporates the AFS authentication library file
- into the Security Integration Architecture (SIA) matrix on the machine, so that users with AFS accounts obtain a token at
- login. In this section you copy the library file to the appropriate location.</para>
-
- <para>For more information on SIA, see the Digital UNIX reference page for <emphasis role="bold">matrix.conf</emphasis>, or
- consult the section on security in your Digital UNIX documentation.</para>
-
- <note>
- <para>If the machine runs both the DCE and AFS client software, AFS must start after DCE. Consult the AFS initialization
- script for suggested symbolic links to create for correct ordering. Also, the system startup script order must initialize
- SIA before any long-running process that uses authentication.</para>
- </note>
-
- <para>Perform the following steps to enable AFS login. <orderedlist>
- <listitem>
- <para>Mount the AFS CD-ROM for Digital UNIX on the local <emphasis role="bold">/cdrom</emphasis> directory, if it is not
- already. Change directory as indicated. <programlisting>
- # <emphasis role="bold">cd /cdrom/alpha_dux40/lib/afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the appropriate AFS authentication library file to the local <emphasis role="bold">/usr/shlib</emphasis>
- directory.</para>
-
- <para>If you use the AFS Authentication Server (<emphasis role="bold">kaserver</emphasis> process) in the cell:</para>
-
- <programlisting>
- # <emphasis role="bold">cp libafssiad.so /usr/shlib</emphasis>
-</programlisting>
-
- <para>If you use a Kerberos implementation of AFS authentication, rename the library file as you copy it:</para>
-
- <programlisting>
- # <emphasis role="bold">cp libafssiad.krb.so /usr/shlib/libafssiad.so</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Proceed to <link linkend="HDRWQ50">Starting the BOS Server</link> (or if referring to these instructions while
- installing an additional file server machine, return to <link linkend="HDRWQ108">Starting Server
- Programs</link>).</para>
- </listitem>
- </orderedlist></para>
- </sect2>
- </sect1>
-
<sect1 id="HDRWQ31">
<title>Getting Started on HP-UX Systems</title>
<para>The instructions specify that you mark each entry as <computeroutput>optional</computeroutput>. However, marking some
modules as optional can mean that they grant access to the corresponding service even when the user does not meet all of the
module's requirements. In some operating system revisions, for example, if you mark as optional the module that controls
- login via a dial-up connection, it allows users to login without providing a password. See the <emphasis>IBM AFS Release
+ login via a dial-up connection, it allows users to login without providing a password. See the <emphasis>OpenAFS Release
Notes</emphasis> for a discussion of any limitations that apply to this operating system.</para>
<para>Also, with some operating system versions you must install patches for PAM to interact correctly with certain
- authentication programs. For details, see the <emphasis>IBM AFS Release Notes</emphasis>.</para>
+ authentication programs. For details, see the <emphasis>OpenAFS Release Notes</emphasis>.</para>
</note>
<para>The recommended AFS-related entries in the PAM configuration file make use of one or more of the following three
<listitem>
<para>Issue the <emphasis role="bold">uname -m</emphasis> command to determine the machine's CPU board type. The <emphasis
role="bold">IP</emphasis><replaceable>xx</replaceable> value in the output must match one of the supported CPU board types
- listed in the <emphasis>IBM AFS Release Notes</emphasis> for the current version of AFS. <programlisting>
+ listed in the <emphasis>OpenAFS Release Notes</emphasis> for the current version of AFS. <programlisting>
# <emphasis role="bold">uname -m</emphasis>
</programlisting></para>
</listitem>
role="bold">xdm</emphasis> login program both automatically grant an AFS token when AFS is incorporated into the machine's
kernel. However, some IRIX distributions use another login utility by default, and it does not necessarily incorporate the
required AFS modifications. If that is the case, you must disable the default utility if you want AFS users to obtain AFS
- tokens at login. For further discussion, see the <emphasis>IBM AFS Release Notes</emphasis>.</para>
+ tokens at login. For further discussion, see the <emphasis>OpenAFS Release Notes</emphasis>.</para>
<para>If you configure the machine to use an AFS-modified login utility, then the <emphasis
role="bold">afsauthlib.so</emphasis> and <emphasis role="bold">afskauthlib.so</emphasis> files (included in the AFS
<para>The instructions specify that you mark each entry as <computeroutput>optional</computeroutput>. However, marking some
modules as optional can mean that they grant access to the corresponding service even when the user does not meet all of the
module's requirements. In some operating system revisions, for example, if you mark as optional the module that controls
- login via a dial-up connection, it allows users to login without providing a password. See the <emphasis>IBM AFS Release
+ login via a dial-up connection, it allows users to login without providing a password. See the <emphasis>OpenAFS Release
Notes</emphasis> for a discussion of any limitations that apply to this operating system.</para>
<para>Also, with some operating system versions you must install patches for PAM to interact correctly with certain
- authentication programs. For details, see the <emphasis>IBM AFS Release Notes</emphasis>.</para>
+ authentication programs. For details, see the <emphasis>OpenAFS Release Notes</emphasis>.</para>
</note>
<para>The recommended AFS-related entries in the PAM configuration file make use of one or more of the following three
<para>As it initializes for the first time, the BOS Server creates the following directories and files, setting the owner to the
local superuser <emphasis role="bold">root</emphasis> and the mode bits to limit the ability to write (and in some cases, read)
- them. For a description of the contents and function of these directories and files, see the chapter in the <emphasis>IBM AFS
+ them. For a description of the contents and function of these directories and files, see the chapter in the <emphasis>OpenAFS
Administration Guide</emphasis> about administering server machines. For further discussion of the mode bit settings, see <link
linkend="HDRWQ96">Protecting Sensitive AFS Directories</link>. <indexterm>
<primary>CD-ROM</primary>
<sect1 id="HDRWQ51">
<title>Defining Cell Name and Membership for Server Processes</title>
- <para>Now assign your cell's name. The chapter in the <emphasis>IBM AFS Administration Guide</emphasis> about cell configuration
+ <para>Now assign your cell's name. The chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell configuration
and administration issues discusses the important considerations, explains why changing the name is difficult, and outlines the
restrictions on name format. Two of the most important restrictions are that the name cannot include uppercase letters or more
than 64 characters.</para>
<para>The entry for AFS server processes, called <emphasis role="bold">afs</emphasis>. No user logs in under this
identity, but the Authentication Server's Ticket Granting Service (TGS) module uses the associated key to encrypt the
server tickets that it grants to AFS clients for presentation to server processes during mutual authentication. (The
- chapter in the <emphasis>IBM AFS Administration Guide</emphasis> about cell configuration and administration describes the
+ chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell configuration and administration describes the
role of server encryption keys in mutual authentication.)</para>
<para>In Step <link linkend="LIWQ58">7</link>, you also place the initial AFS server encryption key into the <emphasis
commands in all of the AFS suites.</para>
<para>The following instructions do not configure all of the security mechanisms related to the AFS Backup System. See the
- chapter in the <emphasis>IBM AFS Administration Guide</emphasis> about configuring the Backup System. <orderedlist>
+ chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about configuring the Backup System. <orderedlist>
<indexterm>
<primary>commands</primary>
their communications from eavesdropping to some degree.</para>
<para>For more information on the <emphasis role="bold">upclient</emphasis> and <emphasis role="bold">upserver</emphasis>
- processes, see their reference pages in the <emphasis>IBM AFS Administration Reference</emphasis>. The commands appear on
+ processes, see their reference pages in the <emphasis>OpenAFS Administration Reference</emphasis>. The commands appear on
multiple lines here only for legibility. <orderedlist>
<listitem>
<para>Issue the <emphasis role="bold">bos create</emphasis> command to start the <emphasis role="bold">upserver</emphasis>
<title>Starting the Controller for NTPD</title>
<para>Keeping the clocks on all server and client machines in your cell synchronized is crucial to several functions, and in
- particular to the correct operation of AFS's distributed database technology, Ubik. The chapter in the <emphasis>IBM AFS
+ particular to the correct operation of AFS's distributed database technology, Ubik. The chapter in the <emphasis>OpenAFS
Administration Guide</emphasis> about administering server machines explains how time skew can disturb Ubik's performance and
cause service outages in your cell.</para>
<note>
<para>Do not run the <emphasis role="bold">runntp</emphasis> process if NTPD or another time synchronization protocol is
already running on the machine. Some versions of some operating systems run a time synchronization program by default, as
- detailed in the <emphasis>IBM AFS Release Notes</emphasis>.</para>
+ detailed in the <emphasis>OpenAFS Release Notes</emphasis>.</para>
<para>Attempting to run multiple instances of the NTPD causes an error. Running NTPD together with another time
synchronization protocol is unnecessary and can cause instability in the clock setting.</para>
<emphasis role="bold">-localclock</emphasis> flag to the <emphasis role="bold">runntp</emphasis> command as indicated in the
following instructions. The flag tells NTPD to rely on the machine's internal clock when all external time sources are
inaccessible. The <emphasis role="bold">runntp</emphasis> command has other arguments that are possibly useful given your cell
- configuration; see the <emphasis>IBM AFS Administration Reference</emphasis>.</para>
+ configuration; see the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
<para>Choosing an appropriate external time source is important, but involves more considerations than can be discussed here. If
you need help in selecting a source, contact the AFS Product Support group.</para>
<para>The <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis> file on a client machine's local disk lists the database
server machines for each cell that the local Cache Manager can contact. If there is no entry in the file for a cell, or if the
list of database server machines is wrong, then users working on this machine cannot access the cell. The chapter in the
- <emphasis>IBM AFS Administration Guide</emphasis> about administering client machines explains how to maintain the file after
+ <emphasis>OpenAFS Administration Guide</emphasis> about administering client machines explains how to maintain the file after
creating it.</para>
<para>As the <emphasis role="bold">afsd</emphasis> program initializes the Cache Manager, it copies the contents of the
<emphasis role="bold">CellServDB</emphasis> file into kernel memory. The Cache Manager always consults the list in kernel memory
rather than the <emphasis role="bold">CellServDB</emphasis> file itself. Between reboots of the machine, you can use the
<emphasis role="bold">fs newcell</emphasis> command to update the list in kernel memory directly; see the chapter in the
- <emphasis>IBM AFS Administration Guide</emphasis> about administering client machines.</para>
+ <emphasis>OpenAFS Administration Guide</emphasis> about administering client machines.</para>
<para>The AFS distribution includes the file <emphasis role="bold">CellServDB.sample</emphasis>, and you have already copied it
to the <emphasis role="bold">/usr/vice/etc</emphasis> directory. It includes an entry for all AFS cells that agreed to share
</listitem>
<listitem>
- <para>The maximum supported cache size can vary in each AFS release; see the <emphasis>IBM AFS Release Notes</emphasis>
+ <para>The maximum supported cache size can vary in each AFS release; see the <emphasis>OpenAFS Release Notes</emphasis>
for the current version.</para>
</listitem>
<note>
<para>Not all file system types that an operating system supports are necessarily supported for use as the cache partition.
- For possible restrictions, see the <emphasis>IBM AFS Release Notes</emphasis>.</para>
+ For possible restrictions, see the <emphasis>OpenAFS Release Notes</emphasis>.</para>
</note>
<para>To configure the disk cache, perform the following procedures: <orderedlist>
to override the parameters' default values and to change the number of some of the daemons. Depending on the machine's cache
size, its amount of RAM, and how many people work on it, you can sometimes improve Cache Manager performance by overriding the
default values. For a discussion of all of the <emphasis role="bold">afsd</emphasis> command's arguments, see its reference page
- in the <emphasis>IBM AFS Administration Reference</emphasis>.</para>
+ in the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
<para>The <emphasis role="bold">afsd</emphasis> command line in the AFS initialization script on each system type includes an
<computeroutput>OPTIONS</computeroutput> variable. You can use it to set nondefault values for the command's arguments, in one
</listitem>
<listitem>
- <para>On Digital UNIX systems, <emphasis role="bold">/sbin/init.d/afs</emphasis></para>
- </listitem>
-
- <listitem>
<para>On HP-UX systems, <emphasis role="bold">/sbin/init.d/afs</emphasis></para>
</listitem>
</orderedlist></para>
<indexterm>
- <primary>Digital UNIX</primary>
-
- <secondary>AFS initialization script</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
-
- <para><emphasis role="bold">On Digital UNIX systems:</emphasis> <orderedlist>
- <listitem>
- <para>Run the AFS initialization script. <programlisting>
- # <emphasis role="bold">/sbin/init.d/afs start</emphasis>
-</programlisting></para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
<primary>HP-UX</primary>
<secondary>AFS initialization script</secondary>
</listitem>
<listitem>
- <para><link linkend="HDRWQ75">Activating the Script on Digital UNIX Systems</link></para>
- </listitem>
-
- <listitem>
<para><link linkend="HDRWQ76">Activating the Script on HP-UX Systems</link></para>
</listitem>
</orderedlist>
<indexterm>
- <primary>Digital UNIX</primary>
-
- <secondary>AFS initialization script</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ75">
- <title>Activating the Script on Digital UNIX Systems</title>
-
- <orderedlist>
- <listitem>
- <para>Change to the <emphasis role="bold">/sbin/init.d</emphasis> directory and issue the <emphasis role="bold">ln
- -s</emphasis> command to create symbolic links that incorporate the AFS initialization script into the Digital UNIX
- startup and shutdown sequence. <programlisting>
- # <emphasis role="bold">cd /sbin/init.d</emphasis>
- # <emphasis role="bold">ln -s ../init.d/afs /sbin/rc3.d/S67afs</emphasis>
- # <emphasis role="bold">ln -s ../init.d/afs /sbin/rc0.d/K66afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
- <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/sbin/init.d</emphasis> directories. If you want
- to avoid potential confusion by guaranteeing that they are always the same, create a link between them. You can always
- retrieve the original script from the AFS CD-ROM if necessary. <programlisting>
- # <emphasis role="bold">cd /usr/vice/etc</emphasis>
- # <emphasis role="bold">rm afs.rc</emphasis>
- # <emphasis role="bold">ln -s /sbin/init.d/afs afs.rc</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Proceed to <link linkend="HDRWQ80">Configuring the Top Levels of the AFS Filespace</link>.</para>
- </listitem>
- </orderedlist>
-
- <indexterm>
<primary>HP-UX</primary>
<secondary>AFS initialization script</secondary>
read/write mount point enables you to access the read/write version of replicated volumes when necessary. Creating both mount
points essentially creates separate read-only and read-write copies of your filespace, and enables the Cache Manager to traverse
the filespace on a read-only path or read/write path as appropriate. For further discussion of these concepts, see the chapter
- in the <emphasis>IBM AFS Administration Guide</emphasis> about administering volumes. <indexterm>
+ in the <emphasis>OpenAFS Administration Guide</emphasis> about administering volumes. <indexterm>
<primary>root.afs volume</primary>
<secondary>replicating</secondary>
<para>In this section you create the necessary volumes. The conventional location to which to link <emphasis
role="bold">/usr/afsws</emphasis> is <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/usr/afsws</emphasis>, where
- <replaceable>sysname</replaceable> is the appropriate system type name as specified in the <emphasis>IBM AFS Release
+ <replaceable>sysname</replaceable> is the appropriate system type name as specified in the <emphasis>OpenAFS Release
Notes</emphasis>. The instructions in <link linkend="HDRWQ133">Installing Additional Client Machines</link> assume that you have
followed the instructions in this section.</para>
<para><anchor id="LIWQ84" />Issue the <emphasis role="bold">vos create</emphasis> command to create volumes for storing
the AFS client binaries for this system type. The following example instruction creates volumes called
<replaceable>sysname</replaceable>, <replaceable>sysname</replaceable>.<emphasis role="bold">usr</emphasis>, and
- <replaceable>sysname</replaceable>.<emphasis role="bold">usr.afsws</emphasis>. Refer to the <emphasis>IBM AFS Release
+ <replaceable>sysname</replaceable>.<emphasis role="bold">usr.afsws</emphasis>. Refer to the <emphasis>OpenAFS Release
Notes</emphasis> to learn the proper value of <replaceable>sysname</replaceable> for this system type. <programlisting>
# <emphasis role="bold">vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <replaceable>sysname</replaceable>
# <emphasis role="bold">vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <replaceable>sysname</replaceable><emphasis
<para>The AFS distribution includes the following documents: <itemizedlist>
<listitem>
- <para><emphasis>IBM AFS Release Notes</emphasis></para>
+ <para><emphasis>OpenAFS Release Notes</emphasis></para>
</listitem>
<listitem>
- <para><emphasis>IBM AFS Quick Beginnings</emphasis></para>
+ <para><emphasis>OpenAFS Quick Beginnings</emphasis></para>
</listitem>
<listitem>
- <para><emphasis>IBM AFS User Guide</emphasis></para>
+ <para><emphasis>OpenAFS User Guide</emphasis></para>
</listitem>
<listitem>
- <para><emphasis>IBM AFS Administration Reference</emphasis></para>
+ <para><emphasis>OpenAFS Administration Reference</emphasis></para>
</listitem>
<listitem>
- <para><emphasis>IBM AFS Administration Guide</emphasis></para>
+ <para><emphasis>OpenAFS Administration Guide</emphasis></para>
</listitem>
</itemizedlist></para>
recommended mount point for the volume is <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
role="bold">/afsdoc</emphasis>. If you wish, you can create a link to the mount point on each client machine's local disk,
called <emphasis role="bold">/usr/afsdoc</emphasis>. Alternatively, you can create a link to the mount point in each user's home
- directory. You can also choose to permit users to access only certain documents (most probably, the <emphasis>IBM AFS User
+ directory. You can also choose to permit users to access only certain documents (most probably, the <emphasis>OpenAFS User
Guide</emphasis>) by creating different mount points or setting different ACLs on different document directories.</para>
<para>The current working directory is still <emphasis role="bold">/usr/afs/bin</emphasis>, which houses the <emphasis
the cells that had agreed to participate in the AFS global namespace at the time your AFS CD-ROM was created. As mentioned in
that section, the AFS Product Support group also maintains a copy of the file, updating it as necessary.)</para>
- <para>The chapter in the <emphasis>IBM AFS Administration Guide</emphasis> about cell administration and configuration issues
+ <para>The chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell administration and configuration issues
discusses the implications of participating in the global AFS namespace. The chapter about administering client machines
explains how to maintain knowledge of foreign cells on client machines, and includes suggestions for maintaining a central
version of the file in AFS. <orderedlist>
<sect1 id="HDRWQ93">
<title>Improving Cell Security</title>
- <para>This section discusses ways to improve the security of AFS data in your cell. Also see the chapter in the <emphasis>IBM
- AFS Administration Guide</emphasis> about configuration and administration issues.</para>
+ <para>This section discusses ways to improve the security of AFS data
+ in your cell. Also see the chapter in the <emphasis>OpenAFS
+ Administration Guide</emphasis> about configuration and administration
+ issues.</para>
<sect2 id="HDRWQ94">
<title>Controlling root Access</title>
<listitem>
<para>Set a short ticket lifetime for administrator accounts (for example, 20 minutes) by using the <emphasis
role="bold">-lifetime</emphasis> argument to the <emphasis role="bold">kas setfields</emphasis> command, which is
- described in the <emphasis>IBM AFS Administration Reference</emphasis>. Do not however, use a short lifetime for users
+ described in the <emphasis>OpenAFS Administration Reference</emphasis>. Do not however, use a short lifetime for users
who issue long-running <emphasis role="bold">backup</emphasis> commands.</para>
</listitem>
</listitem>
</orderedlist></para>
</sect1>
-</chapter>
\ No newline at end of file
+</chapter>
git://git.openafs.org / openafs.git / blobdiff