--- doc/build/sles10_install.frag	2006/10/09 17:18:14	1.1
+++ doc/build/sles10_install.frag	2010/05/27 05:48:22	1.6
@@ -1,20 +1,20 @@
 <h1>Installing LON-CAPA on a minimal SuSE Linux Enterprise Server (SLES) 10</h1>
 <p>
 This document guides you through the process of setting up a new LON-CAPA
-server running SuSE Linux Enterprise Server 10 (SLES 10) with a minimum of packages installed.  
-The computer will be configured solely as a LON-CAPA server and will be 
+server running SuSE Linux Enterprise Server 10 (SLES 10) with a minimum of packages installed.
+The computer will be configured solely as a LON-CAPA server and will be
 expected to have no other services running.  Your server is expected to have
 a reasonably fast connection to the internet.
 </p><p>
-More information is available at 
+More information is available at
 <a href="http://install.lon-capa.org/">http://install.lon-capa.org/</a>.
 </p>
 
 <h2>Before you begin</h2>
 <p>
-Installing Linux is getting easier and easier.  
+Installing Linux is getting easier and easier.
 You will be required to log in to the machine and execute
-some routine Unix commands.  Familiarity with the Apache web server, mod_perl, 
+some routine Unix commands.  Familiarity with the Apache web server, mod_perl,
 perl, and MySQL are not required to install and run LON-CAPA.
 </p>
 
@@ -23,24 +23,25 @@ perl, and MySQL are not required to inst
 The installation process takes the following steps:
 </p>
 <ol>
-  <li> Obtain SLES 10 installation media</li>
-  <li> Determine Network Settings</li>
-  <li> Install SLES 10</li>
-  <li> Update your system </li>
-  <li> Install LON-CAPA </li>
-  <li> Create a Domain Coordinator </li>
-  <li> Start/Restart services </li>
-  <li> Log in to LON-CAPA </li>
+  <li><a href="#obt">Obtain SLES 10 installation media</a></li>
+  <li><a href="#net">Determine Network Settings</a></li>
+  <li><a href="#lin">Install SLES 10</a></li>
+  <li><a href="#upd">Update your system</a></li>
+  <li><a href="#ilc">Install LON-CAPA</a></li>
+  <li><a href="#cdc">Create a Domain Coordinator</a></li>
+  <li><a href="#sts">Start/Restart services</a></li>
+  <li><a href="#log">Log in to LON-CAPA</a></li>
 </ol>
 
-<h2>Obtain SuSE Linux Enterprise Server 10</h2>
+<hr />
+<h2>1. <a name="obt">Obtain SuSE Linux Enterprise Server 10</a></h2>
 <p>
-SuSE ISO files can be obtained from the Novell site: <a href="http://www.novell.com/products/server/">http://www.novell.com/products/server/</a>.  
-</p> 
+SuSE ISO files can be obtained from the Novell site: <a href="http://www.novell.com/products/server/">http://www.novell.com/products/server/</a>.
+</p>
 
-<h2>Determine Network Settings</h2>
+<h2>2. <a name="net">Determine Network Settings</a></h2>
 <p>
-You will need to know the following network settings for your installation.  
+You will need to know the following network settings for your installation.
 <b>Note:</b>You must have a static IP address to use LON-CAPA.
 DHCP is <em>not</em> supported.
 </p>
@@ -52,35 +53,38 @@ DHCP is <em>not</em> supported.
   <li>domain name server(s) </li>
 </ul>
 
-<h2>Minimal SLES 10 Install</h2>
+<h2>3. <a name="lin">Minimal SLES 10 Install</a></h2>
 <p>
 Installing SuSE Linux Enterprise Server is quite easy if you've installed Linux products
-before.  Some documentation is available from 
+before.  Some documentation is available from
 <a href="http://www.novell.com/documentation/sles10/">
 http://www.novell.com/documentation/sles10/</a>.<br /><br />
 Most of the subsequent installation screens are self explanatory.
 There are a few steps that require comment and are dealt with below.
 </p>
 <dl style="list-style:square outside none">
+   <dt>Installation Language</dt>
+   <dd>Use English as your installation language.</dd>
+
    <dt>Partitioning your Drive</dt>
-   <dd>For a LON-CAPA library server (i.e., the main server used 
-       for permanent storage of course and user data), 
-       a separate partition is recommended for /home, as this    
+   <dd>For a LON-CAPA library server (i.e., the main server used
+       for permanent storage of course and user data),
+       a separate partition is recommended for /home, as this
        simplifies future upgrades of the operating system.
