Commit 8c3f1a2d authored by unknown's avatar unknown

DOC: some updates including new link to tarball

parent 8f4d2682
...@@ -9,7 +9,7 @@ ...@@ -9,7 +9,7 @@
\noindent \rule{\textwidth}{.1cm} \noindent \rule{\textwidth}{.1cm}
\hfill January 15, 2015 \hfill July 13, 2018
\vspace*{3cm} \vspace*{3cm}
...@@ -24,7 +24,7 @@ ...@@ -24,7 +24,7 @@
%--------------------------------------------------------------- %---------------------------------------------------------------
% name % name
%--------------------------------------------------------------- %---------------------------------------------------------------
\noindent {\Large \textbf{Theodor-Adrian Stana (CERN/BE-CO-HT)}} \noindent {\Large \textbf{CERN/BE-CO-HT}}
\noindent \rule{\textwidth}{.05cm} \noindent \rule{\textwidth}{.05cm}
......
...@@ -119,7 +119,7 @@ focuses on installing the test system (scripts, preparing shortcuts, etc.) on th ...@@ -119,7 +119,7 @@ focuses on installing the test system (scripts, preparing shortcuts, etc.) on th
\label{sec:rack} \label{sec:rack}
To setup the rack for the PTS system, we will need to insert an RTM Interface Tester To setup the rack for the PTS system, we will need to insert an RTM Interface Tester
card to the back side of the ELMA crate placed inside the 19'' rack. You will need card into the back of the ELMA crate placed inside the 19'' rack. You will need
an RTM Interface Tester card to set up the system, so this would be a good time to an RTM Interface Tester card to set up the system, so this would be a good time to
obtain one. obtain one.
...@@ -151,6 +151,9 @@ system to gain remote access to the laptop, the installation of the system can a ...@@ -151,6 +151,9 @@ system to gain remote access to the laptop, the installation of the system can a
on the laptop directly. However, the steps related to network drivers and configuration on the laptop directly. However, the steps related to network drivers and configuration
should be followed in order to have a properly working PTS system. should be followed in order to have a properly working PTS system.
Also note that the admin account should be named \verb=pts-administrator=. This account
name is important as it is embedded in the PTS scripts (Password \verb=pts-admin=).
The guide should be followed until \textbf{step 17} of section \textbf{Set up the PTS user account}. The guide should be followed until \textbf{step 17} of section \textbf{Set up the PTS user account}.
After this step, the guide is SVEC-related and need not be followed. We will continue with After this step, the guide is SVEC-related and need not be followed. We will continue with
the details in the next section to test our system and network was properly installed. the details in the next section to test our system and network was properly installed.
...@@ -171,7 +174,8 @@ the details in the next section to test our system and network was properly inst ...@@ -171,7 +174,8 @@ the details in the next section to test our system and network was properly inst
Escape character is '^]'. Escape character is '^]'.
login:admin login:admin
password: ADMIN password: ADMIN
%> %>
$
\end{verbatim} \end{verbatim}
\vspace{11pt} \vspace{11pt}
\item Make sure the ELMA crate has gateware version 2.31 or higher on it. In the SysMon Telnet prompt: \item Make sure the ELMA crate has gateware version 2.31 or higher on it. In the SysMon Telnet prompt:
...@@ -220,12 +224,12 @@ We will detail here the simplest of the two, downloading the ready-made archive. ...@@ -220,12 +224,12 @@ We will detail here the simplest of the two, downloading the ready-made archive.
See Appendix~\ref{app:build} for details on the second. See Appendix~\ref{app:build} for details on the second.
\begin{enumerate} \begin{enumerate}
\item Log in to the \verb=pts= user on the laptop \item Log in to the \verb=pts-administrator= user on the laptop
\item Open up a terminal window, download the PTS folder structure tarball from OHWR \item Open up a terminal window, download the PTS folder structure tarball from OHWR
to the home folder of the \verb=pts= user and extract the archive: to the home folder of the \verb=pts= user and extract the archive:
\begin{verbatim} \begin{verbatim}
cd ~ cd ~
wget http://www.ohwr.org/attachments/download/3777/ubuntu.tar.gz wget https://www.ohwr.org/attachments/5822/ubuntu.tar.gz
tar xzvf ubuntu.tar.gz tar xzvf ubuntu.tar.gz
\end{verbatim} \end{verbatim}
Note that you can also copy the archive from a USB stick instead of downloading it from OHWR. Note that you can also copy the archive from a USB stick instead of downloading it from OHWR.
...@@ -259,7 +263,7 @@ See Appendix~\ref{app:build} for details on the second. ...@@ -259,7 +263,7 @@ See Appendix~\ref{app:build} for details on the second.
\begin{verbatim} \begin{verbatim}
chmod a+w * chmod a+w *
\end{verbatim} \end{verbatim}
\item Now we that have the test scripts on the system we can create a dedicated \item Now that we have the test scripts on the system we can create a dedicated
user that will be used to run the PTS for the CONV-TTL-BLO. Open up Ubuntu's user that will be used to run the PTS for the CONV-TTL-BLO. Open up Ubuntu's
\textbf{User Accounts} window (click the \verb=pts= user account name at the top-right \textbf{User Accounts} window (click the \verb=pts= user account name at the top-right
side of the screen), unlock this window by providing the \verb=pts= user account's side of the screen), unlock this window by providing the \verb=pts= user account's
...@@ -286,9 +290,9 @@ See Appendix~\ref{app:build} for details on the second. ...@@ -286,9 +290,9 @@ See Appendix~\ref{app:build} for details on the second.
\begin{verbatim} \begin{verbatim}
cd ~ cd ~
cp .bashrc .bashrc.old cp .bashrc .bashrc.old
cp /home/pts/ubuntu/ttlbl/config/bashrc.pts .bashrc cp /home/pts-administrator/ubuntu/ttlbl/config/bashrc.pts .bashrc
cd ~/Desktop/ cd ~/Desktop/
cp /home/pts/ubuntu/ttlbl/config/*.desktop . cp /home/pts-administrator/ubuntu/ttlbl/config/*.desktop .
\end{verbatim} \end{verbatim}
\item Right-click on the terminal icon in the launcher bar at the left and click \textbf{Lock to Launcher} \item Right-click on the terminal icon in the launcher bar at the left and click \textbf{Lock to Launcher}
\item Close the terminal window \item Close the terminal window
...@@ -298,7 +302,7 @@ See Appendix~\ref{app:build} for details on the second. ...@@ -298,7 +302,7 @@ See Appendix~\ref{app:build} for details on the second.
\begin{itemize} \begin{itemize}
\item on the Desktop, right-click and select \textbf{Change Desktop Background} \item on the Desktop, right-click and select \textbf{Change Desktop Background}
\item hit the \textbf{+} under Wallpapers \item hit the \textbf{+} under Wallpapers
\item navigate to \verb=/home/pts/ubuntu/ttlbl/config/= \item navigate to \verb=/home/pts-administrator/ubuntu/ttlbl/config/=
\item select \verb=ttlbl-background.png= as the background image \item select \verb=ttlbl-background.png= as the background image
\item make sure the scaling of the image is set to \textbf{Zoom} \item make sure the scaling of the image is set to \textbf{Zoom}
\end{itemize} \end{itemize}
...@@ -355,12 +359,16 @@ In order to build a test system from scratch, follow these steps: ...@@ -355,12 +359,16 @@ In order to build a test system from scratch, follow these steps:
git clone git://ohwr.org/level-conversion/conv-ttl-blo/conv-ttl-blo-tst.git git clone git://ohwr.org/level-conversion/conv-ttl-blo/conv-ttl-blo-tst.git
\end{verbatim} \end{verbatim}
\end{small} \end{small}
\item Run \verb=make= in the \verb=pts-fm/= folder, setting the options as appropriate \item Run \verb=make= in the \verb=fm/pts/= folder, setting the options as appropriate
in your case: in your case:
\begin{verbatim} \begin{verbatim}
cd conv-ttl-blo-tst/fm/ cd conv-ttl-blo-tst/fm/pts
make # ... set options here ... make # ... set options here ...
\end{verbatim} \end{verbatim}
\item Copy the entire \verb=./ubuntu= folder to the \verb=pts-administrator= home directory. Type:
\begin{verbatim}
cp -r ./ubuntu /home/pts-administrator/
\end{verbatim}
\end{enumerate} \end{enumerate}
This will generate an archive similar to that downloaded in Section~\ref{sec:environment}, This will generate an archive similar to that downloaded in Section~\ref{sec:environment},
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment