RXK5DEVEL-mdw-rxk5-m58-20080103

merge in latest changes from openafs-devel-1_5_x
update to rxk5-m58

Makefile.in

@@ -443,7 +443,7 @@ volser_depinstall: pinstall rxgen comerr
 	${COMPILE_PART1} volser ${COMPILE_DEPINSTALL}
 
 ${DEST}/bin/dedebug: dedebug
-	${INSTALL} -s $? $@
+	${INSTALL} $? $@
 
 
 #
@@ -722,6 +722,7 @@ clean2:
 	-${COMPILE_PART1} libafsauthent ${COMPILE_CLEAN}
 	-${COMPILE_PART1} shlibafsrpc ${COMPILE_CLEAN}
 	-${COMPILE_PART1} shlibafsauthent ${COMPILE_CLEAN}
+	-${COMPILE_PART1} platform ${COMPILE_CLEAN}
 	-${COMPILE_PART1} libadmin ${COMPILE_CLEAN}
 	-${COMPILE_PART1} libadmin/adminutil ${COMPILE_CLEAN}
 	-${COMPILE_PART1} libadmin/client ${COMPILE_CLEAN}

README

@@ -71,6 +71,30 @@ A. Creating the proper directory structure.
       or insecure software included with OpenAFS. See README.OBSOLETE and
       README.SECURITY for more details.
 
+      There is an option to control whether or not binaries are stripped
+      of their symbol table information.  All binaries, except for the
+      'fileserver' and 'volserver' executables, are stripped by default.
+
+      To prevent stripping, specify the '--disable-strip-binaries' option on
+      the ./configure command line.
+
+      This option works alongside the existing --enable-debug option to
+      control how binaries are produced.  When --enable-debug is specified,
+      binaries will not be stripped.  This behavior can be modified by
+      using different combinations of --enable-debug and --enable (or
+      --disable)-strip-binaries.  One can, for example, compile binaries for
+      debug and strip them anyway.  Alternatively, one can compile without
+      debug and force the binaries to not be stripped.  Note that these
+      combinations are not necessarily useful.
+
+      If neither of these options is specified, the default will be to build
+      non-debug binaries that are stripped (with the exceptions noted above,
+      which are never stripped at present).  Specifying --enable-debug also
+      turns on --disable-strip-binaries.  These are the most useful settings.
+
+      The two binaries noted above, 'fileserver' and 'volserver' will never
+      be stripped, regardless of any options given to configure.
+
   There are two modes for directory path handling: "Transarc mode" and "default mode":
   - In Transarc mode, we retain compatibility with Transarc/IBM AFS tools
     by putting client configuaration files in /usr/vice/etc, and server

README-NT

@@ -53,7 +53,7 @@ The following steps describe how to configure Windows 2000/XP:
    F. Build the binaries
    G. Install NSIS 2.30
    H. Build NSIS Install Package
-   I. Install Wix 2.0.4310
+   I. Install Wix 2.0.5325
    J. Build Wix MSI Install Package
    K. Final Results
    L. Optional Items
@@ -97,8 +97,8 @@ version is supported:
 The WiX installer requires about 18 MB of storage.  The following 
 version is supported:
 
-    Wix 2.0.4310.0
+    Wix 2.0.5325.0
-      http://prdownloads.sourceforge.net/wix/sources-2.0.4310.0.zip
+      http://prdownloads.sourceforge.net/wix/sources-2.0.5325.0.zip
 
 The InstallShield scripts (although not supported) require version 5.5
 of InstallShiled. Version 6.0 or higher of InstallShield are not 
@@ -352,119 +352,9 @@ From the %AFSROOT% directory execute:
 
 STEP I.  Install Wix MSI Installer
 
-Download the Wix 2.0.2217.0 installer from 
+Download the Wix 2.0.5325.0 installer from 
 
-    http://prdownloads.sourceforge.net/wix/sources-2.0.2217.0.zip
+    http://prdownloads.sourceforge.net/wix/sources-2.0.5325.0.zip
-
-Apply the following patches to the source tree and execute 
-
-    make ship
-
-from the \src\wix directory.  
-
-Index: src/wix/Common.cs
-===================================================================
-RCS file: /cvsroot/wix/wix/src/wix/Common.cs,v
-retrieving revision 1.7
-diff -w -r1.7 Common.cs
-140a141,146
-> 		public static long GetFileTimeFromDateTime(string dateTime) 
-> 		{
-> 			System.DateTime sdt = System.Xml.XmlConvert.ToDateTime(dateTime);
-> 			return sdt.ToFileTime();
-> 		}
-> 
-Index: src/wix/Compiler.cs
-===================================================================
-RCS file: /cvsroot/wix/wix/src/wix/Compiler.cs,v
-retrieving revision 1.14
-diff -w -r1.14 Compiler.cs
-847c847
-<                     this.AddRegistryKey(sourceLineNumbers, null, MsiInterop.MsidbRegistryRootClassesRoot, String.Concat("CLSID\\", classId, "\\", context[i]), String.Empty, String.Concat("\"[!", fileServer, "]", argument == null ? String.Empty : " ", argument, "\""), componentId); // ClassId context
----
->                     this.AddRegistryKey(sourceLineNumbers, null, MsiInterop.MsidbRegistryRootClassesRoot, String.Concat("CLSID\\", classId, "\\", context[i]), String.Empty, String.Concat("\"[#", fileServer, "]", argument == null ? String.Empty : " ", argument, "\""), componentId); // ClassId context
-2352a2353,2358
-> 			// if a Value attribute was given by itself, make this a type 19 custom action
-> 			if( sourceBits == 0 && targetBits == MsiInterop.MsidbCustomActionTypeTextData ) 
-> 			{
-> 				sourceBits = MsiInterop.MsidbCustomActionTypeSourceFile;
-> 			}
-> 
-3881c3887
-<                         minDate = attrib.Value;
----
->                         minDate = Common.GetFileTimeFromDateTime( attrib.Value ).ToString();
-3884c3890
-<                         maxDate = attrib.Value;
----
->                         maxDate = Common.GetFileTimeFromDateTime( attrib.Value ).ToString();
-8187a8194,8207
-> 					case "Delete":
-> 						switch (attrib.Value)
-> 						{
-> 							case "install":
-> 								events |= MsiInterop.MsidbServiceControlEventDelete;
-> 								break;
-> 							case "uninstall":
-> 								events |= MsiInterop.MsidbServiceControlEventUninstallDelete;
-> 								break;
-> 							case "both":
-> 								events |= MsiInterop.MsidbServiceControlEventDelete | MsiInterop.MsidbServiceControlEventUninstallDelete;
-> 								break;
-> 						}
-> 						break;
-9685a9706
-> 
-Index: src/wix/Preprocessor.cs
-===================================================================
-RCS file: /cvsroot/wix/wix/src/wix/Preprocessor.cs,v
-retrieving revision 1.6
-diff -w -r1.6 Preprocessor.cs
-274c274
-<                             context = new IfContext(context.IsTrue & context.Active, this.variables.ContainsKey(reader.Value.Trim()), IfState.If);
----
->                             context = new IfContext(context.IsTrue & context.Active, this.IsDefined(reader.Value.Trim()), IfState.If);
-279c279
-<                             context = new IfContext(context.IsTrue & context.Active, !this.variables.ContainsKey(reader.Value.Trim()), IfState.If);
----
->                             context = new IfContext(context.IsTrue & context.Active, !this.IsDefined(reader.Value.Trim()), IfState.If);
-360a361,362
-> 						case "error":
-> 							throw new WixPreprocessorException(this.GetCurrentSourceLineNumbers(), this.PreprocessVariables(reader.Value));
-419a422,437
-> 		/// Returns true if the symbol exists.
-> 		/// </summary>
-> 		/// <param name="symbol">symbol name to check</param>
-> 		/// <returns>true if symbol is defined</returns>
-> 		private bool IsDefined(string symbol)
-> 		{
-> 			if( symbol.StartsWith("env.") )
-> 				return Environment.GetEnvironmentVariable(symbol.Substring(4)) != null;
-> 			if( symbol.StartsWith("var.") )
-> 				return this.variables.ContainsKey(symbol.Substring(4));
-> 			if( symbol.StartsWith("sys.") )
-> 				return this.systemVariables.ContainsKey(symbol.Substring(4));
-> 			return this.variables.ContainsKey(symbol);
-> 		}
-> 
->         /// <summary>
-Index: src/wix/wix.csproj
-===================================================================
-RCS file: /cvsroot/wix/wix/src/wix/wix.csproj,v
-retrieving revision 1.4
-diff -w -r1.4 wix.csproj
-661a662,666
->                     RelPath = "Xsd\wix.xsx"
->                     DependentUpon = "wix.xsd"
->                     BuildAction = "None"
->                 />
->                 <File
-664a670,674
->                 <File
->                     RelPath = "Xsd\wixloc.xsx"
->                     DependentUpon = "wixloc.xsd"
->                     BuildAction = "None"
->                 />
 
 
 STEP J.  Build Wix MSI install package