-       If you are adding an additional access server to an 
-       existing LON-CAPA domain, this does not apply as no 
+       If you are adding an additional access server to an
+       existing LON-CAPA domain, this does not apply as no
        permanent data are stored on an access server.
        As LON-CAPA resource files are stored in the /home directory,
-       the majority of the disk space should be allocated here.    
+       the majority of the disk space should be allocated here.
        If you have 20 GB of space for SLES10, /home should
-       receive at least 10 to 12 gigs. Since MySQL uses the /var 
-       filesystem to store its databases you should have as least 
-       4 gigs of space available on /var.  Be sure to 
+       receive at least 10 to 12 gigs. Since MySQL uses the /var
+       filesystem to store its databases you should have as least
+       4 gigs of space available on /var.  Be sure to
        include adequate swap space.  A minimum is 512 Megs, but you should
        typically have 1 or 2x as much swap space as you do physical RAM.
        </dd>
    <dt>Software Selection</dt>
-   <dd> 
+   <dd>
    Installation of the minimum set of packages is recommended.  This will involve unchecking all checkboxes except for the base SuSE installation.</dd>
 </dl>
 <p>Once you system has rebooted, you will use yast to complete the configuration. Change the following settings:
@@ -96,10 +100,11 @@ There are a few steps that require comme
 <p>
 Finish installing your server, read the "readme", reboot and log in as root.
 </p>
-<h2>Configure Firewall Settings</h2>
-<p>After reboot you should start yast, and select Security and Users -> Firewall. At step 2 include the following services: HTTP, HTTP with SSL, and Secure Shell.  Use the "Expert..." option to add additional TCP services on ports 5663 and 8080.    
+<h3>Configure Firewall Settings</h3>
+<p>After reboot you should start yast, and select Security and Users -> Firewall. At step 2 include the following services: HTTP, HTTP with SSL, and Secure Shell.
 </p>
-<h2>Change software sources for your system</h2>
+
+<h2>4. <a name="upd">Change software sources for your system</a></h2>
 <p>
 You will use yast to import packages required for LON-CAPA.<br />
 Execute:
@@ -108,10 +113,17 @@ Execute:
 yast
 </pre>
 <p>
