diff --git a/src/Glossary.tex b/src/Glossary.tex
index 7535944..5a1c287 100644
--- a/src/Glossary.tex
+++ b/src/Glossary.tex
@@ -435,3 +435,4 @@
 % PPS (gps)
 % gpsd
 % List of Software ?
+% NTP
diff --git a/src/Software.tex b/src/Software.tex
index f0c04fe..3b5b972 100644
--- a/src/Software.tex
+++ b/src/Software.tex
@@ -416,9 +416,24 @@ When mount control is functioning, a location on the sky chart, such as a star,
  can be clicked on and the mount will go to that location and optionally track it.
 Using this, a telescope mount can be used to easily point the camera at a location
 and track it to observe telescopes. It should also provide a superior \gls{FITS} file
-for extracting data (XXX made up).
+for extracting data than using a static mount (XXX made up).
 \index{KStars}\index{sky chart}\index{GOTO}\index{mount}\index{track}
 
+To fully set up a telescope tracking mount, the following steps need to be performed in
+roughly this order:
+
+\begin{mdframed}[backgroundcolor=blue!10,linecolor=blue!30]
+\begin{enumerate}
+        \item Physically mount all hardware.
+	\item Plug in and power everything up.
+	\item Confirm all hardware looks ok (e.g. \texttt{lsusb}).
+	\item Confirm GNSS time and location are ok (e.g. \texttt{cgps -u m}).
+	\item Conr
+\end{enumerate}
+\end{mdframed}
+\index{mount}\index{KStars}\index{telescope}\index{track}
+\index{lsusb}\index{cgps}\index{GNSS}
+
 \begin{sidewaysfigure}[p!]
         \begin{center}
                 \includegraphics[keepaspectratio=true,height=1.00\textheight,width=1.00\textwidth,angle=0]{kstars-skychart.png}
@@ -570,3 +585,42 @@ See below for sample output from \texttt{cgps}.
 \end{minted}
 \index{cgps}
 
+\section{NTP}
+\label{sec:software-ntp}
+\index{NTP}
+With all the above, time still needs to be configured.
+Configuring \texttt{gpsd} isn't enough for correct system time.
+The main system on the Internet used for time synchronization is NTP.
+In \gls{Debian} there are a few options for NTP.
+The best is to use a hardware GPS, with PPS for improved
+accuracy. The easiest is to just use NTP.
+\index{PPS}
+
+All systems in the chain need to have the correct time and
+location. It is best if they all pull from the same NTP
+server, or even better than best if they all run \gls{GNSS}
+hardware with PPS enabled.
+
+Some quick and dirty time synchronization commands.
+The \texttt{ntpd} daemon can have slow startup synchronization
+sometimes. If so, perhaps run like this:
+
+\begin{minted}{sh}
+# Get the daemon out of the way.
+sudo systemctl stop ntp
+
+# Get time from someone, MIT in this case:
+sudo ntpdate time.mit.edu
+
+# OR
+
+# Get time from local server, such as router (made up IP):
+sudo ntpdate 192.168.1.1
+
+# Restart daemon
+sudo systemctl start ntp
+\end{minted}
+
+Go through each of the systems used in the toolchain and make
+sure they all have accurate time or everything will be off.
+