--- doc/build/centos8_install.frag	2019/10/03 15:12:52	1.1
+++ doc/build/centos8_install.frag	2020/11/02 21:16:44	1.4
@@ -34,17 +34,17 @@ The installation process takes the follo
 </ol>
 
 <hr />
-<h2>1. <a name="obt">Obtain CentOS Linux 8</a></h2>
+<h2>1. <a id="obt">Obtain CentOS Linux 8</a></h2>
 <p>
 CentOS 8 isos can be obtained from links included on the 
 <a href="http://mirror.centos.org/centos/8/isos/x86_64">CentOS download page</a>.
 Either download the Boot ISO or the CentOS 8 DVD1 ISO. 
 </p>
 
-<h2>2. <a name="net">Determine Network Settings</a></h2>
+<h2>2. <a id="net">Determine Network Settings</a></h2>
 <p>
 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.
+<b>Note: </b>You must have a static IP address to use LON-CAPA.
 DHCP is <em>not</em> supported.
 
 <ul>
@@ -55,7 +55,7 @@ DHCP is <em>not</em> supported.
   <li>domain name server(s) </li>
 </ul>
 
-<h2>3. <a name="lin">Minimal CentOS Linux 8 Install</a></h2>
+<h2>3. <a id="lin">Minimal CentOS Linux 8 Install</a></h2>
 <p>
 Documentation is available from
 <a href="https://docs.centos.org/en-US/8-docs/">
@@ -95,12 +95,12 @@ web server ports (i.e., http and https):
 <pre>
 systemctl enable firewalld
 systemctl start firewalld
-sudo firewall-cmd --zone=public --permanent --add-service=http
-sudo firewall-cmd --zone=public --permanent --add-service=https
-sudo firewall-cmd --reload
+firewall-cmd --zone=public --permanent --add-service=http
+firewall-cmd --zone=public --permanent --add-service=https
+firewall-cmd --reload
 </pre>
 
-<h2>4. <a name="upd">Update your system</a></h2>
+<h2>4. <a id="upd">Update your system</a></h2>
 <p>
 Update your system to the latest versions of the system software using dnf.
 </p>
@@ -116,7 +116,7 @@ If the kernel was updated, reboot your s
 Enable access to the EPEL repository
 </p>
 <pre>
-dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
+dnf install epel-release
 </pre>
 <p>
 Enable the CentOS-PowerTools repository
@@ -134,6 +134,31 @@ mv centos8_PowerTools_yum.conf /etc/yum.
 </pre>
 </li>
 </ol>
+<p>
+Install the loncapa.repo file from the LON-CAPA install site:
+</p>
+<pre>
+wget -O /etc/yum.repos.d/loncapa.repo http://install.loncapa.org/versions/centos/8/loncapa.repo
+</pre>
+<p>
+Verify the required repositories are enabled:
+</p>
+<pre>
+dnf repolist enabled
+</pre>
+<p>
+The list of enabled repos should be as follows:
+</p>
+<table style="border: 0px; border-collapse: collapse;">
+<tr><th>repo id</th><th>repo name</th></tr>
+<tr><td>AppStream</td><td>CentOS-8 - AppStream</td></tr>
+<tr><td>BaseOS</td><td>CentOS-8 - Base</td></tr>
+<tr><td>PowerTools</td><td>CentOS-8 - PowerTools</td></tr>
+<tr><td>*epel</td><td>Extra Packages for Enterprise Linux 8 - x86_64</td></tr>
+<tr><td>extras</td><td>CentOS-8 - Extras</td></tr>
+<tr><td>loncapa-updates-basearch</td><td>CentOS 8 LON-CAPA x86_64 Updates</td></tr>
+<tr><td>loncapa-updates-noarch</td><td>CentOS 8 LON-CAPA noarch Updates</td></tr>
+</table>
 
 <h3>Install and enable a Mail Transfer Agent (MTA), e.g., postfix</h3>
 <pre>
@@ -159,7 +184,7 @@ mv loncapa_selinux_config /etc/selinux/c
 reboot
 </pre>
 