README-WIN9X

@@ -1,200 +0,0 @@
-Copyright 2000, International Business Machines Corporation and others.
-All Rights Reserved.
-
-This software has been released under the terms of the IBM Public
-License.  For details, see the LICENSE file in the top-level source
-directory or online at http://www.openafs.org/dl/license10.html
-
-NOTE: As of the OpenAFS 1.3 release series, Windows 9x platforms are no
-longer officially supported.  It is not clear whether or not the source
-tree will build successfully or not.  As far as we know, no one has tried
-in a very long time.
-
-Building Open AFS on Win 95
----------------------------
-
-The Windows 95 Open AFS client consists of two main components: the client
-program afsd.exe, which is compiled with the DJGPP compiler and runs in a
-DOS virtual machine; and the utility programs, which are built on Windows
-NT or 9x using the Microsoft Visual C++ compiler V6.0.
-
-afsd.exe
---------
-
-afsd.exe is built using the DJGPP cross-compiler, executed from Linux.
-It should also be possible to build it using the native DOS DJGPP compiler,
-but we did not try this.  You will need to install the following packages
-from DJGPP and the Coda project.
-
-ftp://ftp.coda.cs.cmu.edu/pub/tools/djgpp-2.01_0.93_glibc-1.i386.rpm
-ftp://ftp.coda.cs.cmu.edu/pub/tools/djgpp-win95ext-2.01_0.93_glibc-1.i386.rpm
-ftp://ftp.coda.cs.cmu.edu/pub/tools/gdb-djgpp-4.16-2.i386.rpm
-
-You will also need the MMAP.VXD and SOCK.VXD from the Coda project.  Source
-is available here:
-ftp://ftp.coda.cs.cmu.edu/pub/coda/src/win95-coda-5.2.0.zip
-
-Follow the Coda instructions to build these VXD's, which you can read here:
-http://www.coda.cs.cmu.edu/doc/html/coda-howto-6.html#ss6.4
-
-Once you have the necessary tools installed, set the following environment
-variables:
-SYS_NAME: set to i386_djgpp
-LINUX_SYS: set to the sysname of the Linux version you are using, e.g.,
-           i386_linux22
-
-The makefile expects to build into a platform directory with symlinks
-into the source directory.  The Perl script "mkdest.pl" in this dir. will
-set this up for you.  To use it, create a directory under the top-level
-dir. (the directory above src) called "i386_djgpp".  Then cd to that
-directory and type "../src/mkdest.pl <absolute path of your src dir.>"
-
-Then execute "make -f Makefile.djgpp" from the top-level directory.
-(You can create a symlink to src/Makefile.djgpp from this dir.)
-The afsd.exe will be built into i386_djgpp/dest/bin.
-
-Build notes:
-
-  The Makefile.djgpp actually builds Linux versions of the utilities
-  rxgen, install, compile_et, and util.a.  It uses the Linux version
-  of param.h which it copies to the afs subdirectory of the above
-  components.  You will need to set SYS_NAME to your Linux system name
-  manually if you want to build these utilities separately.
-
-Utilities and GUI programs
---------------------------
-
-The rest of the support programs are built as Win32 executables from a
-Windows 9x or NT system.  You will need to set the following environment
-variables:
-
-set SYS_NAME=i386_win95
-set AFSDEV_BUILDTYPE=CHECKED (or FREE if you want to skip debugging info.)
-set AFSDEV_INCLUDE=<path of your Visual C include files>
-set AFSDEV_LIB=<path of your Visual C libs>
-set AFSDEV_BIN=.
-set AFSROOT=<PATH to base of development directory> 
-	e.g. AFSROOT\SRC is source directory of the build tree
-SET _WIN32_IE=0x400
-set OBJ=src or obj, see below
-set MSSDK=<path to sdk header files>, see below
-
-If you are building on a Unix directory exported to Windows through Samba
-or AFS, you can create a platform directory named "i386_win95" using the
-"mkdest.pl" script as described above (run from a Unix system).  This will
-only work on a file system that supports symbolic links.  If you are using
-a platform directory, set the OBJ environment var. to "obj" and create
-a symlink "obj" in the top-level dir. that points to "i386_win95/obj".
-Otherwise, set OBJ to "src" to build the objects with the sources.
-
-The environment variable AFSROOT points to the parent of the AFS src
-directory.  Executables will be built by default in AFSROOT\dest.
-
-Copy the file src\NTMake9x to the parent of the src directory.  You only
-need to do this once.  If you are building on a local drive, copy
-AFSROOT\src\symlink.bat to AFSROOT\.
-
-Follow the NT build instructions in file "README-NT" to perform the build.
-You will be using "NTMake9x" as the top-level makefile, instead of
-"NTMakefile".  Most of the instructions in "README-NT" apply to the Win9x
-build as well.
-
-Build Notes:
-
-1) If you are building the Windows 9x AFS Client Control Panel
-   (win9xpanel), it requires shlwapi.h.  This file can be found in the
-   header files associated with the Windows SDK (95/98 NT or W2000).
-
-2) You can build the Windows 9x client from a Windows NT or W2000 system.
-   This requires you to edit AFSROOT\config\NTMakefile.i386_win95.
-   Change line: DEL = $(AFSROOT)\src\rmbat
-		 to:  DEL = -del  /q /f
-
-3) If you build the W2000 client, then switch to building the Windows 95
-   client (or vice versa), you should clean the previous build by either:
-	nmake -f ntmakefile clean 
-or 	nmake -f ntmake9x clean
-
-4) When building the "comerr" component, the makefile now uses the
-   existing error_table_nt.c file (and touches it so it will be up to date
-   by default.)  If you make changes to the lex or yacc source files and want
-   to rebuild error_table_nt.c, you can simply delete it and rerun make,
-   which will cause the file to be built using lex and yacc.  Make sure
-   you have these utilities on your system.
-
-5) Required DLL's for redistribution
-
-   The AFS Control Panel for Win95/98 requires Microsoft DLL's that can
-   be installed using:
-      VC6RedistSetup_enu.exe
-   This is located at:
-      http://support.microsoft.com/support/kb/articles/Q259/4/03.ASP
-	Two Microsoft DLL's must be included at DEST\WinInstall\Config\.
-	   SHLWAPI.DLL
-	   WININET.DLL  
-	These DLL's will not be left on the target machine, there are only
-	used for installation and removed after installation is complete.
-
-6) Required changes to configuration file .\src\config\NTMakefile.i386_win95
-
-AFSPRODUCT_VERSION  - Product version
-CELLNAME_DEFAULT - The default AFS cell name
-CELLSERVDB_INSTALL - The default name for the CellServDB included in the install script
-CELLSERVDB_WEB  - The default web address to obtain CellServDB
-		  
-For Example:
-
- .\src\config\NTMakefile.i386_win95  
-   AFSPRODUCT_VERSION=1.1.1a
-   CELLNAME_DEFAULT=openafs.org
-   CELLSERVDB_INSTALL=CellServDB.GrandCentral
-   CELLSERVDB_WEB=http://grand.central.org/dl/cellservdb/CellServDB
-
-Version level may be specified in different formats, for example the following
-forms all have the same version level; however will be displayed differently:
-
-AFSPRODUCT_VERSION=1.1.1a
-AFSPRODUCT_VERSION=1.1.1 a
-AFSPRODUCT_VERSION=1.1.1.1
-AFSPRODUCT_VERSION=1.1.101
-
-6) Installation
-
-   First, execute "nmake /f ntmake9x media" to copy all the client
-   executables and other files to DEST\WinInstall.
-
-   You can then install the client onto a target Windows 9x machine by
-   executing:
-     install.bat <source> <drive> <install dir.> <home cell> <cache size in 1K blocks>
-   For example,
-     install.bat DEST\WinInstall\ c: \afscli almaden.ibm.com 40000
-
-   If you do not wish to use the batch file, you can install the client
-   manually by performing the following steps.
-
-   1. On the target machine, copy all the files from DEST\WinInstall to the
-      install location (usually c:\afscli).
-   2. Add entries to the target's AUTOEXEC.BAT file as follows:
-       set AFSCONF=c:\afscli (replace with your install dir.)
-       path %path%;c:\afscli
-   3. Copy the template.reg file to afscli.reg.  Replace any references
-      to c: and afscli with your install location.  Double click on the
-      afscli.reg file to add the registry entries to the target system.
-   4. Create the following AFS configuration files in the install dir.:
-      - ThisCell:
-        containing the name of your home cell
-      - cache.info:
-        containing your cache configuration.  For example,
-        to configure a cache of 40,000 1KB blocks with a disk cache
-        location of c:\afscache, you would enter in this file:
-            /afs:c:\afscache;40000
-        (The cache location has no effect unless you have enabled
-        the experimental disk cache support.)
-      - CellServDB:
-        the cell server database.  You can get the latest version from AFS:
-        /afs/transarc.com/service/etc/CellServDB.export
-   5. Reboot the target machine.
-   6. You can now start the client by executing the program WinAfsLoad.exe
-      from the install directory.
-
-

