diff --git a/docs/expert/software-installation.md b/docs/expert/software-installation.md
index 098a7645b6197bfcfd2bf6022276bf8fcae7777a..a484d92cd228162e4a2244e0c83d990ab3c0b64b 100644
--- a/docs/expert/software-installation.md
+++ b/docs/expert/software-installation.md
@@ -9,73 +9,26 @@ detailed instructions are provided in the DAQ expert guide
### Obtain the repo
-The GEM online software group maintains a yum repository for the
-officially released software packages. To use these on your setup follow
-the appropriate steps below.
-
-=== "centos7"
-
- ``` sh
- curl -L https://cern.ch/cmsgemdaq/sw/gemos/repos/releases/legacy/gemos_release_centos7_x86_64.repo -o /etc/yum.repos.d/gemos.repo
- ```
-
-=== "arm"
-
- This file should be placed on the CTP7 (eventually)
-
- ``` sh
- curl -L https://cern.ch/cmsgemdaq/sw/gemos/repos/releases/legacy/gemos_release_peta_armv7l.repo -o /etc/yum.repos.d/gemos.repo
- ```
+The GEM online software group maintains a yum repository for the officially released software packages.
+To use these on your setup follow the appropriate steps below.
### Determine which packages you require and then install
For most teststands, the following command should be sufficient
``` sh
-yum install xhal reedmuller wiscrpcsvc gempython\* --enablerepo=cernonly
+yum install cmsgemos --enablerepo=cernonly
```
!!! note
CERN packages and provides some packages that are not available in
- \"standard\" repositories, e.g., `cx_Oracle`. In order to have `yum`
+ "standard" repositories, e.g., `cx_Oracle`. In order to have `yum`
find these packages, you should either ensure that the appropriate
`cernonly` repository file is always enabled, or you should use the
`--enablerepo=cernonly` flag, as shown in the example.
-### Install pacakges on the CTP7
-
-The CTP7 requires that some setup be performed in order to be useful.
-Assuming that the CTP7 is already
-`set up to communicate with the teststand<gemos-ctp7-setup-new>`{.interpreted-text
-role="ref"}, this simply requires putting the correct version of the
-libraries in the expected locations.
-
-``` sh
-smart install xhal reedmuller ctp7_modules
-```
-
## Environment setup
-### Environment setup script
-
-From the machine you\'ll be setting up you have several options for
-setting the environment.
-
-- This method is aggressively invasive, it applies to all users on all
- logins:
-
- > ``` bash
- > sudo curl -L https://cern.ch/cmsgemdaq/sw/gemos/repos/releases/legacy/gemdaqenv.sh -o /etc/profile.d/gemdaqenv.sh
- > ```
-
-- This method is better, it applies only to the specific users who
- enable it
-
- ``` bash
- curl -L https://cern.ch/cmsgemdaq/sw/gemos/repos/releases/legacy/gemdaqenv.sh -o ~/gemdaqenv.sh
- # add source ~/gemdaqenv.sh to your appropriate profile file
- ```
-
### Site specific variables
A number of shell variables should be defined for the software to work
@@ -83,28 +36,13 @@ completely. Many of these are set with the environment setup script
mentioned in the previous section, but several must be set for the
specific setup.
- -------------------------------------------------------------------------------------
- Variable name Description
- ---------------------------------------- --------------------------------------------
- `ELOG_PATH`{.interpreted-text Location the software will place certain
- role="envvar"} plots
-
- `DATA_PATH`{.interpreted-text Location the software will place output
- role="envvar"} files and will look for intermediate results
-
- `GBT_SETTINGS`{.interpreted-text Location the software will look for GBTx
- role="envvar"} configuration settings
-
- `GEM_ONLINE_DB_NAME`{.interpreted-text DB SID name from the `tnsnames.ora` file
- role="envvar"}
-
- `GEM_ONLINE_DB_CONN`{.interpreted-text Connection SID and credential, in the
- role="envvar"} following format the
- `<DB user>/<DB password>` contact the GEM
- DAQ expert team for the password, but the
- usual user is `CMS_GEM_APPUSER_R`, the
- standard GEM DB reader account
- -------------------------------------------------------------------------------------
+| Variable name | Description |
+|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `ELOG_PATH` | Location the software will place certain plots |
+| `DATA_PATH` | Location the software will place output files and will look for intermediate results |
+| `GBT_SETTINGS` | Location the software will look for GBTx configuration settings |
+| `GEM_ONLINE_DB_NAME` | DB SID name from the `tnsnames.ora` file |
+| `GEM_ONLINE_DB_CONN` | Connection SID and credential, in the following format the `<DB user>/<DB password>` contact the GEM DAQ expert team for the password, but the usual user is `CMS_GEM_APPUSER_R`, the standard GEM DB reader account |
``` bash
export ELOG_PATH=/your/favorite/elog/path