From 6e545ebf974c81f29b3249d3201821b52586ba6f Mon Sep 17 00:00:00 2001 From: Benjamin Kaduk Date: Wed, 5 Nov 2014 14:26:36 -0500 Subject: [PATCH] Deorbit IRIX-specific QuickStartGuide bits Get the rest of them all at once. Change-Id: Ife9920f00ec8eea953929a76a30f86d958d55f9c Reviewed-on: http://gerrit.openafs.org/11590 Reviewed-by: Chas Williams - CONTRACTOR Tested-by: BuildBot Reviewed-by: Benjamin Kaduk --- doc/xml/QuickStartUnix/appendix.xml | 47 --- doc/xml/QuickStartUnix/auqbg005.xml | 133 -------- doc/xml/QuickStartUnix/auqbg006.xml | 503 ---------------------------- doc/xml/QuickStartUnix/auqbg007.xml | 456 +------------------------ 4 files changed, 2 insertions(+), 1137 deletions(-) diff --git a/doc/xml/QuickStartUnix/appendix.xml b/doc/xml/QuickStartUnix/appendix.xml index 4fc8d08a2..612e6fc6d 100644 --- a/doc/xml/QuickStartUnix/appendix.xml +++ b/doc/xml/QuickStartUnix/appendix.xml @@ -632,11 +632,6 @@ ll name> Enabling AFS Login on HP-UX Systems - - - Enabling AFS Login on IRIX Systems - - Enabling AFS Login on Linux Systems @@ -992,48 +987,6 @@ ll name> - - Enabling kaserver based AFS Login on IRIX Systems - - The standard IRIX command-line - login program and the graphical - xdm 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 - OpenAFS Release Notes. - - If you configure the machine to use an AFS-modified login - utility, then the afsauthlib.so and - afskauthlib.so files (included in the - AFS distribution) must reside in the - /usr/vice/etc directory. Issue the - ls command to verify. - - - # ls /usr/vice/etc - - - If the files do not exist, unpack the OpenAFS Binary Distribution - for IRIX (if it is not already), change directory as indicated, and copy - them. - - - # cd /tmp/afsdist/sgi_65/dest/root.client/usr/vice/etc - # cp -p *authlib* /usr/vice/etc - - - After taking any necessary action, proceed to - Starting the BOS Server if you - are installing your first file server; - Starting Server Programs if you - are installing an additional file server machine; or - Loading and Creating Client Files - if you are installing a client. - Enabling kaserver based AFS Login on Linux Systems diff --git a/doc/xml/QuickStartUnix/auqbg005.xml b/doc/xml/QuickStartUnix/auqbg005.xml index 1a85f2ae5..806432fe3 100644 --- a/doc/xml/QuickStartUnix/auqbg005.xml +++ b/doc/xml/QuickStartUnix/auqbg005.xml @@ -3716,10 +3716,6 @@ Password for you/admin@REALM: your_passw On HP-UX systems, /sbin/init.d/afs - - On IRIX systems, /etc/init.d/afs - - On Fedora and RHEL systems, /etc/sysconfg/openafs @@ -3941,85 +3937,6 @@ Password for you/admin@REALM: your_passw - - IRIX - - AFS initialization script - - on first AFS machine - - - - afsclient variable (IRIX) - - first AFS machine - - - - variables - - afsclient (IRIX) - - first AFS machine - - - - IRIX - - afsclient variable - - first AFS machine - - - - afsserver variable (IRIX) - - first AFS machine - - - - variables - - afsserver (IRIX) - - first AFS machine - - - - IRIX - - afsserver variable - - first AFS machine - - - On IRIX systems: - - If you have configured the machine to use the ml dynamic loader program, - reboot the machine and log in again as the local superuser root. - # cd / - # shutdown -i6 -g0 -y - login: root - Password: root_password - - - - - Issue the chkconfig command to activate the afsserver and afsclient configuration variables. - - # /etc/chkconfig -f afsserver on - # /etc/chkconfig -f afsclient on - - - - - Run the AFS initialization script. - # /etc/init.d/afs start - - - - Linux @@ -4208,10 +4125,6 @@ Password for you/admin@REALM: your_passw Activating the Script on HP-UX Systems - - Activating the Script on IRIX Systems - - Activating the Script on Linux Systems @@ -4295,45 +4208,6 @@ Password for you/admin@REALM: your_passw - - IRIX - - AFS initialization script - - on first AFS machine - - - - - Activating the Script on IRIX Systems - - - - Change to the /etc/init.d directory and issue the ln - -s command to create symbolic links that incorporate the AFS initialization script into the IRIX startup and - shutdown sequence. - # cd /etc/init.d - # ln -s ../init.d/afs /etc/rc2.d/S35afs - # ln -s ../init.d/afs /etc/rc0.d/K35afs - - - - - (Optional) There are now copies of the AFS initialization file in both the - /usr/vice/etc and /etc/init.d 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. - # cd /usr/vice/etc - # rm afs.rc - # ln -s /etc/init.d/afs afs.rc - - - - - Proceed to Configuring the Top Levels of the AFS Filespace. - - - Linux @@ -5830,13 +5704,6 @@ Password for you/admin@REALM: your_passw - - On IRIX systems, issue the chkconfig command to deactivate the afsclient configuration variable. - # /etc/chkconfig -f afsclient off - - - Reboot the machine. Most system types use the shutdown command, but the appropriate options vary. diff --git a/doc/xml/QuickStartUnix/auqbg006.xml b/doc/xml/QuickStartUnix/auqbg006.xml index b13fb5ae1..bc3948cf6 100644 --- a/doc/xml/QuickStartUnix/auqbg006.xml +++ b/doc/xml/QuickStartUnix/auqbg006.xml @@ -243,10 +243,6 @@ Getting Started on HP-UX Systems - - Getting Started on IRIX Systems - - Getting Started on Linux Systems @@ -759,391 +755,6 @@ - - Getting Started on IRIX Systems - - Begin by incorporating AFS modifications into the kernel. Either use the ml dynamic - loader program, or build a static kernel. Then configure partitions to house AFS volumes. AFS supports use of both EFS and - XFS partitions for housing AFS volumes. SGI encourages use of XFS partitions. - file server machine, additional - - fsck program - - on IRIX - - fsck program - - on server machine after first - - IRIX - - - You do not need to replace IRIX fsck program, because the version that SGI - distributes handles AFS volumes properly. - - incorporating AFS kernel extensions - - server machine after first - - IRIX - - - - AFS kernel extensions - - on server machine after first - - IRIX - - - - file server machine, additional - - AFS kernel extensions - - on IRIX - - - - Prepare for incorporating AFS into the kernel by performing the following procedures. - - Unpack the OpenAFS IRIX distribution tarball. The - examples below assume that you have unpacked the files into - the /tmp/afsdist - directory. If you pick a different location, substitue this - in all of the following examples. Once you have unpacked - the distribution, change directory as indicated. - - # cd /tmp/afsdist/sgi_65/dest/root.client - - - - - Copy the AFS initialization script to the local directory for initialization files (by convention, - /etc/init.d on IRIX machines). Note the removal of the .rc extension as you copy the script. - # cp -p usr/vice/etc/afs.rc /etc/init.d/afs - - - - - Issue the uname -m command to determine the machine's CPU board type. The - IPxx value in the output must match one of the - supported CPU board types listed in the OpenAFS Release Notes for the current version of - AFS. - # uname -m - - - - - - - Incorporate AFS into the kernel, either using the ml program or by building AFS - modifications into a static kernel. - - IRIX - - AFS kernel extensions - - on server machine after first - - - - To use the ml program: - afsml variable (IRIX) - - server machine after first - - variables - - afsml (IRIX) - - server machine after first - - IRIX - - afsml variable - - server machine after first - - afsxnfs variable (IRIX) - - server machine after first - - variables - - afsxnfs (IRIX) - - server machine after first - - IRIX - - afsxnfs variable - - server machine after first - - - Create the local /usr/vice/etc/sgiload directory to house the AFS - kernel library file. - # mkdir /usr/vice/etc/sgiload - - - - - Copy the appropriate AFS kernel library file to the /usr/vice/etc/sgiload directory. The IPxx portion of the library file name must match the - value previously returned by the uname -m command. Also choose the file - appropriate to whether the machine's kernel supports NFS server functionality (NFS must be supported for - the machine to act as an NFS/AFS Translator). Single- and multiprocessor machines use the same library - file. - - (You can choose to copy all of the kernel library files into the /usr/vice/etc/sgiload directory, but they require a significant amount of - space.) - - If the machine's kernel supports NFS server functionality: - - - # cp -p usr/vice/etc/sgiload/libafs.IPxx.o /usr/vice/etc/sgiload - - - If the machine's kernel does not support NFS server functionality: - - - # cp -p usr/vice/etc/sgiload/libafs.IPxx.nonfs.o \ - /usr/vice/etc/sgiload - - - - - Issue the chkconfig command to activate the afsml configuration variable. - # /etc/chkconfig -f afsml on - - - If the machine is to function as an NFS/AFS Translator and the kernel supports NFS server - functionality, activate the afsxnfs variable. - - - # /etc/chkconfig -f afsxnfs on - - - - - Run the /etc/init.d/afs script to load AFS extensions into the - kernel. The script invokes the ml command, automatically determining - which kernel library file to use based on this machine's CPU type and the activation state of the - afsxnfs variable. - - You can ignore any error messages about the inability to start the BOS Server or the Cache Manager - or AFS client. - - - # /etc/init.d/afs start - - - - - Proceed to Step 3. - - - - - IRIX - - AFS-modified kernel - - on add'l server machine - - - - - If you prefer to build a kernel, and the machine's hardware and software configuration exactly matches - another IRIX 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. - - Copy the kernel initialization file afs.sm to the local /var/sysgen/system directory, and the kernel master file afs to the local /var/sysgen/master.d directory. - - # cp -p bin/afs.sm /var/sysgen/system - # cp -p bin/afs /var/sysgen/master.d - - - - - Copy the appropriate AFS kernel library file to the local file /var/sysgen/boot/afs.a; the IPxx portion of the library file name must match the - value previously returned by the uname -m command. Also choose the file - appropriate to whether the machine's kernel supports NFS server functionality (NFS must be supported for - the machine to act as an NFS/AFS Translator). Single- and multiprocessor machines use the same library - file. - - If the machine's kernel supports NFS server functionality: - - - # cp -p bin/libafs.IPxx.a /var/sysgen/boot/afs.a - - - If the machine's kernel does not support NFS server functionality: - - - # cp -p bin/libafs.IPxx.nonfs.a /var/sysgen/boot/afs.a - - - - - Issue the chkconfig command to deactivate the afsml configuration variable. - # /etc/chkconfig -f afsml off - - - If the machine is to function as an NFS/AFS Translator and the kernel supports NFS server - functionality, activate the afsxnfs variable. - - - # /etc/chkconfig -f afsxnfs on - - - - - Copy the existing kernel file, /unix, to a safe location. Compile - the new kernel, which is created in the file /unix.install. It overwrites - the existing /unix file when the machine reboots in the next step. - - # cp /unix /unix_noafs - # autoconfig - - - - - Reboot the machine to start using the new kernel, and login again as the superuser root. - # cd / - # shutdown -i6 -g0 -y - login: root - Password: root_password - - - - - - - - configuring - - AFS server partition on server machine after first - - IRIX - - - - AFS server partition - - configuring on server machine after first - - IRIX - - - - file server machine, additional - - AFS server partition - - on IRIX - - - - IRIX - - AFS server partition - - on add'l server machine - - - - - Create a directory called /vicepxx for each AFS server partition you are configuring (there - must be at least one). Repeat the command for each partition. - # mkdir /vicepxx - - - - - Add a line with the following format to the file systems registry file, /etc/fstab, for each partition (or logical volume created with the XLV volume manager) to be - mounted on one of the directories created in the previous step. - - For an XFS partition or logical volume: - - - /dev/dsk/disk /vicepxx xfs rw,raw=/dev/rdsk/disk 0 0 - - - For an EFS partition: - - - /dev/dsk/disk /vicepxx efs rw,raw=/dev/rdsk/disk 0 0 - - - The following are examples of an entry for each file system type: - - - /dev/dsk/dks0d2s6 /vicepa xfs rw,raw=/dev/rdsk/dks0d2s6 0 0 - /dev/dsk/dks0d3s1 /vicepb efs rw,raw=/dev/rdsk/dks0d3s1 0 0 - - - - - Create a file system on each partition that is to be mounted on a /vicepxx directory. The following commands are probably appropriate, - but consult the IRIX documentation for more information. In both cases, raw_device is a raw - device name like /dev/rdsk/dks0d0s0 for a single disk partition or /dev/rxlv/xlv0 for a logical volume. - - For XFS file systems, include the indicated options to configure the partition or logical volume with inodes - large enough to accommodate AFS-specific information: - - - # mkfs -t xfs -i size=512 -l size=4000b raw_device - - - For EFS file systems: - - - # mkfs -t efs raw_device - - - - - Mount each partition by issuing either the mount -a command to mount all - partitions at once or the mount command to mount each partition in turn. - - - - (Optional) If you have configured partitions or logical volumes to use XFS, - issue the following command to verify that the inodes are configured properly (are large enough to accommodate - AFS-specific information). If the configuration is correct, the command returns no output. Otherwise, it specifies the - command to run in order to configure each partition or logical volume properly. - # /usr/afs/bin/xfs_size_check - - - - - If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the - instructions in Enabling AFS Login on IRIX Systems. - - - - Proceed to Starting Server Programs. - - - - Getting Started on Linux Systems @@ -2451,10 +2062,6 @@ On HP-UX systems, /sbin/init.d/afs - - On IRIX systems, /etc/init.d/afs - - On Fedora and RHEL systems, /etc/sysconfig/openafs. @@ -2654,116 +2261,6 @@ - - IRIX - - AFS initialization script - - on add'l server machine - - - - afsclient variable (IRIX) - - server machine after first - - - - variables - - afsclient (IRIX) - - server machine after first - - - - IRIX - - afsclient variable - - server machine after first - - - - afsserver variable (IRIX) - - server machine after first - - - - variables - - afsserver (IRIX) - - server machine after first - - - - IRIX - - afsserver variable - - server machine after first - - - On IRIX systems: - - If you have configured the machine to use the ml dynamic loader program, - reboot the machine and log in again as the local superuser root. - # cd / - # shutdown -i6 -g0 -y - login: root - Password: root_password - - - - - Issue the chkconfig command to activate the afsserver configuration variable. - # /etc/chkconfig -f afsserver on - - - If you have configured this machine as an AFS client and want to it remain one, also issue the chkconfig command to activate the afsclient configuration - variable. - - - # /etc/chkconfig -f afsclient on - - - - - Run the AFS initialization script. - # /etc/init.d/afs start - - - - - Change to the /etc/init.d directory and issue the ln - -s command to create symbolic links that incorporate the AFS initialization script into the IRIX - startup and shutdown sequence. - # cd /etc/init.d - # ln -s ../init.d/afs /etc/rc2.d/S35afs - # ln -s ../init.d/afs /etc/rc0.d/K35afs - - - - - (Optional) There are now copies of the AFS initialization file in both the - /usr/vice/etc and /etc/init.d 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. - # cd /usr/vice/etc - # rm afs.rc - # ln -s /etc/init.d/afs afs.rc - - - - - Proceed to Step 4. - - - Linux diff --git a/doc/xml/QuickStartUnix/auqbg007.xml b/doc/xml/QuickStartUnix/auqbg007.xml index ac9aa9a97..7427cf31e 100644 --- a/doc/xml/QuickStartUnix/auqbg007.xml +++ b/doc/xml/QuickStartUnix/auqbg007.xml @@ -150,10 +150,6 @@ Getting Started on HP-UX Systems - - Getting Started on IRIX Systems - - Getting Started on Linux Systems @@ -569,342 +565,7 @@ Proceed to Loading and Creating Client Files. - - - - incorporating AFS kernel extensions - - client machine - - IRIX - - - - AFS kernel extensions - - on client machine - - IRIX - - - client machine - - AFS kernel extensions - - on IRIX - - - - - - Getting Started on IRIX Systems - - In this section you incorporate AFS into the IRIX kernel, choosing one of two methods: - - Dynamic loading using the ml program distributed by Silicon Graphics, Incorporated - (SGI). - - - - Building a new static kernel. - - - - Then see Enabling AFS Login on IRIX Systems to read about integrated AFS login on IRIX - systems. - - In preparation for either dynamic loading or kernel building, perform the following procedures: - - Unpack the OpenAFS IRIX distribution tarball. The examples - below assume that you have unpacked the files into the - /tmp/afsdist directory. If you - pick a different location, substitue this in all of the following - examples. Once you have unpacked the distribution, change directory - as indicated. - - # cd /tmp/afsdist/sgi_65/dest/root.client - - - - Copy the AFS initialization script to the local directory for initialization files (by convention, /etc/init.d on IRIX machines). Note the removal of the .rc - extension as you copy the script. - # cp -p usr/vice/etc/afs.rc /etc/init.d/afs - - - - - Issue the uname -m command to determine the machine's CPU board type. The IPxx value in the output must match one of the supported CPU board types - listed in the OpenAFS Release Notes for the current version of AFS. - # uname -m - - - - - Proceed to either Loading AFS into the IRIX Kernel or Building AFS into the IRIX Kernel. - - - - - IRIX - - AFS kernel extensions - - on client machine - - - - afsml variable (IRIX) - - client machine - - - - variables - - afsml (IRIX) - - client machine - - - - IRIX - - afsml variable - - client machine - - - - afsxnfs variable (IRIX) - - client machine - - - - variables - - afsxnfs (IRIX) - - client machine - - - - IRIX - - afsxnfs variable - - client machine - - - - Loading AFS into the IRIX Kernel - - The ml program is the dynamic kernel loader provided by SGI for IRIX systems. If you - use it rather than building AFS modifications into a static kernel, then for AFS to function correctly the ml program must run each time the machine reboots. Therefore, the AFS initialization script (included - in the OpenAFS Binary Distribution) invokes it automatically when the afsml configuration variable is - activated. In this section you activate the variable and run the script. - - In a later section you verify that the script correctly initializes the Cache Manager, then create the links that - incorporate AFS into the IRIX startup and shutdown sequence. - - Create the local /usr/vice/etc/sgiload directory to house the AFS kernel library - file. - # mkdir /usr/vice/etc/sgiload - - - - - Copy the appropriate AFS kernel library file to the /usr/vice/etc/sgiload - directory. The IPxx portion of the library file name must - match the value previously returned by the uname -m command. Also choose the file - appropriate to whether the machine's kernel supports NFS server functionality (NFS must be supported for the machine to - act as an NFS/AFS Translator). Single- and multiprocessor machines use the same library file. - - (You can choose to copy all of the kernel library files into the /usr/vice/etc/sgiload directory, but they require a significant amount of space.) - - If the machine's kernel supports NFS server functionality: - - - # cp -p usr/vice/etc/sgiload/libafs.IPxx.o /usr/vice/etc/sgiload - - - If the machine's kernel does not support NFS server functionality: - - - # cp -p usr/vice/etc/sgiload/libafs.IPxx.nonfs.o \ - /usr/vice/etc/sgiload - - - - - Issue the chkconfig command to activate the afsml configuration variable. - # /etc/chkconfig -f afsml on - - - If the machine is to function as an NFS/AFS Translator and the kernel supports NFS server functionality, activate - the afsxnfs variable. - - - # /etc/chkconfig -f afsxnfs on - - - - - Run the /etc/init.d/afs script to load AFS extensions into the kernel. The script - invokes the ml command, automatically determining which kernel library file to use - based on this machine's CPU type and the activation state of the afsxnfs - variable. - - You can ignore any error messages about the inability to start the BOS Server or the Cache Manager or AFS - client. - - - # /etc/init.d/afs start - - - - - Proceed to Enabling AFS Login on IRIX Systems. - - - - - IRIX - - AFS-modified kernel - - on client machine - - - - - Building AFS into the IRIX Kernel - - If you prefer to build a kernel, and the machine's hardware and software configuration exactly matches another IRIX - 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. - - Copy the kernel initialization file afs.sm to the local /var/sysgen/system directory, and the kernel master file afs to - the local /var/sysgen/master.d directory. - # cp -p bin/afs.sm /var/sysgen/system - # cp -p bin/afs /var/sysgen/master.d - - - - - Copy the appropriate AFS kernel library file to the local file /var/sysgen/boot/afs.a; the IPxx - portion of the library file name must match the value previously returned by the uname - -m command. Also choose the file appropriate to whether the machine's kernel supports NFS server - functionality (NFS must be supported for the machine to act as an NFS/AFS Translator). Single- and multiprocessor - machines use the same library file. - - If the machine's kernel supports NFS server functionality: - - - # cp -p bin/libafs.IPxx.a /var/sysgen/boot/afs.a - - - If the machine's kernel does not support NFS server functionality: - - - # cp -p bin/libafs.IPxx.nonfs.a /var/sysgen/boot/afs.a - - - - - Issue the chkconfig command to deactivate the afsml configuration variable. - # /etc/chkconfig -f afsml off - - - If the machine is to function as an NFS/AFS Translator and the kernel supports NFS server functionality, activate - the afsxnfs variable. - - - # /etc/chkconfig -f afsxnfs on - - - - - Copy the existing kernel file, /unix, to a safe location. Compile the new kernel, - which is created in the file /unix.install. It overwrites the existing /unix file when the machine reboots in the next step. - # cp /unix /unix_noafs - # autoconfig - - - - - Reboot the machine to start using the new kernel, and login again as the superuser root. - # cd / - # shutdown -i6 -g0 -y - login: root - Password: root_password - - - - - Proceed to Enabling AFS Login on IRIX Systems. - - - - - enabling AFS login - - client machine - - IRIX - - - - AFS login - - on client machine - - IRIX - - - - client machine - - AFS login - - on IRIX - - - - - Enabling AFS Login on IRIX Systems - - Whilst the standard IRIX command-line - login program and the - graphical xdm login program both have - the ability to grant AFS tokens, this ability relies upon the deprecated - kaserver authentication system. As this system is not recommended for - new installations, this is not documented here. - - Users who have been successfully authenticated via Kerberos 5 - authentication may obtain AFS tokens following login by running the - aklog command. - - If you are at a site which still requires - kaserver or external Kerberos v4 based - authentication, please consult - Enabling kaserver based AFS Login on Linux Systems - for further installation instructions. - - Proceed to Loading and Creating Client Files. incorporating AFS kernel extensions @@ -959,7 +620,8 @@ on Linux client machine - + + @@ -2092,10 +1754,6 @@ On HP-UX systems, /sbin/init.d/afs - - On IRIX systems, /etc/init.d/afs - - On Fedora and RHEL systems, /etc/sysconfig/openafs @@ -2187,10 +1845,6 @@ Running the Script on HP-UX Systems - - Running the Script on IRIX Systems - - Running the Script on Linux Systems @@ -2343,112 +1997,6 @@ AFS initialization file - - IRIX - - AFS initialization script - - on client machine - - - - etc/init.d/afs - - afs file - - - - afsclient variable (IRIX) - - client machine - - - - variables - - afsclient (IRIX) - - client machine - - - - IRIX - - afsclient variable - - client machine - - - - - Running the Script on IRIX Systems - - - - If you have configured the machine to use the ml dynamic loader program, reboot the - machine and log in again as the local superuser root. - # cd / - # shutdown -i6 -g0 -y - login: root - Password: root_password - - - - - Issue the chkconfig command to activate the afsclient configuration variable. - # /etc/chkconfig -f afsclient on - - - - - Run the AFS initialization script. - # /etc/init.d/afs start - - - - - Change to the /etc/init.d directory and issue the ln - -s command to create symbolic links that incorporate the AFS initialization script into the IRIX startup and - shutdown sequence. - # cd /etc/init.d - # ln -s ../init.d/afs /etc/rc2.d/S35afs - # ln -s ../init.d/afs /etc/rc0.d/K35afs - - - - - (Optional) There are now copies of the AFS initialization file in both the - /usr/vice/etc and /etc/init.d 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. - # cd /usr/vice/etc - # rm afs.rc - # ln -s /etc/init.d/afs afs.rc - - - - - If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to Setting Up Volumes and Loading Binaries into AFS. Otherwise, the installation is - complete. - - - - - afs file - - AFS initialization file - - - - files - - afs - - AFS initialization file - - etc/rc.d/init.d/afs -- 2.39.5