-<h2>5. <a name="ilc">Installing LON-CAPA</a></h2>
+<h2>5. <a id="ilc">Installing LON-CAPA</a></h2>
 <h3>Install prerequisites</h3>
 <p> Execute: </p>
 <pre>
@@ -181,8 +206,8 @@ Extract the archive with the following c
 tar xf install.tar
 </pre>
 <p>
-This creates a directory named <tt>installation</tt>.  Change to it and
-execute the setup script with the following commands:
+This creates a directory named <span style="font-family: 'Lucida Console','Menlo','Monaco','Courier', monospace;">installation</span>. 
+Change to it and execute the setup script with the following commands:
 </p>
 <pre>
 cd installation
@@ -224,8 +249,8 @@ for it to function at all.  Below is a l
   <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
-      special characters.</i><br>Domain names which include a departmental
+      meaningful.  <i>Restriction: One word, no underscores, and no special
+      characters except . or  -</i> .<br />Domain names which include a departmental
       abbreviation are not recommended as although LON-CAPA may start in
       a single department, other departments frequently join subsequently.
       For a domain name: 'msu' is a superior choice to 'msuphys' for example.
@@ -233,17 +258,20 @@ for it to function at all.  Below is a l
   <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,
-      no hyphens, underscores, or special characters.</i>
+      no underscores, and no special characters except -</i> .
   </dd>
   <dt>Domain's Primary Library Server ID</dt>
    <dd>If you are setting up a domain with a single library server, then the domain's primary library server ID will be the LON-CAPA host id of that server (e.g., msul1). Once your domain grows and you need to add more servers, one of the library servers in the domain should be assigned as the domain's primary library server.  This will be where domain-wide settings will be stored.<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
-      serious trouble. On a laptop, make this <tt>root@localhost</tt>.
+      serious trouble. If you are installing a LON-CAPA instance on a laptop,
+      because you are planning to contribute to LON-CAPA development,
+      make this <span style="font-family: 'Lucida Console','Menlo','Monaco','Courier', monospace;">
+      root@localhost</span>.
   </dd>
   <dt>Support email address</dt>
-  <dd>If you enter an e-mail address here, then users of the system
+  <dd>Enter an e-mail address here, so users of the system
       will be able to click an "Ask Helpdesk" link in the system to
       display a web form which they will complete to request support from
       your institution's helpdesk. On form submission the contents
@@ -264,7 +292,7 @@ You will need to enter the LON-CAPA conf
 in the previous section.
 </p>
 
-<h2>6. <a name="cdc">Creating a Domain Coordinator</a></h2>
+<h2>6. <a id="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
@@ -280,33 +308,39 @@ cd /root/loncapa-X.Y.Z/loncom/build
 perl make_domain_coordinator.pl USERNAME DOMAIN
 </pre>
 
-<h2>7. <a name="sts">Start/Restart Services</a></h2>
+<h2>7. <a id="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.
 </p>
 <pre>
 /etc/init.d/loncontrol start
-service httpd start
+systemctl start httpd
 </pre>
 <p>
 If you receive warnings about missing perl modules, when starting the httpd service
 please make sure that the LONCAPA-prerequisites rpm is installed using this command:
+</p>
 <pre>
 rpm -q LONCAPA-prerequisites rpm
 </pre>
-If it is not installed, check that the LON-CAPA Linux repository is a listed repo:
-<pre>
-more /etc/yum.repos.d/loncapa.repo
-</pre>
-and if so, do:
+<p>
+If it is not installed, ensure that the required Linux repositories are enabled (see
+the "Set up access to package repositories" section above), then install it:
+</p>
 <pre>
 dnf install LONCAPA-prerequisites
 </pre>
+<p>
 If you still have errors, please contact the LON-CAPA Helpdesk: helpdesk at loncapa.org
 </p>
+<p>Ensure that LON-CAPA network services and the httpd service are set to start on boot:
+<pre>
+systemctl enable loncontrol
+systemctl enable httpd
+</pre>
 
-<h2>8. <a name="log">Log in to your LON-CAPA Machine</a></h2>
+<h2>8. <a id="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!