-Select "Change Source of Installation". The media you used to install SLES10 will be listed as an installation source.  You may also wish to create a local repository by copying the contents of the RPM directories on the five CDs to a local directory to avoid the need to flip CDs during LON-CAPA installation.  Information about building a local repository is available at:<a href="http://portal.suse.com/sdb/en/2004/02/yast_instsrc.html">http://portal.suse.com/sdb/en/2004/02/yast_instsrc.html</a>.
-</p>
+Select "Change Source of Installation". The media you used to install SLES10 will be listed as an installation source. If you do not already have a SLES10 installation source at your location, you may want to consider creating one from the 4 iso files for CDs 1 - 4,  to avoid the need to flip CDs during LON-CAPA installation.  Proceed as follows (e.g., for 32 bit):</p>
+<pre>
+mkdir -p sles10/CD1
+mount -o ro,loop SLES-10-x86-CD1.iso /mnt
+cp -rv /mnt/* sles10/CD1
+umount /mnt
+</pre>
+<p>
+Repeat those steps with CD2, CD3 and CD4.</p>
 <h3>Add an additional installation source</h3>
-<p>Add the LON-CAPA SLES 10 repository as an additional installation source, so software installation in yast will have access to two repositories - a SuSE/Novell source (for packages included for the standard distribution) and the LON-CAPA repository (for extra packages needed to run LON-CAPA). For the LON-CAPA source you will use:
+<p>Add the LON-CAPA SLES 10 repository as an additional installation source, so software installation in yast will have access to at least two repositories - a SuSE/Novell source (for packages included for the standard distribution) and the LON-CAPA repository (for extra packages needed to run LON-CAPA). For the LON-CAPA source you will use:
 <dl style="list-style:square outside none">
 <dd>Protocol</dd>
 <dt>HTTP</dt>
@@ -122,8 +134,10 @@ Select "Change Source of Installation".
 <dd>Authentication</dd>
 <dt>Anonymous</dt>
 </dl>
-After saving this configuration information for the LON-CAPA repository, quit yast.  
+After saving this configuration information for the LON-CAPA repository, quit yast.
 </p>
+
+<h2>5. <a name="ilc">Installing LON-CAPA</a></h2>
 <h3>Install prerequisites</h3>
 <p> Execute: </p>
 <pre>
@@ -165,23 +179,23 @@ for it to function at all.  Below is a l
   <dd>The server must be designated a 'library' or an 'access' server.  In
       general you should have a library server for your instructors to create
       their course content on and run their courses.  Students should connect
-      to access servers.  If you are doing the first install of LON-CAPA at 
+      to access servers.  If you are doing the first install of LON-CAPA at
       your site, or if you are playing with it for your own edification you
       should make your machine a 'library' server.</dd>
   <dt>LON-CAPA domain</dt>
   <dd>Each site or school which installs LON-CAPA needs its own domain.
       Here at MSU we use 'msu'.  You should choose something short but
-      meaningful.  <i>Restriction: One word, no hyphens, underscores, or 
+      meaningful.  <i>Restriction: One word, no hyphens, underscores, or
       special characters.</i>
   </dd>
   <dt>LON-CAPA host id</dt>
   <dd>Each LON-CAPA server requires a unique internal name.  We use names
-      such as "msul1" for the first library server. <i>Restriction: One word, 
+      such as "msul1" for the first library server. <i>Restriction: One word,
       no hyphens, underscores, or special characters.</i>
   </dd>
   <dt>Host administrator email</dt>
   <dd>The amount of email sent to this address is relatively minimal.  Messages
-      are sent every time the system starts up, or if the system is in 
+      are sent every time the system starts up, or if the system is in
       serious trouble. On a laptop, make this <tt>root@localhost</tt>.
   </dd>
 </dl>
@@ -195,21 +209,22 @@ cd /root/loncapa-N.N.N     (N.N.N should
 ./UPDATE
 </pre>
 <p>
-You will need to enter the LON-CAPA configuration information you determined 
-in the previous section.  
+You will need to enter the LON-CAPA configuration information you determined
+in the previous section.
 </p>
 <p>After installing LON-CAPA, and taking any actions included in the WARNINGS file created during installation, it is recommended that you set loncontrol to start automatically on boot, by executing the following command:</p>
 <pre>
 /sbin/chkconfig --level 345 loncontrol on
 </pre>
-<h2>Creating a Domain Coordinator</h2>
+
+<h2>6. <a name="cdc">Creating a Domain Coordinator</a></h2>
 <p>
 You will need at least one user at your site who has the role of
 'domain coordinator'.  This user creates accounts for other users and
 grants them additional privileges.  The make_domain_coordinator.pl script
 invoked below requires that you enter the users password.  The password will
 show in plaintext as you type it.  Feel free to use the "passwd username"
-command to change it later.  Replace USERNAME and DOMAIN with an 
+command to change it later.  Replace USERNAME and DOMAIN with an
 appropriate user name and your domain.
 </p>
 <pre>
@@ -217,7 +232,8 @@ cd /root/loncapa-N.N/loncom/build
 perl make_domain_coordinator.pl USERNAME DOMAIN
 (WILL PROMPT FOR PASSWORD HERE)
 </pre>
-<h2>Start/Restart Services</h2>
+
+<h2>7. <a name="sts">Start/Restart Services</a></h2>
 <p>
 The LON-CAPA network services take a moment to start.  Most misconfigurations
 will be apparent at this step.
@@ -228,21 +244,24 @@ will be apparent at this step.
 </pre>
 <p>
 If you receive warnings when starting the httpd about missing perl modules,
-please make sure you followed the instructions in 
+please make sure you followed the instructions in
 <b>Installing LON-CAPA Dependencies</b>.  If you still have errors, please
-contact the LON-CAPA support team.
+contact the LON-CAPA group.
 </p>
-<h2>Log in to your LON-CAPA Machine</h2>
+
+<h2>8. <a name="log">Log in to your LON-CAPA Machine</a></h2>
 <p>
 Point a web browser at your new machine and log in as the domain
 coordinator.  Congratulations!
 </p>
+
+<hr />
 <h2>If things aren't working right</h2>
 <p>
 If you've followed the steps above and the server doesn't start or you think
-there's something wrong, please get in touch with the LON-CAPA support team.
+there's something wrong, please get in touch with the LON-CAPA group.
 You can submit a help request using our web form:<br />
-<a href="http://support.loncapa.org/help/">http://support.loncapa.org/help/</a><br />
+<a href="http://help.loncapa.org/help/">http://help.loncapa.org/help/</a><br />
 If there were errors in installation of the dependency RPMs or during the
 automatic setup, please send us as much information as possible.
 If some part of this document is unclear please let us know.