Incorporating AFS into the IRIX Kernel

Issue the uname -m command to determine the machine's CPU type. The IPxx value in the output must match one of the supported CPU types listed in Supported System Types.

   # uname -m   

Access the AFS distribution by changing directory as indicated. Substitute "sgi_65" for the sysname variable.

• If you copied the contents of the root.client directory into AFS (in Step 6 of Storing Binaries in AFS), change directory as indicated.

  # cd /afs/cellname/sysname/usr/afsws/root.client

• If copying files from the CD-ROM, mount the CD-ROM for this machine's system type on the local /cdrom directory. For instructions on mounting CD-ROMs (either locally or remotely via NFS), consult the operating system documentation. Then change directory as indicated.

  # cd /cdrom/sysname/root.client

• If accessing the distribution electronically, you possibly already downloaded it in Storing Binaries in AFS. If so, it is still in the temp_afs36_dir directory. If not, download it and run any commands necessary to uncompress or unpack the distribution. Place it in a temporary location (temp_afs36_dir), and change directory to the indicated subdirectory.

  # cd temp_afs36_dir/root.client

Copy the appropriate AFS kernel library file to the local /usr/vice/etc/sgiload directory; the IPxx portion of the library file name must match the value 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.

   # cd  usr/vice/etc/sgiload    

   # cp -p  libafs.IPxx.nonfs.o  /usr/vice/etc/sgiload   

   # cp -p   libafs.IPxx.o   /usr/vice/etc/sgiload   

Proceed to Enabling the AFS Initialization Script on IRIX Systems.

Access the AFS distribution by changing directory as indicated. Substitute "sgi_65" for the sysname variable.

• If you copied the contents of the root.client directory into AFS (in Step 6 of Storing Binaries in AFS), change directory as indicated.

  # cd /afs/cellname/sysname/usr/afsws/root.client

• If copying files from the CD-ROM, mount the CD-ROM for this machine's system type on the local /cdrom directory. For instructions on mounting CD-ROMs (either locally or remotely via NFS), consult the operating system documentation. Then change directory as indicated.

  # cd /cdrom/sysname/root.client

• If accessing the distribution electronically, you possibly already downloaded it in Storing Binaries in AFS. If so, it is still in the temp_afs36_dir directory. If not, download it and run any commands necessary to uncompress or unpack the distribution. Place it in a temporary location (temp_afs36_dir), and change directory to the indicated subdirectory.

  # cd temp_afs36_dir/root.client

Issue the uname -m command to determine the machine's CPU type. The IPxx value in the output must match one of the supported CPU types listed in the OpenAFS Release Notes for the current version of OpenAFS.

   # uname -m    

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 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.

   # cd bin   

   # cp -p libafs.IPxx.nonfs.a /var/sysgen/boot/afs.a

   # cp -p libafs.IPxx.a /var/sysgen/boot/afs.a  

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 afs.sm /var/sysgen/system
   
   # cp -p afs /var/sysgen/master.d   

Copy the existing kernel file, /unix, to a safe location and compile the new kernel. It is created as /unix.install, and overwrites the existing /unix file when the machine reboots.

   # cp -p /unix /unix_orig
   
   # autoconfig   

Proceed to Enabling the AFS Initialization Script on IRIX Systems.

Because you ran AFS 3.5 on this machine, the appropriate AFS initialization file possibly already exists as /etc/init.d/afs. Compare it to the version in the root.client/usr/vice/etc directory of the AFS 3.6 distribution to see if any changes are needed. If the initialization file is not already in place, copy it now. If the machine is configured as a client machine, you already copied the script to the local /usr/vice/etc directory. Otherwise, change directory as indicated, substituting "sgi_65" for the sysname variable.

• If you copied the contents of the root.client directory into AFS (in Step 6 of Storing Binaries in AFS), change directory as indicated.

  # cd /afs/cellname/sysname/usr/afsws/root.client

• If copying files from the CD-ROM, mount the CD-ROM for this machine's system type on the local /cdrom directory. For instructions on mounting CD-ROMs (either locally or remotely via NFS), consult the operating system documentation. Then change directory as indicated.

  # cd /cdrom/sysname/root.client

• If accessing the distribution electronically, you possibly already downloaded it in Storing Binaries in AFS. If so, it is still in the temp_afs36_dir directory. If not, download it and run any commands necessary to uncompress or unpack the distribution. Place it in a temporary location (temp_afs36_dir), and change directory to the indicated subdirectory.

  # cd temp_afs36_dir/root.client

   # cp -p script_location/afs.rc /etc/init.d/afs  

If the afsml configuration variable is not already set appropriately, issue the chkconfig command. If you are using the ml program:

   # /etc/chkconfig -f afsml on   

   # /etc/chkconfig -f afsml off   

   # /etc/chkconfig -f afsxnfs on   

Verify the existence of the symbolic links specified in the following commands, which incorporate the AFS initialization script into the IRIX startup and shutdown sequence. If necessary, issue the commands to create the links.

   # ln -s ../init.d/afs /etc/rc2.d/S35afs
  
   # ln -s ../init.d/afs /etc/rc0.d/K35afs   

(Optional) If the machine is configured as a client, 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 distribution if necessary.

   # cd /usr/vice/etc
   
   # rm afs.rc
  
   # ln -s  /etc/init.d/afs  afs.rc   

Reboot the machine.

   # shutdown -i6 -g0 -y   

If you are upgrading a server machine, login again as the local superuser root, then return to Step 6 in Upgrading Server Machines.

   login: root
   Password: root_password