acinclude.m4

@@ -120,6 +120,9 @@ AC_ARG_ENABLE(optimize-kernel,
 AC_ARG_ENABLE(debug,
 [  --enable-debug			enable compilation of the user space code with debugging information (defaults to disabled)],, enable_debug="no"
 )
+AC_ARG_ENABLE(strip-binaries,
+[  --disable-strip-binaries             disable stripping of symbol information from binaries (defaults to enabled)],, enable_strip_binaries="maybe"
+)
 AC_ARG_ENABLE(optimize,
 [  --disable-optimize			disable optimization for compilation of the user space code (defaults to enabled)],, enable_optimize="yes"
 )
@@ -350,6 +353,14 @@ else
 			AFS_PARAM_COMMON=param.nbsd20.h
 			AFS_SYSNAME="amd64_nbsd20"
 			;;
+		x86_64-*-netbsd*3.[0-8]*)
+			AFS_PARAM_COMMON=param.nbsd30.h
+			AFS_SYSNAME="amd64_nbsd30"
+			;;
+		x86_64-*-netbsd*4.[0-8]*)
+			AFS_PARAM_COMMON=param.nbsd40.h
+			AFS_SYSNAME="amd64_nbsd40"
+			;;
 		powerpc-*-netbsd*2.0*)
 			AFS_PARAM_COMMON=param.nbsd20.h
 			AFS_SYSNAME="ppc_nbsd20"
@@ -625,10 +636,16 @@ case $AFS_SYSNAME in *_linux* | *_umlinux*)
 		 fi
 
 		 LINUX_KERNEL_COMPILE_WORKS
+                 LINUX_KBUILD_USES_EXTRA_CFLAGS
+                 LINUX_HAVE_CURRENT_KERNEL_TIME
+                 LINUX_KMEM_CACHE_INIT
+		 LINUX_HAVE_KMEM_CACHE_T
+		 LINUX_KMEM_CACHE_CREATE_TAKES_DTOR
 dnl XXX ask about LINUX_KERNEL_HAS_NFSSRV
 		 LINUX_KERNEL_HAS_NFSSRV
 		 LINUX_CONFIG_H_EXISTS
 		 LINUX_COMPLETION_H_EXISTS
+		 LINUX_EXPORTFS_H_EXISTS
 		 LINUX_DEFINES_FOR_EACH_PROCESS
 		 LINUX_DEFINES_PREV_TASK
 		 LINUX_FS_STRUCT_SUPER_HAS_ALLOC_INODE
@@ -656,12 +673,15 @@ dnl XXX ask about LINUX_KERNEL_HAS_NFSSRV
 	  	 LINUX_FOP_F_FLUSH_TAKES_FL_OWNER_T
 	  	 LINUX_AOP_WRITEBACK_CONTROL
 		 LINUX_FS_STRUCT_FOP_HAS_FLOCK
+		 LINUX_FS_STRUCT_FOP_HAS_SENDFILE
+		 LINUX_FS_STRUCT_FOP_HAS_SPLICE
 		 LINUX_KERNEL_LINUX_SYSCALL_H
 		 LINUX_KERNEL_LINUX_SEQ_FILE_H
 		 LINUX_KERNEL_POSIX_LOCK_FILE_WAIT_ARG
 		 LINUX_KERNEL_SELINUX
 		 LINUX_KERNEL_SOCK_CREATE
 		 LINUX_KERNEL_PAGE_FOLLOW_LINK
+                 LINUX_KEY_TYPE_H_EXISTS
 		 LINUX_NEED_RHCONFIG
 		 LINUX_RECALC_SIGPENDING_ARG_TYPE
 		 LINUX_SCHED_STRUCT_TASK_STRUCT_HAS_PARENT
@@ -679,6 +699,7 @@ dnl XXX ask about LINUX_KERNEL_HAS_NFSSRV
 		 LINUX_GET_SB_HAS_STRUCT_VFSMOUNT
 		 LINUX_STATFS_TAKES_DENTRY
 		 LINUX_FREEZER_H_EXISTS
+		 LINUX_HAVE_SVC_ADDR_IN
 		 if test "x$ac_cv_linux_freezer_h_exists" = "xyes" ; then
 		  AC_DEFINE(FREEZER_H_EXISTS, 1, [define if you have linux/freezer.h])
 		 fi
@@ -689,6 +710,7 @@ dnl XXX ask about LINUX_KERNEL_HAS_NFSSRV
 		 LINUX_GENERIC_FILE_AIO_READ
 		 LINUX_INIT_WORK_HAS_DATA
 		 LINUX_REGISTER_SYSCTL_TABLE_NOFLAG
+		 LINUX_SYSCTL_TABLE_CHECKING
                  LINUX_EXPORTS_SYS_CHDIR
                  LINUX_EXPORTS_SYS_CLOSE
                  LINUX_EXPORTS_SYS_OPEN
@@ -762,6 +784,12 @@ dnl XXX ask about LINUX_KERNEL_HAS_NFSSRV
 		 if test "x$ac_cv_linux_config_h_exists" = "xyes" ; then
 		  AC_DEFINE(CONFIG_H_EXISTS, 1, [define if config.h exists])
 		 fi
+		 if test "x$ac_cv_linux_exportfs_h_exists" = "xyes"; then
+		  AC_DEFINE(EXPORTFS_H_EXISTS, 1, [define if linux/exportfs.h exists])
+		 fi
+		 if test "x$ac_cv_linux_key_type_h_exists" = "xyes" ; then
+		  AC_DEFINE(KEY_TYPE_H_EXISTS, 1, [define if key-type.h exists])
+		 fi
 		 if test "x$ac_cv_linux_defines_for_each_process" = "xyes" ; then
 		  AC_DEFINE([DEFINED_FOR_EACH_PROCESS], 1, [define if for_each_process defined])
 		 fi
@@ -900,17 +928,41 @@ dnl XXX ask about LINUX_KERNEL_HAS_NFSSRV
 		 if test "x$ac_cv_linux_fs_struct_fop_has_flock" = "xyes" ; then
 		  AC_DEFINE(STRUCT_FILE_OPERATIONS_HAS_FLOCK, 1, [define if your struct file_operations has flock])
 		 fi
+		 if test "x$ac_cv_linux_fs_struct_fop_has_sendfile" = "xyes" ; then
+		  AC_DEFINE(STRUCT_FILE_OPERATIONS_HAS_SENDFILE, 1, [define if your struct file_operations has sendfile])
+		 fi
+		 if test "x$ac_cv_linux_fs_struct_fop_has_splice" = "xyes" ; then
+		  AC_DEFINE(STRUCT_FILE_OPERATIONS_HAS_SPLICE, 1, [define if your struct file_operations has splice_write and splice_read])
+		 fi
 		 if test "x$ac_cv_linux_register_sysctl_table_noflag" = "xyes" ; then
 		  AC_DEFINE(REGISTER_SYSCTL_TABLE_NOFLAG, 1, [define if register_sysctl_table has no insert_at head flag])
 		 fi
+		 if test "x$ac_cv_linux_sysctl_table_checking" = "xyes" ; then
+		  AC_DEFINE(SYSCTL_TABLE_CHECKING, 1, [define if your kernel has sysctl table checking])
+		 fi
 		 if test "x$ac_cv_linux_exports_tasklist_lock" = "xyes" ; then
 		  AC_DEFINE(EXPORTED_TASKLIST_LOCK, 1, [define if tasklist_lock exported])
 		 fi
