update-systypes-in-README-20010210

[openafs.git] / src / README

diff --git a/src/README b/src/README
index dfe3a0c..769d72e 100644 (file)
--- a/src/README
+++ b/src/README
@@ -10,19 +10,23 @@ Building OpenAFS on UNIX and LINUX
 
 A. Creating the proper directory structure.
 
-   Uncompress the source into a directory of your choice.
-   Preferrably, afs space. In the directory that you uncompressed the
-   source in, you will only have an src directory.
-       
+   Uncompress the source into a directory of your choice. A directory
+   in afs space is also valid. In the directory that you uncompressed the
+   source in, you will only have an src/ directory.
+
    1. Make a directory for each system type that you plan on
       building. Current tested system types include the following
      (this step is skipped for the i386_nt40 system type):
 
       alpha_dux40/
+      alpha_dux50/ (only tested on 5.0A)
       i386_linux22/
+      i386_linux24/ (only tested with 2.4.0 kernel)
       rs_aix42/
+      sgi_65/ (file server not tested)
       sun4x_56/
       sun4x_57/
+      sun4x_58/
 
       Example:
       % mkdir i386_linux22
@@ -41,31 +45,35 @@ A. Creating the proper directory structure.
       % mkdir i386_linux22/obj
 
    3. Create symbolic links to the system type you are about to build
+      a. If the source is in AFS space
 
-      Example:
-      % ln -s @sys/dest dest
-      % ln -s @sys/obj  obj
-      % ls -CF
-      Makefile@     dest@     i386_linux22/     obj@     src/
+         Example:
+         % ln -s @sys/dest dest
+         % ln -s @sys/obj  obj
+         % ls -CF
+         dest@     i386_linux22/     obj@     src/
 
-   4. If this source is NOT in AFS space, You must make a link from
-      @sys to your current system type. 
+         Within AFS space, the AFS Cache Manager automatically
+         substitutes the local machine's AFS system name (CPU/operating
+         system type [ie: alpha_dux40, i386_linux22, ...]) for the @sys
+         variable.
 
-      Example:
-      % ln -s i386_linux22 @sys
-
-      Within AFS space, the AFS Cache Manager automatically
-      substitutes the local machine's AFS system name (CPU/operating
-      system type [ie: alpha_dux40, i386_linux22, ...]) for the @sys
-      variable.
+      b. If this source is NOT in AFS space, You must make a link from
+         @sys to your current system type. 
 
+         Example:
+         % ln -s i386_linux22 @sys
+         % ln -s @sys/dest dest
+         % ln -s @sys/obj  obj
+         % ls -CF
+         dest@     i386_linux22/     obj@     src/     sys@
+ 
    5. Create the top level Makefile:
-      a. For LINUX and UNIX versions
 
          Example:
          % ln -s src/Makefile Makefile
          % ls -CF
-         Makefile@     i386_linux22/     src/
+         Makefile@     dest@     i386_linux22/     obj@     src/
 
 B  Building
 
@@ -77,7 +85,7 @@ B  Building
 
    2. Begin building
       a. For Linux
-         % make SYS_NAME="i386_linux22" LINUX_VERSION="2.2.14"
+         % make SYS_NAME="i386_linux22" LINUX_VERS="2.2.14"
 
       b. For UNIX versions, specify the system name as given by
          the system type defined in step A1.
@@ -88,6 +96,9 @@ B  Building
 
 C  Problems
    If you have a problem building this source, you may want to visit
-   http://oss.software.ibm.com/developerworks/opensource/afs/ to see
-   if any problems have been reported or to find out how to get more
-   help.
+   http://www.openafs.org/ to see if any problems have been reported 
+   or to find out how to get more help.
+
+   Mailing lists have been set up to help; More details can be found
+   on the openafs.org site.
+