</listitem>
<listitem>
- <para><link linkend="HDRWQ103">Getting Started on HP-UX Systems</link></para>
- </listitem>
-
- <listitem>
<para><link linkend="HDRWQ106">Getting Started on Linux Systems</link></para>
</listitem>
</orderedlist></para>
</sect3>
- <sect3 id="HDRWQ103">
- <title>Getting Started on HP-UX Systems</title>
-
- <para>Begin by building AFS modifications into the kernel, then configure server partitions and replace the HP-UX <emphasis
- role="bold">fsck</emphasis> program with a version that correctly handles AFS volumes.</para>
-
- <para>If the machine's hardware and software configuration exactly matches another HP-UX machine on which AFS is already
- built into the kernel, you can copy the kernel from that machine to this one. In general, however, it is better to build AFS
- modifications into the kernel on each machine according to the following instructions.
- <orderedlist>
- <indexterm>
- <primary>incorporating AFS kernel extensions</primary>
-
- <secondary>server machine after first</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS kernel extensions</primary>
-
- <secondary>on server machine after first</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>file server machine, additional</primary>
-
- <secondary>AFS kernel extensions</secondary>
-
- <tertiary>on HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>HP-UX</primary>
-
- <secondary>AFS-modified kernel</secondary>
-
- <tertiary>on add'l server machine</tertiary>
- </indexterm>
-
- <listitem>
- <para>Move the existing kernel-related files to a safe location. <programlisting>
- # <emphasis role="bold">cp /stand/vmunix /stand/vmunix.noafs</emphasis>
- # <emphasis role="bold">cp /stand/system /stand/system.noafs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Unpack the OpenAFS HP-UX distribution tarball. The examples
- below assume that you have unpacked the files into the
- <emphasis role="bold">/tmp/afsdist</emphasis> directory. If you
- pick a different location, substitute this in all of the following
- examples. Once you have unpacked the distribution, change
- directory as indicated.
-<programlisting>
- # <emphasis role="bold">cd /tmp/afsdist/hp_ux110/dest/root.client</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS initialization file to the local directory for initialization files (by convention, <emphasis
- role="bold">/sbin/init.d</emphasis> on HP-UX machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
- extension as you copy the file. <programlisting>
- # <emphasis role="bold">cp usr/vice/etc/afs.rc /sbin/init.d/afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the file <emphasis role="bold">afs.driver</emphasis> to the local <emphasis
- role="bold">/usr/conf/master.d</emphasis> directory, changing its name to <emphasis role="bold">afs</emphasis> as you
- do. <programlisting>
- # <emphasis role="bold">cp usr/vice/etc/afs.driver /usr/conf/master.d/afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS kernel module to the local <emphasis role="bold">/usr/conf/lib</emphasis> directory.</para>
-
- <para>If the machine's kernel supports NFS server functionality:</para>
-
- <programlisting>
- # <emphasis role="bold">cp bin/libafs.a /usr/conf/lib</emphasis>
-</programlisting>
-
- <para>If the machine's kernel does not support NFS server functionality, change the file's name as you copy it:</para>
-
- <programlisting>
- # <emphasis role="bold">cp bin/libafs.nonfs.a /usr/conf/lib/libafs.a</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Incorporate the AFS driver into the kernel, either using the <emphasis role="bold">SAM</emphasis> program or a
- series of individual commands. <itemizedlist>
- <listitem>
- <para>To use the <emphasis role="bold">SAM</emphasis> program: <orderedlist>
- <listitem>
- <para>Invoke the <emphasis role="bold">SAM</emphasis> program, specifying the hostname of the local
- machine as <replaceable>local_hostname</replaceable>. The <emphasis role="bold">SAM</emphasis> graphical
- user interface pops up. <programlisting>
- # <emphasis role="bold">sam -display</emphasis> <replaceable>local_hostname</replaceable><emphasis role="bold">:0</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Choose the <emphasis role="bold">Kernel Configuration</emphasis> icon, then the <emphasis
- role="bold">Drivers</emphasis> icon. From the list of drivers, select <emphasis
- role="bold">afs</emphasis>.</para>
- </listitem>
-
- <listitem>
- <para>Open the pull-down <emphasis role="bold">Actions</emphasis> menu and choose the <emphasis
- role="bold">Add Driver to Kernel</emphasis> option.</para>
- </listitem>
-
- <listitem>
- <para>Open the <emphasis role="bold">Actions</emphasis> menu again and choose the <emphasis
- role="bold">Create a New Kernel</emphasis> option.</para>
- </listitem>
-
- <listitem>
- <para>Confirm your choices by choosing <emphasis role="bold">Yes</emphasis> and <emphasis
- role="bold">OK</emphasis> when prompted by subsequent pop-up windows. The <emphasis
- role="bold">SAM</emphasis> program builds the kernel and reboots the system.</para>
- </listitem>
-
- <listitem>
- <para>Login again as the superuser <emphasis role="bold">root</emphasis>. <programlisting>
- login: <emphasis role="bold">root</emphasis>
- Password: <replaceable>root_password</replaceable>
-</programlisting></para>
- </listitem>
- </orderedlist></para>
- </listitem>
-
- <listitem>
- <para>To use individual commands: <orderedlist>
- <listitem>
- <para>Edit the file <emphasis role="bold">/stand/system</emphasis>, adding an entry for <emphasis
- role="bold">afs</emphasis> to the <computeroutput>Subsystems</computeroutput> section.</para>
- </listitem>
-
- <listitem>
- <para>Change to the <emphasis role="bold">/stand/build</emphasis> directory and issue the <emphasis
- role="bold">mk_kernel</emphasis> command to build the kernel. <programlisting>
- # <emphasis role="bold">cd /stand/build</emphasis>
- # <emphasis role="bold">mk_kernel</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Move the new kernel to the standard location (<emphasis role="bold">/stand/vmunix</emphasis>),
- reboot the machine to start using it, and login again as the superuser <emphasis
- role="bold">root</emphasis>. <programlisting>
- # <emphasis role="bold">mv /stand/build/vmunix_test /stand/vmunix</emphasis>
- # <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>
- </listitem>
- </itemizedlist></para>
-
- <indexterm>
- <primary>configuring</primary>
-
- <secondary>AFS server partition on server machine after first</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS server partition</primary>
-
- <secondary>configuring on server machine after first</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>file server machine, additional</primary>
-
- <secondary>AFS server partition</secondary>
-
- <tertiary>on HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>HP-UX</primary>
-
- <secondary>AFS server partition</secondary>
-
- <tertiary>on add'l server machine</tertiary>
- </indexterm>
- </listitem>
-
- <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>Use the <emphasis role="bold">SAM</emphasis> program to create a file system on each partition. For
- instructions, consult the HP-UX documentation.</para>
- </listitem>
-
- <listitem>
- <para>On some HP-UX systems that use logical volumes, the <emphasis role="bold">SAM</emphasis> program automatically
- mounts the partitions. If it has not, 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. <indexterm>
- <primary>replacing fsck program</primary>
-
- <secondary>server machine after first</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm> <indexterm>
- <primary>fsck program</primary>
-
- <secondary>on server machine after first</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm> <indexterm>
- <primary>file server machine, additional</primary>
-
- <secondary>fsck program</secondary>
-
- <tertiary>on HP-UX</tertiary>
- </indexterm> <indexterm>
- <primary>HP-UX</primary>
-
- <secondary>fsck program</secondary>
-
- <tertiary>on add'l server machine</tertiary>
- </indexterm></para>
- </listitem>
-
- <listitem>
- <para>Create the command configuration file <emphasis role="bold">/sbin/lib/mfsconfig.d/afs</emphasis>. Use a text
- editor to place the indicated two lines in it: <programlisting>
- format_revision 1
- fsck 0 m,P,p,d,f,b:c:y,n,Y,N,q,
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Create and change directory to an AFS-specific command directory called <emphasis
- role="bold">/sbin/fs/afs</emphasis>. <programlisting>
- # <emphasis role="bold">mkdir /sbin/fs/afs</emphasis>
- # <emphasis role="bold">cd /sbin/fs/afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS-modified version of the <emphasis role="bold">fsck</emphasis> program (the <emphasis
- role="bold">vfsck</emphasis> binary) and related files from the distribution directory to the new AFS-specific command
- directory. <programlisting>
- # <emphasis role="bold">cp -p /tmp/afsdist/hp_ux110/dest/root.server/etc/* .</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Change the <emphasis role="bold">vfsck</emphasis> binary's name to <emphasis role="bold">fsck</emphasis> and set
- the mode bits appropriately on all of the files in the <emphasis role="bold">/sbin/fs/afs</emphasis> directory.
- <programlisting>
- # <emphasis role="bold">mv vfsck fsck</emphasis>
- # <emphasis role="bold">chmod 755 *</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Edit the <emphasis role="bold">/etc/fstab</emphasis> file, changing the file system type for each AFS server
- partition from <computeroutput>hfs</computeroutput> to <computeroutput>afs</computeroutput>. This ensures that the
- AFS-modified <emphasis role="bold">fsck</emphasis> program runs on the appropriate partitions.</para>
-
- <para>The sixth line in the following example of an edited file shows an AFS server partition, <emphasis
- role="bold">/vicepa</emphasis>.</para>
-
- <programlisting>
- /dev/vg00/lvol1 / hfs defaults 0 1
- /dev/vg00/lvol4 /opt hfs defaults 0 2
- /dev/vg00/lvol5 /tmp hfs defaults 0 2
- /dev/vg00/lvol6 /usr hfs defaults 0 2
- /dev/vg00/lvol8 /var hfs defaults 0 2
- /dev/vg00/lvol9 /vicepa afs defaults 0 2
- /dev/vg00/lvol7 /usr/vice/cache hfs defaults 0 2
-</programlisting>
- </listitem>
-
- <listitem>
- <para>If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the
- instructions in <link linkend="HDRWQ35">Enabling AFS Login on HP-UX Systems</link>.</para>
- </listitem>
-
- <listitem>
- <para>Proceed to <link linkend="HDRWQ108">Starting Server Programs</link>.</para>
- </listitem>
- </orderedlist></para>
- </sect3>
-
<sect3 id="HDRWQ106">
<title>Getting Started on Linux Systems</title>
</listitem>
<listitem>
- <para>On HP-UX systems, <emphasis role="bold">/sbin/init.d/afs</emphasis></para>
- </listitem>
-
- <listitem>
<para>On Fedora and RHEL systems,
<emphasis role="bold">/etc/sysconfig/openafs</emphasis>.
Note that this file has a different format from a standard
</orderedlist></para>
<indexterm>
- <primary>HP-UX</primary>
-
- <secondary>AFS initialization script</secondary>
-
- <tertiary>on add'l server machine</tertiary>
- </indexterm>
-
- <para><emphasis role="bold">On HP-UX systems:</emphasis> <orderedlist>
- <listitem>
- <para>Run the AFS initialization script. <programlisting>
- # <emphasis role="bold">/sbin/init.d/afs start</emphasis>
-</programlisting></para>
- </listitem>
-
- <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 HP-UX
- startup and shutdown sequence. <programlisting>
- # <emphasis role="bold">cd /sbin/init.d</emphasis>
- # <emphasis role="bold">ln -s ../init.d/afs /sbin/rc2.d/S460afs</emphasis>
- # <emphasis role="bold">ln -s ../init.d/afs /sbin/rc2.d/K800afs</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 Step <link linkend="LIWQ113">4</link>.</para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
<primary>Linux</primary>
<secondary>AFS initialization script</secondary>
git://git.openafs.org / openafs.git / blobdiff