+		 if test "x$ac_cv_linux_have_kmem_cache_t" = "xyes" ; then
+		  AC_DEFINE(HAVE_KMEM_CACHE_T, 1, [define if kmem_cache_t exists])
+		 fi
+		 if test "x$ac_cv_linux_kmem_cache_init" = "xyes" ; then
+		  AC_DEFINE(KMEM_CACHE_INIT, 1, [define for new kmem_cache init function parameters])
+		 fi
+		 if test "x$ac_cv_linux_have_current_kernel_time" = "xyes" ; then
+		  AC_DEFINE(HAVE_CURRENT_KERNEL_TIME, 1, [define if current_kernel_time() exists])
+		 fi
+		 if test "x$ac_cv_linux_have_kmem_cache_t" = "xyes" ; then
+		  AC_DEFINE(KMEM_CACHE_TAKES_DTOR, 1, [define if kmem_cache_create takes a destructor argument])
+		 fi
 		 if test "x$ac_cv_linux_kernel_page_follow_link" = "xyes" -o "x$ac_cv_linux_func_i_put_link_takes_cookie" = "xyes"; then
 		  AC_DEFINE(USABLE_KERNEL_PAGE_SYMLINK_CACHE, 1, [define if your kernel has a usable symlink cache API])
 		 else
 		  AC_MSG_WARN([your kernel does not have a usable symlink cache API])
 		 fi
+		 if test "x$ac_cv_linux_have_svc_addr_in" = "xyes"; then
+		  AC_DEFINE(HAVE_SVC_ADDR_IN, 1, [define if svc_add_in exists])
+                 fi
                 :
 		fi
 esac
@@ -1226,7 +1278,7 @@ dnl checks for header files.
 AC_HEADER_STDC
 AC_HEADER_SYS_WAIT
 AC_HEADER_DIRENT
-AC_CHECK_HEADERS(stdlib.h string.h unistd.h fcntl.h sys/time.h sys/file.h)
+AC_CHECK_HEADERS(stdlib.h string.h unistd.h poll.h fcntl.h sys/time.h sys/file.h)
 AC_CHECK_HEADERS(netinet/in.h netdb.h sys/fcntl.h sys/mnttab.h sys/mntent.h)
 AC_CHECK_HEADERS(mntent.h sys/vfs.h sys/param.h sys/fs_types.h sys/fstyp.h)
 AC_CHECK_HEADERS(sys/mount.h strings.h termios.h signal.h)

configure-libafs.in

@@ -1,8 +1,11 @@
 AC_INIT(src/libafs/Makefile.common.in)
-AM_INIT_AUTOMAKE(openafs-libafs,1.5.25)
+AM_INIT_AUTOMAKE(openafs-libafs,1.5.28)
 AC_CONFIG_HEADER(src/config/afsconfig.h)
-define(OPENAFS_CONFIGURE_LIBAFS)
+MACOS_VERSION=1.5.28
 
+AC_SUBST(MACOS_VERSION)
+
+define(OPENAFS_CONFIGURE_LIBAFS)
 AC_PROG_CC
 OPENAFS_CONFIGURE_COMMON
 

configure.in

@@ -1,9 +1,13 @@
-AC_INIT(openafs,1.5.25)
+AC_INIT(openafs,1.5.28)
 AC_CONFIG_SRCDIR(src/config/stds.h)
 AM_INIT_AUTOMAKE
 AC_CONFIG_HEADER(src/config/afsconfig.h)
+MACOS_VERSION=1.5.28
+
+AC_SUBST(MACOS_VERSION)
 
 AC_PROG_CC
+AC_CHECK_PROGS(CPP,[/lib/cpp /usr/bin/cpp /usr/ccs/lib/cpp cpp])
 OPENAFS_CONFIGURE_COMMON
 
 if test -e 'doc/man-pages/Makefile.in' ; then
@@ -81,6 +85,10 @@ src/lwp/test/Makefile \
 src/mpp/Makefile \
 src/null/Makefile \
 src/package/Makefile \
+src/packaging/MacOS/OpenAFS.Info.plist \
+src/packaging/MacOS/OpenAFS.info \
+src/packaging/MacOS/buildpkg.sh \
+src/packaging/RedHat/openafs.spec \
 src/pam/Makefile \
 src/pinstall/Makefile \
 src/pinstall/test/Makefile \

doc/man-pages/README

@@ -78,7 +78,10 @@ Formatting Standards
   documents common options, and discusses the general use of the suite.
   Then, each operation code in the suite should have a separate man page,
   named after the command with the space between the command suite and the
-  operation code replaced with an underscore.
+  operation code replaced with an underscore.  The NAME section of the
+  operation man page must also use an underscore (fs_listacl, not fs
+  listacl) for compatibility with some man programs.  The SYNOPSIS section
+  should, of course, use a space, since that's what the user must type.
 
   All man pages must follow the standard layout for man page sections and
   formatting.  The best general reference is the pod2man man page,
@@ -199,17 +202,13 @@ Known Problems
    * The following installed commands have no man pages:
 
        copyauth
-       fs rxstatpeer
        fs rxstatproc
        fs setcbaddr
-       kseal
-       read_tape
        restorevol
        rmtsysd
        vldb_convert
        vos clone
-       vos convertROtoRW
+       vos setfields
-       vos copy
        vos shadow
        vsys
 
@@ -221,9 +220,6 @@ Known Problems
    * Some of the documentation in fs getserverprefs needs minor updates to
      reflect what happens in the dynroot case.
 
-   * fs sysname documentation needs to include the possibility of setting
-     multiple sysnames and the resulting behavior.
-
    * bos listkeys and the KeyFile man page assume that you're using the
      kaserver.
 

doc/man-pages/pod1/fs_apropos.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs apropos - Displays each help entry containing a keyword string
+fs_apropos - Displays each help entry containing a keyword string
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_checkservers.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs checkservers - Displays the status of server machines
+fs_checkservers - Displays the status of server machines
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_checkvolumes.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs checkvolumes - Forces the Cache Manager to update volume information
+fs_checkvolumes - Forces the Cache Manager to update volume information
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_cleanacl.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs cleanacl - Remove obsolete entries from an ACL
+fs_cleanacl - Remove obsolete entries from an ACL
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_copyacl.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs copyacl - Copies an ACL from a directory to one or more other directories
+fs_copyacl - Copies an ACL from a directory to one or more other directories
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_diskfree.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs diskfree - Shows data about the partition housing a directory or file
+fs_diskfree - Shows data about the partition housing a directory or file
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_examine.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs examine - Shows data about the volume containing a directory or file
+fs_examine - Shows data about the volume containing a directory or file
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_exportafs.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs exportafs - Configures export of AFS to clients of other file systems
+fs_exportafs - Configures export of AFS to clients of other file systems
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_flush.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs flush - Forces the Cache Manager to discard a cached file or directory
+fs_flush - Forces the Cache Manager to discard a cached file or directory
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_flushall.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs flushall - Force the AFS Cache Manager to discard all data
+fs_flushall - Force the AFS Cache Manager to discard all data
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_flushmount.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs flushmount - Forces the Cache Manager to discard a mount point
+fs_flushmount - Forces the Cache Manager to discard a mount point
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_flushvolume.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs flushvolume - Forces the Cache Manager to discard cached data from a volume
+fs_flushvolume - Forces the Cache Manager to discard cached data from a volume
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_getcacheparms.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs getcacheparms - Displays the current size and usage of the cache
+fs_getcacheparms - Displays the current size and usage of the cache
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_getcalleraccess.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs getcalleraccess - Show the current user's access to a file or directory
+fs_getcalleraccess - Show the current user's access to a file or directory
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_getcellstatus.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs getcellstatus - Reports whether setuid programs are honored in a cell
+fs_getcellstatus - Reports whether setuid programs are honored in a cell
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_getclientaddrs.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs getclientaddrs - Displays the client interfaces to register
+fs_getclientaddrs - Displays the client interfaces to register
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_getcrypt.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs getcrypt - Displays the state of encryption for AFS file transfers
+fs_getcrypt - Displays the state of encryption for AFS file transfers
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_getserverprefs.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs getserverprefs - Displays preference ranks for file servers or VL servers
+fs_getserverprefs - Displays preference ranks for file servers or VL servers
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_help.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs help - Displays help for fs commands
+fs_help - Displays help for fs commands
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_listacl.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs listacl - Displays ACLs
+fs_listacl - Displays ACLs
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_listaliases.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs listaliases - Displays the current list of aliases for AFS cells
+fs_listaliases - Displays the current list of aliases for AFS cells
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_listcells.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs listcells - Displays the database server machines known to the Cache Manager
+fs_listcells - Displays the database server machines known to the Cache Manager
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_listquota.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs listquota - Displays quota information for a volume
+fs_listquota - Displays quota information for a volume
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_lsmount.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs lsmount - Reports the volume for which a directory is the mount point.
+fs_lsmount - Reports the volume for which a directory is the mount point.
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_messages.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs messages - Sets whether the Cache Manager writes log messages
+fs_messages - Sets whether the Cache Manager writes log messages
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_mkmount.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs mkmount - Creates a mount point for a volume
+fs_mkmount - Creates a mount point for a volume
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_newalias.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs newalias - Creates a new alias for a cell
+fs_newalias - Creates a new alias for a cell
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_newcell.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs newcell - Changes the kernel-resident list of a cell's database servers
+fs_newcell - Changes the kernel-resident list of a cell's database servers
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_quota.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs quota - Displays the quota used in the volume containing a directory or file
+fs_quota - Displays the quota used in the volume containing a directory or file
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_rmmount.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs rmmount - Removes a mount point
+fs_rmmount - Removes a mount point
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_rxstatpeer.pod

