</listitem>
<listitem>
- <para><link linkend="HDRWQ138">Getting Started on HP-UX Systems</link></para>
- </listitem>
-
- <listitem>
<para><link linkend="HDRWQ143">Getting Started on Linux Systems</link></para>
</listitem>
<listitem>
<para>Proceed to <link linkend="HDRWQ145">Loading and Creating Client Files</link>.</para>
</listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>incorporating AFS kernel extensions</primary>
-
- <secondary>client machine</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS kernel extensions</primary>
-
- <secondary>on client machine</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>client machine</primary>
-
- <secondary>AFS kernel extensions</secondary>
-
- <tertiary>on HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>HP-UX</primary>
-
- <secondary>AFS-modified kernel</secondary>
-
- <tertiary>on client machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>enabling AFS login</primary>
-
- <secondary>client machine</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS login</primary>
-
- <secondary>on client machine</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>client machine</primary>
-
- <secondary>AFS login</secondary>
-
- <tertiary>on HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>HP-UX</primary>
-
- <secondary>AFS login</secondary>
-
- <tertiary>on client machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>PAM</primary>
-
- <secondary>on HP-UX</secondary>
-
- <tertiary>client machine</tertiary>
- </indexterm>
- </sect2>
- </sect1>
-
- <sect1 id="HDRWQ138">
- <title>Getting Started on HP-UX Systems</title>
-
- <para>In this section you build AFS into the HP-UX kernel. Then incorporate AFS modifications into the machine's Pluggable
- Authentication Module (PAM) system, if you wish to enable AFS login.</para>
-
- <sect2 id="Header_126">
- <title>Building AFS into the HP-UX Kernel</title>
-
- <para>On HP-UX systems, you must build AFS modifications into a new static kernel; HP-UX does not support dynamic loading. 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 choose to 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>
- <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>
- </listitem>
- </orderedlist></para>
- </sect2>
-
- <sect2 id="Header_127">
- <title>Enabling AFS Login on HP-UX Systems</title>
-
- <para>At this point you incorporate AFS into the operating system's Pluggable Authentication Module (PAM) scheme. PAM
- integrates all authentication mechanisms on the machine, including login, to provide the security infrastructure for
- authenticated access to and from the machine.</para>
-
- <para>In modern AFS installations, you should be using Kerberos v5
- for user login, and obtaining AFS tokens subsequent to this authentication
- step. OpenAFS does not currently distribute a PAM module allowing AFS
- tokens to be automatically gained at login. Whilst there are a number of
- third party modules providing this functionality, it is not know if these
- have been tested with HP/UX.</para>
-
- <para>Following login, users can
- obtain tokens by running the <emphasis role="bold">aklog</emphasis>
- command</para>
-
- <para>If you are at a site which still requires
- <emphasis role="bold">kaserver</emphasis> or external Kerberos v4 based
- authentication, please consult
- <link linkend="KAS014">Enabling kaserver based AFS Login on HP-UX systems</link>
- for further installation instructions.
- <orderedlist>
- <listitem>
- <para>Proceed to <link linkend="HDRWQ145">Loading and Creating Client Files</link>.</para>
- </listitem>
</orderedlist>
<indexterm>
</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></para>
</listitem>
</listitem>
<listitem>
- <para><link linkend="HDRWQ153">Running the Script on HP-UX Systems</link></para>
- </listitem>
-
- <listitem>
<para><link linkend="HDRWQ155">Running the Script on Linux Systems</link></para>
</listitem>
</indexterm>
<indexterm>
- <primary>HP-UX</primary>
-
- <secondary>AFS initialization script</secondary>
-
- <tertiary>on client machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ153">
- <title>Running the Script on HP-UX Systems</title>
-
- <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>If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to <link
- linkend="HDRWQ157">Setting Up Volumes and Loading Binaries into AFS</link>. Otherwise, the installation is
- complete.</para>
- </listitem>
- </orderedlist>
-
- <indexterm>
- <primary>afs file</primary>
-
- <secondary>AFS initialization file</secondary>
- </indexterm>
-
- <indexterm>
- <primary>files</primary>
-
- <secondary>afs</secondary>
-
- <tertiary>AFS initialization file</tertiary>
- </indexterm>
-
- <indexterm>
<primary>etc/rc.d/init.d/afs</primary>
<see>afs file</see>
git://git.openafs.org / openafs.git / blobdiff