@@ -0,0 +1,67 @@
+=head1 NAME
+
+fs_rxstatpeer - Enables Rx packet logging in the OpenAFS kernel module
+
+=head1 SYNOPSIS
+
+=for html
+<div class="synopsis">
+
+B<fs rxstatpeer> [B<-clear>] [B<-disable>] [B<-enable>] [B<-help>]
+
+=for html
+</div>
+
+=head1 DESCRIPTION
+
+B<fs rxstatpeer> manipulates some of the Rx protocol counters in the
+OpenAFS kernel interface.
+
+=head1 OPTIONS
+
+=over 4
+
+=item B<-clear>
+
+Clear the Rx stats for peers in the kernel module.
+
+=item B<-disable>
+
+Disable logging of Rx stats for peers in the kernel module.
+
+=item B<-enable>
+
+Enable logging of Rx stats for peers in the kernel module.
+
+=item B<-help>
+
+Prints the online help for this command. All other valid options are
+ignored.
+
+=back
+
+=head1 OUTPUT
+
+This command produces no output other than error messages.
+
+=head1 EXAMPLES
+
+Enable Rx Stats for peers:
+
+   % fs rxstatpeer -enable
+
+=head1 PRIVILEGE REQUIRED
+
+The issuer must be logged in as the local superuser root.
+
+=head1 SEE ALSO
+
+L<fs(1)>,
+L<rxdebug(1)>
+
+=head1 COPYRIGHT
+
+Copyright 2007 Jason Edgecombe <jason@rampaginggeek.com>
+
+This documentation is covered by the IBM Public License Version 1.0. This
+man page was written by Jason Edgecombe for OpenAFS.

doc/man-pages/pod1/fs_setacl.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs setacl - Sets the ACL for a directory
+fs_setacl - Sets the ACL for a directory
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_setcachesize.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs setcachesize - Sets the size of the disk cache
+fs_setcachesize - Sets the size of the disk cache
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_setcell.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs setcell - Configures permissions for setuid programs from specified cells
+fs_setcell - Configures permissions for setuid programs from specified cells
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_setclientaddrs.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs setclientaddrs - Sets the client interfaces to register with the File Server
+fs_setclientaddrs - Sets the client interfaces to register with the File Server
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_setcrypt.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs setcrypt - Enables of disables the encryption of AFS file transfers
+fs_setcrypt - Enables of disables the encryption of AFS file transfers
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_setquota.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs setquota - Sets the quota for the volume containing a file or directory
+fs_setquota - Sets the quota for the volume containing a file or directory
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_setserverprefs.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs setserverprefs - Sets the preference ranks for file servers or VL servers
+fs_setserverprefs - Sets the preference ranks for file servers or VL servers
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_setvol.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs setvol - Set quota and messages for a volume containing a file or directory
+fs_setvol - Set quota and messages for a volume containing a file or directory
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_storebehind.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs storebehind - Enables asynchronous writes to the file server
+fs_storebehind - Enables asynchronous writes to the file server
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_sysname.pod

@@ -1,15 +1,15 @@
 =head1 NAME
 
-fs sysname - Reports or sets the CPU/operating system type
+fs_sysname - Reports or sets the CPU/operating system type
 
 =head1 SYNOPSIS
 
 =for html
 <div class="synopsis">
 
-B<fs sysname> S<<< [B<-newsys> <I<new sysname>>] >>> [B<-help>]
+B<fs sysname> S<<< [B<-newsys> <I<new sysname>>]+ >>> [B<-help>]
 
-B<fs sy> S<<< [B<-n> <I<new sysname>>] >>> [B<-h>]
+B<fs sy> S<<< [B<-n> <I<new sysname>>]+ >>> [B<-h>]
 
 =for html
 </div>
@@ -19,7 +19,7 @@ B<fs sy> S<<< [B<-n> <I<new sysname>>] >>> [B<-h>]
 The B<fs sysname> command sets or displays the local machine's
 CPU/operating system type as recorded in kernel memory. The Cache Manager
 substitutes the string for the I<@sys> variable which can occur in AFS
-pathnames; the I<IBM AFS Quick Beginnings> and I<IBM AFS Administration
+pathnames; the I<OpenAFS Quick Beginnings> and I<OpenAFS Administration
 Guide> explain how using I<@sys> can simplify cell configuration. It is
 best to use it sparingly, however, because it can make the effect of
 changing directories unpredictable.
@@ -42,10 +42,14 @@ must verify that the correct string is set for the new identity also.
 
 =item B<-newsys> <I<new sysname>>
 
-Sets the CPU/operating system indicator string for the local machine. If
+Sets the CPU/operating system indicator string for the local machine. This
-this argument is omitted, the output displays the current setting
+option may be used multiple times in the same invocation, which sets I<@sys>
-instead. AFS uses a standardized set of strings; consult the I<IBM AFS
+to an array of values. When I<@sys> contains an array of values, the first
-Quick Beginnings> or I<AFS Release Notes>.
+value that matches a path is used.
+
+If this argument is omitted, the output displays the current setting
+instead. AFS uses a standardized set of strings; consult the I<OpenAFS Quick
+Beginnings> or I<OpenAFS Release Notes>.
 
 =item B<-help>
 
@@ -61,6 +65,10 @@ system type in the following format:
 
    Current sysname is '<system_type>'
 
+When the B<-newsys> argument is included, the output is the following:
+
+   fs: new sysname list set.
+
 =head1 EXAMPLES
 
 The following example shows the output produced on a Sun SPARCStation
@@ -74,6 +82,18 @@ The following command defines a machine to be a IBM RS/6000 running AIX
 
    % fs sysname -newsys rs_aix42
 
+The following command defines a machine to be Mac OS X PPC and a
+custom type 'foo'. The second command queries the new sysname:
+
+   % fs sysname -newsys ppc_darwin_80 -newsys foo
+   fs: new sysname list set.
+   % fs sysname
+   Current sysname list is 'ppc_darwin_80' 'foo'
+
+If I<@sys> is C<ppc_darwin_80 foo>, then C<cd @sys> will try to change
+to the C<ppc_darwin_80> directory. If the C<ppc_darwin_80> directory
+doesn't exist, then the C<foo> directory is tried.
+
 =head1 PRIVILEGE REQUIRED
 
 To display the current setting, no privilege is required. To include the
@@ -85,9 +105,14 @@ as the local superuser C<root>.
 L<fs_exportafs(1)>,
 L<sys(1)>
 
-I<IBM AFS Quick Beginnings>
+I<OpenAFS Quick Beginnings>
+L<http://www.openafs.org/pages/doc/QuickStartUnix/auqbg000.htm>
 
-I<IBM AFS Administration Guide>
+I<OpenAFS Administration Guide>
+L<http://www.openafs.org/pages/doc/AdminGuide/auagd000.htm>
+
+For the list of assigned standard sysname values, see
+L<http://grand.central.org/numbers/systypes.html>
 
 =head1 COPYRIGHT
 

doc/man-pages/pod1/fs_uuid.pod

@@ -0,0 +1,81 @@
+=head1 NAME
+
+fs_uuid - Prints the uuid of the client or generates a new one
+
+=head1 SYNOPSIS
+
+=for html
+<div class="synopsis">
+
+B<fs uuid> [B<-generate>] [B<-help>]
+
+=for html
+</div>
+
+=head1 DESCRIPTION
+
+B<fs uuid> prints the current UUID of an OpenAFS client.  It can
+optionally force the generation of a new UUID, if needed.  The client UUID
+is used by the B<fileserver> to differentiate clients with the same IP
+address.
+
+=head1 CAUTIONS
+
+The B<fs uuid> command is only available in OpenAFS versions after 1.4.5
+and 1.5.8.  The behavior differs slightly between versions.  In OpenAFS
+1.4.5 and later, the B<-generate> option is required and the UUID for the
+client machine is never printed.  OpenAFS versions 1.5.8 and later will
+print the UUID.
+
+=head1 OPTIONS
+
+=over 4
+
+=item B<-generate>
+
+Generates a new UUID for the cache manager.  This is useful if two clients
+share the same UUID (if systems were cloned incorrectly, for example).
+B<-generate> is optional in OpenAFS versions 1.5.8 and later, but it is
+required in OpenAFS versions 1.4.5 and later.
+
+=item B<-help>
+
+Prints the online help for this command.  All other valid options are
+ignored.
+
+=back
+
+=head1 OUTPUT
+
+B<fs uuid> prints out the current UUID for the client or the new UUID
+if the B<-generate> option is passed to it.
+
+=head1 EXAMPLES
+
+There are only two ways to invoke B<fs uuid> under 1.5.8 and later:
+
+   % fs uuid
+   UUID: 8ac66f9308a8e-47d7-80f7-50d0040cddc2
+
+   % fs uuid -generate
+   New UUID: 436bd660-1720-429508e470cff38f5c6fb0
+
+Here is the only way to invoke B<fs uuid> under OpenAFS 1.4.5 and later:
+
+   % fs uuid -generate
+   New uuid generated.
+
+=head1 PRIVILEGE REQUIRED
+
+The issuer must be logged on as the local superuser C<root>.
+
+=head1 SEE ALSO
+
+L<fs(1)>
+
+=head1 COPYRIGHT
+
+Copyright 2007 Jason Edgecombe <jason@rampaginggeek.com>
+
+This documentation is covered by the IBM Public License Version 1.0. This
+man page was written by Jason Edgecombe for OpenAFS.

doc/man-pages/pod1/fs_whereis.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs whereis - Reports each file server housing a file or directory
+fs_whereis - Reports each file server housing a file or directory
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_whichcell.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs whichcell - Returns the cell to which a file or directory belongs
+fs_whichcell - Returns the cell to which a file or directory belongs
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/fs_wscell.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-fs wscell - Returns the name of the cell to which a machine belongs
+fs_wscell - Returns the name of the cell to which a machine belongs
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_adduser.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts adduser - Adds a user or machine to a Protection Database group
+pts_adduser - Adds a user or machine to a Protection Database group
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_apropos.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts apropos - Displays each help entry containing a keyword string
+pts_apropos - Displays each help entry containing a keyword string
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_chown.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts chown - Changes the owner of a Protection Database entry
+pts_chown - Changes the owner of a Protection Database entry
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_creategroup.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts creategroup - Creates an (empty) Protection Database group entry
+pts_creategroup - Creates an (empty) Protection Database group entry
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_createuser.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts createuser - Creates a user or machine entry in the Protection Database
+pts_createuser - Creates a user or machine entry in the Protection Database
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_delete.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts delete - Deletes a Protection Database entry
+pts_delete - Deletes a Protection Database entry
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_examine.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts examine - Displays a Protection Database entry
+pts_examine - Displays a Protection Database entry
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_help.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts help - Displays help for pts commands
+pts_help - Displays help for pts commands
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_interactive.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts interactive - issue multiple multiple pts commands
+pts_interactive - issue multiple multiple pts commands
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_listentries.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts listentries - Displays all users or groups in the Protection Database
+pts_listentries - Displays all users or groups in the Protection Database
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_listmax.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts listmax - Displays the max user id and max group id counters
+pts_listmax - Displays the max user id and max group id counters
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_listowned.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts listowned - Show the Protection Database groups owned by a user or group
+pts_listowned - Show the Protection Database groups owned by a user or group
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_membership.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts membership - Displays the membership list for a user or group
+pts_membership - Displays the membership list for a user or group
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_quit.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts quit - Exit from pts interactive mode
+pts_quit - Exit from pts interactive mode
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_removeuser.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts removeuser - Removes a user from a Protection Database group
+pts_removeuser - Removes a user from a Protection Database group
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_rename.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts rename - Changes the name of a Protection Database entry
+pts_rename - Changes the name of a Protection Database entry
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_setfields.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts setfields - Sets privacy flags or quota for a Protection Database entry
+pts_setfields - Sets privacy flags or quota for a Protection Database entry
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_setmax.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts setmax - Sets the value of the max group id or max user id counter
+pts_setmax - Sets the value of the max group id or max user id counter
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_sleep.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts sleep - pause for time
+pts_sleep - pause for time
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/pts_source.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-pts source - read pts commands from a file.
+pts_source - read pts commands from a file.
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/symlink.pod

@@ -0,0 +1,40 @@
+=head1 NAME
+
+symlink - Introduction to the symlink command suite
+
+=head1 DESCRIPTION
+
+The B<symlink> command creates, lists and removes Unix-style symbolic links
+(symlinks) in OpenAFS filespace from a platform that does not support
+symlinks, like Windows.  The B<symlink make> command is equivalent to
+C<ln -s> on a Unix platform.  B<symlink> can manipulate symlinks created
+by C<ln -s> on Unix and vice versa.
+
+=head1 CAUTIONS
+
+The B<symlink> commands are only available on Windows platforms.  On
+other platforms, use the C<ln -s> command.
+
+=head1 OPTIONS
+
+=over 4
+
+=item B<-help>
+
+Prints the online help for this command.  All other valid options are
+ignored.
+
+=back
+
+=head1 SEE ALSO
+
+L<symlink_list(1)>,
+L<symlink_make(1)>,
+L<symlink_remove(1)>
+
+=head1 COPYRIGHT
+
+Copyright 2007 Jason Edgecombe <jason@rampaginggeek.com>
+
+This documentation is covered by the IBM Public License Version 1.0. This
+man page was written by Jason Edgecombe for OpenAFS.

doc/man-pages/pod1/symlink_list.pod

@@ -0,0 +1,79 @@
+=head1 NAME
+
+symlink_list - Show the file to which a symlink points
+
+=head1 SYNOPSIS
+
+=for html
+<div class="synopsis">
+
+B<symlink list> S<<< [B<-name>] <I<file name>> >>> [B<-help>]
+
+=for html
+</div>
+
+=head1 DESCRIPTION
+
+The B<symlink list> command shows if a file is a symbolic link and, if so,
+shows to which file the link points.
+
+=head1 CAUTIONS
+
+The B<symlink> commands are only available on Windows platforms.  On other
+platforms, use the B<readlink> command.
+
+=head1 OPTIONS
+
+=over 4
+
+=item [B<-name>] <I<file name>>
+
+Specify one or more symbolic links to list.  The C<-name> is optional, but
+the file name is not.
+
+=item B<-help>
+
+Prints the online help for this command.  All other valid options are
+ignored.
+
+=back
+
+=head1 OUTPUT
+
+This command prints "'file' is a symlink to 'otherfile'" or "'file' is
+not a symlink."
+
+=head1 EXAMPLES
+
+Given that file C<mylink> is a link pointing to file C<myfile>, the
+following commands will list the files:
+
+   % symlink list -name mylink
+   'mylink' is a symlink to 'myfile'
+
+   % symlink list mylink
+   'mylink' is a symlink to 'myfile'
+
+   % symlink list -name myfile
+   'myfile' is not a symlink.
+
+   % symlink list myfile
+   'myfile' is not a symlink.
+
+=head1 PRIVILEGE REQUIRED
+
+The issuer must have the C<l> (look) and C<r> (read) permissions on the ACL
+of the directory that houses the symlink.
+
+=head1 SEE ALSO
+
+L<symlink(1)>,
+L<symlink_make(1)>,
+L<symlink_remove(1)>
+
+=head1 COPYRIGHT
+
+Copyright 2007 Jason Edgecombe <jason@rampaginggeek.com>
+
+This documentation is covered by the IBM Public License Version 1.0. This
+man page was written by Jason Edgecombe for OpenAFS.

doc/man-pages/pod1/symlink_make.pod

@@ -0,0 +1,76 @@
+=head1 NAME
+
+symlink_make - Create a symbolic link
+
+=head1 SYNOPSIS
+
+=for html
+<div class="synopsis">
+
+B<symlink make> S<<< [B<-name>] <I<file name>> >>>
+   S<<< [B<-to>] <I<file name>> >>> [B<-help>]
+
+=for html
+</div>
+
+=head1 DESCRIPTION
+
+The B<symlink make> command creates a new symbolic link to a file.  The file
+to which the link points does not have to exist when the link is created.
+
+=head1 CAUTIONS
+
+The B<symlink> commands are only available on Windows platforms.  On other
+platforms, use the C<ln -s> command.
+
+=head1 OPTIONS
+
+=over 4
+
+=item [B<-name>] <I<file name>>
+
+Specify the name of the new link.  B<-name> is optional, but the file name
+is not.
+
+=item [B<-to>] <I<file name>>
+
+Specify the file to which the new link points.  B<-to> is optional, but the
+file name is not.
+
+=item B<-help>
+
+Prints the online help for this command.  All other valid options are
+ignored.
+
+=back
+
+=head1 OUTPUT
+
+Prints the online help for this command.  All other valid options are
+ignored.
+
+=head1 EXAMPLES
+
+In order to create a link named C<mylink> pointing to the file C<myfile>,
+use one of the following commands:
+
+   % symlink make -name mylink -to myfile
+   % symlink make mylink myfile
+
+=head1 PRIVILEGE REQUIRED
+
+The issuer must have the C<l> (look) and C<i> (insert) permissions on the
+ACL of the directory that houses the symlink.
+
+=head1 SEE ALSO
+
+L<symlink(1)>,
+L<symlink_list(1)>,
+L<symlink_remove(1)>
+
+=head1 COPYRIGHT
+
+Copyright 2007 Jason Edgecombe <jason@rampaginggeek.com>
+
+This documentation is covered by the IBM Public License Version 1.0. This
+man page was written by Jason Edgecombe for OpenAFS.

doc/man-pages/pod1/symlink_remove.pod

@@ -0,0 +1,70 @@
+=head1 NAME
+
+symlink_remove - Remove a symbolic link.
+
+=head1 SYNOPSIS
+
+=for html
+<div class="synopsis">
+
+B<symlink remove> S<<< [B<-name>] <I<file name>> >>> [B<-help>]
+
+=for html
+</div>
+
+=head1 DESCRIPTION
+
+The B<symlink remove> command removes a symbolic link to a file.
+
+=head1 CAUTIONS
+
+The B<symlink> commands are only available on Windows platforms. On other
+platforms, use the B<rm> command.
+
+=head1 OPTIONS
+
+=over 4
+
+=item [B<-name>] <I<file name>>
+
+Specify one or more symbolic links to remove.  The B<-name> is optional, but
+the file name is not.
+
+=item B<-help>
+
+Prints the online help for this command.  All other valid options are
+ignored.
+
+=back
+
+=head1 OUTPUT
+
+This command has no output except error and help messages.  If the command
+is passed a real file instead of a symlink, it prints "symlink: 'file name'
+is not a symlink" instead of removing the file.
+
+=head1 EXAMPLES
+
+Given that file C<mylink> is a link pointing to file C<myfile>, the
+following commands will remove the link C<mylink>:
+
+   % symlink remove -name mylink
+   % symlink remove mylink
+
+=head1 PRIVILEGE REQUIRED
+
+The issuer must have the C<l> (look) and C<d> (delete) permissions on
+the ACL of the directory that houses the symlink.
+
+=head1 SEE ALSO
+
+L<symlink(1)>,
+L<symlink_list(1)>,
+L<symlink_make(1)>
+
+=head1 COPYRIGHT
+
+Copyright 2007 Jason Edgecombe <jason@rampaginggeek.com>
+
+This documentation is covered by the IBM Public License Version 1.0. This
+man page was written by Jason Edgecombe for OpenAFS.

doc/man-pages/pod1/vos.pod

@@ -237,7 +237,8 @@ L<vos_apropos(1)>,
 L<vos_backup(1)>,
 L<vos_backupsys(1)>,
 L<vos_changeaddr(1)>,
-L<vos_changeloc(1)>,
+L<vos_convertROtoRW(1)>,
+L<vos_copy(1)>,
 L<vos_create(1)>,
 L<vos_delentry(1)>,
 L<vos_dump(1)>,

doc/man-pages/pod1/vos_addsite.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos addsite - Adds a read-only site definition to a volume's VLDB entry
+vos_addsite - Adds a read-only site definition to a volume's VLDB entry
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_apropos.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos apropos - Displays each help entry containing a keyword string
+vos_apropos - Displays each help entry containing a keyword string
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_backup.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos backup - Creates a backup volume for a single read/write volume
+vos_backup - Creates a backup volume for a single read/write volume
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_backupsys.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos backupsys - Creates a backup volume for several read/write volumes
+vos_backupsys - Creates a backup volume for several read/write volumes
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_changeaddr.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos changeaddr - Changes or removes a file server machine's entry in the VLDB
+vos_changeaddr - Changes or removes a file server machine's entry in the VLDB
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_changeloc.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos changeloc - Change a volume's entry in the VLDB
+vos_changeloc - Change a volume's entry in the VLDB
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_convertROtoRW.pod

@@ -0,0 +1,122 @@
+=head1 NAME
+
+vos_convertROtoRW - Converts a Read-Only volume into a Read/Write volume
+
+=head1 SYNOPSIS
+
+=for html
+<div class="synopsis">
+
+B<vos convertROtoRW> S<<< [B<-server>] <I<machine name>> >>>
+   S<<< [B<-partition>] <I<partition name>> >>>
+   S<<< [B<-id>] <I<volume name or ID>> >>> [B<-force>]
+   S<<< [B<-cell> <I<cell name>>] >>> [B<-noauth>] [B<-localauth>]
+   [B<-verbose>] [B<-encrypt>] [B<-help>]
+
+=for html
+</div>
+
+=head1 DESCRIPTION
+
+B<vos convertROtoRW> converts a Read-Only volume into a Read/Write volume
+when the original Read/Write volume is no longer available.  It's normal use
+is to recover the Read/Write volume from a replica after a failed disk,
+failed server, or accidental deletion.
+
+=head1 CAUTIONS
+
+This command can only be used with namei AFS file servers.  If used on an
+inode AFS file server, it will fail with an error.
+
+The command name is case-sensitive.  It must be issued with the capital "RO"
+and "RW".
+
+=head1 OPTIONS
+
+=over 4
+
+=item B<-server> <I<server name>>
+
+Identifies the file server machine that houses the Read-Only volume which
+will be converted.  Provide the machine's IP address or its host name
+(either fully qualified or using an unambiguous abbreviation).  For details,
+see L<vos(1)>.
+
+=item B<-partition> <I<partition name>>
+
+Identifies the partition on the file server machine that houses the
+Read-Only volume which will be converted.  Provide the full partition name
+(for, example, B</vicepa>) or one of the abbreviated forms described in
+L<vos(1)>.
+
+=item B<-id> <I<volume ID>>
+
+Specifies either the complete name or volume ID number of a Read/Write
+volume.
+
+=item B<-force>
+
+Don't ask for confirmation.
+
+=item B<-cell> <I<cell name>>
+
+Names the cell in which to run the command. Do not combine this argument
+with the B<-localauth> flag. For more details, see L<vos(1)>.
+
+=item B<-noauth>
+
+Assigns the unprivileged identity C<anonymous> to the issuer. Do not
+combine this flag with the B<-localauth> flag. For more details, see
+L<vos(1)>.
+
+=item B<-localauth>
+
+Constructs a server ticket using a key from the local
+F</usr/afs/etc/KeyFile> file. The B<vos> command interpreter presents it
+to the Volume Server and Volume Location Server during mutual
+authentication. Do not combine this flag with the B<-cell> argument or
+B<-noauth> flag. For more details, see L<vos(1)>.
+
+=item B<-verbose>
+
+Produces on the standard output stream a detailed trace of the command's
+execution. If this argument is omitted, only warnings and error messages
+appear.
+
+=item B<-encrypt>
+
+Encrypts the command so that the operation's results are not transmitted
+across the network in clear text.
+
+=item B<-help>
+
+Prints the online help for this command. All other valid options are
+ignored.
+
+=back
+
+=head1 EXAMPLES
+
+The following example converts the read-only volume test3.readonly in
+partition vicepb on server1 to a read-write volume:
+
+   % vos convertROtoRW server1 b test3.readonly
+
+=head1 PRIVILEGE REQUIRED
+
+The issuer must be listed in the F</usr/afs/etc/UserList> file on the
+machines specified with the B<-toserver> and B<-fromserver> arguments and
+on each database server machine.  If the B<-localauth> flag is included,
+the issuer must instead be logged on to a server machine as the local
+superuser C<root>.
+
+=head1 SEE ALSO
+
+L<vos(1)>
+
+=head1 COPYRIGHT
+
+Copyright 2007 Jason Edgecombe <jason@rampaginggeek.com>
+
+This documentation is covered by the IBM Public License Version 1.0. This
+man page was written by Jason Edgecombe for OpenAFS.

doc/man-pages/pod1/vos_copy.pod

@@ -0,0 +1,158 @@
+=head1 NAME
+
+vos_copy - Make a copy of a volume
+
+=head1 SYNOPSIS
+
+=for html
+<div class="synopsis">
+
+B<vos copy> S<<< [B<-id>] <I<volume name or ID of source>> >>>
+   S<<< [B<-fromserver>] <I<machine name for source>> >>>
+   S<<< [B<-frompartition>] <I<partition name for source>> >>>
+   S<<< [B<-toname>] <I<volume name for new copy>> >>>
+   S<<< [B<-toserver>] <I<machine name for destination>> >>>
+   S<<< [B<-topartition>] <I<partition name for destination>> >>>
+   [B<-offline>] [B<-readonly>] [B<-live>] S<<< [B<-cell> <I<cell name>>] >>>
+   [B<-noauth>] [B<-localauth>] [B<-verbose>] [B<-encrypt>] [B<-help>]
+
+=for html
+</div>
+
+=head1 DESCRIPTION
+
+The B<vos copy> command makes a copy of a volume with a new name.  It is
+equivalent to B<vos dump> followed by B<vos restore>, but doesn't require
+the volume be stored locally by the client.
+
+=head1 OPTIONS
+
+=over 4
+
+=item [B<-id>] <I<volume name or ID>>
+
+Specifies either the complete name or volume ID number of a read/write
+volume.
+
+=item [B<-fromserver>] <I<machine name for source>>
+
+Identifies the file server machine where the source volume resides. Provide
+the machine's IP address or its host name (either fully qualified or using
+an unambiguous abbreviation). For details, see L<vos(1)>.
+
+=item [B<-frompartition>] <I<partition name for source>>
+
+Names the partition where the source volume resides. Provide the full
+partition name (for, example, B</vicepa>) or one of the abbreviated forms
+described in L<vos(1)>.
+
+=item [B<-toname>] <I<volume name for new copy>>
+
+The complete name of the new volume to create.
+
+=item [B<-toserver>] <I<machine name for destination>>
+
+Identifies the file server machine to which to copy the volume.  Provide
+the machine's IP address or its host name (either fully qualified or using
+an unambiguous abbreviation). For details, see L<vos(1)>.
+
+=item [B<-topartition>] <I<partition name for destination>>
+
+Names the partition to which to copy the volume. Provide the full partition
+name (for, example, B</vicepa>) or one of the abbreviated forms described in
+L<vos(1)>.
+
+=item B<-offline>
+
+Leaves the new volume flagged as off-line in the volume database.
+
+=item B<-readonly>
+
+Flags the new volume as read-only in the volume database.
+
+=item B<-live>
+
+Copies the live volume without cloning.  This is normally not necessary and
+causes the volume to be kept locked for longer than the normal copy
+mechanism.
+
+=item B<-localauth>
+
+Constructs a server ticket using a key from the local
+F</usr/afs/etc/KeyFile> file. The B<vos> command interpreter presents it to
+the Volume Server and Volume Location Server during mutual
+authentication. Do not combine this flag with the B<-cell> argument or
+B<-noauth> flag. For more details, see L<vos(1)>.
+
+=item B<-verbose>
+
+Produces on the standard output stream a detailed trace of the command's
+execution. If this argument is omitted, only warnings and error messages
+appear.
+
+=item B<-encrypt>
+
+Encrypts the command so that the operation's results are not transmitted
+across the network in clear text.
+
+=item B<-help>
+
+Prints the online help for this command. All other valid options are
+ignored.
+
+=back
+
+=head1 OUTPUT
+
+This command has no output unless C<-verbose> is specified or there is
+an error.
+
+=head1 EXAMPLES
+
+The following example makes a verbose copy of the C<test> volume named
+C<test2> in the cell C<localcell>. The volume and copy both reside on
+C</vicepa> of C<server1>.
+
+   % vos copy test server1  a test2 server1 a -cell localcell -verbose
+   Starting transaction on source volume 536870921 ... done
+   Allocating new volume id for clone of volume 536870921 ... done
+   Allocating new volume id for copy of volume 536870921 ... done
+   Cloning source volume 536870921 ... done
+   Ending the transaction on the source volume 536870921 ... done
+   Starting transaction on the cloned volume 536870926 ... done
+   Setting flags on cloned volume 536870926 ... done
+   Getting status of cloned volume 536870926 ... done
+   Creating the destination volume 536870927 ... done
+   Setting volume flags on destination volume 536870927 ... done
+   Dumping from clone 536870926 on source to volume 536870927 on destination ... done
+   Ending transaction on cloned volume 536870926 ... done
+   Starting transaction on source volume 536870921 ... done
+   Doing the incremental dump from source to destination for volume 536870921 ...  done
+   Setting volume flags on destination volume 536870927 ... done
+   Ending transaction on destination volume 536870927 ... done
+   Ending transaction on source volume 536870921 ... done
+   Starting transaction on the cloned volume 536870926 ... done
+   Deleting the cloned volume 536870926 ... done
+   Ending transaction on cloned volume 536870926 ... done
+   Created the VLDB entry for the volume test2 536870927
+   Volume 536870921 copied from server1 /vicepa to test2 on server1 /vicepa 
+
+=head1 PRIVILEGE REQUIRED
+
+The issuer must be listed in the F</usr/afs/etc/UserList> file on the
+machine specified with the B<-server> argument and on each database server
+machine. If the B<-localauth> flag is included, the issuer must instead be
+logged on to a server machine as the local superuser C<root>.
+
+=head1 SEE ALSO
+
+L<vos(1)>,
+L<vos_clone(1)>,
+L<vos_move(1)>
+
+=head1 COPYRIGHT
+
+Copyright 2007 Jason Edgecombe <jason@rampaginggeek.com>
+
+This documentation is covered by the IBM Public License Version 1.0. This
+man page was written by Jason Edgecombe for OpenAFS.

doc/man-pages/pod1/vos_create.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos create - Creates a read/write volume and associated VLDB entry
+vos_create - Creates a read/write volume and associated VLDB entry
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_delentry.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos delentry - Removes a volume entry from the VLDB.
+vos_delentry - Removes a volume entry from the VLDB.
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_dump.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos dump - Converts a volume into ASCII format and writes it to a file
+vos_dump - Converts a volume into ASCII format and writes it to a file
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_examine.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos examine - Shows volume header and VLDB entry information for a volume
+vos_examine - Shows volume header and VLDB entry information for a volume
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_help.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos help - Displays help for vos commands
+vos_help - Displays help for vos commands
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_listaddrs.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos listaddrs - Displays all VLDB server entries
+vos_listaddrs - Displays all VLDB server entries
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_listpart.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos listpart - Displays all AFS partitions on a file server machine
+vos_listpart - Displays all AFS partitions on a file server machine
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_listvldb.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos listvldb - Displays a volume's VLDB entry
+vos_listvldb - Displays a volume's VLDB entry
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_listvol.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos listvol - Displays information from a volume header
+vos_listvol - Displays information from a volume header
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_lock.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos lock - Locks a VLDB volume entry
+vos_lock - Locks a VLDB volume entry
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_move.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos move - Moves a read/write volume to another site
+vos_move - Moves a read/write volume to another site
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_offline.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos offline - Takes a volume offline
+vos_offline - Takes a volume offline
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_online.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos online - Brings a volume online
+vos_online - Brings a volume online
 
 =head1 SYNOPSIS
 

doc/man-pages/pod1/vos_partinfo.pod

@@ -1,6 +1,6 @@
 =head1 NAME
 
-vos partinfo - Reports the available and total space on a partition
+vos_partinfo - Reports the available and total space on a partition
 
 =head1 SYNOPSIS