From badbb8173ccd14fc8e52ed63346036c6d5e9fe87 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bob=20Dr=C3=B6ge?= <b.e.droge@rug.nl>
Date: Fri, 20 Feb 2026 14:13:55 +0100
Subject: [PATCH 1/6] add cvmfs_config reload step, add tip about
 EESSI-specific config files

---
 docs/site_specific_config/gpu.md | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/docs/site_specific_config/gpu.md b/docs/site_specific_config/gpu.md
index 9923e4a173..f63ffaeef6 100644
--- a/docs/site_specific_config/gpu.md
+++ b/docs/site_specific_config/gpu.md
@@ -49,7 +49,12 @@ sudo bash -c "echo 'EESSI_NVIDIA_OVERRIDE_DEFAULT=/opt/eessi/nvidia' >> /etc/cvm
 sudo bash -c "echo 'EESSI_HOST_INJECTIONS=/desired/path/to/host/injections' >> /etc/cvmfs/default.local"
 ```
 
-Third, you run the helper script
+*Step 3:* To actually reconfigure the variant symlinks, reload the updated CernVM-FS configuration using:
+```{ .bash copy }
+sudo cvmfs_config reload software.eessi.io
+```
+
+*Step 4:* Run the helper script:
 
 ```{ .bash .copy }
 /cvmfs/software.eessi.io/versions/${EESSI_VERSION}/scripts/gpu_support/nvidia/link_nvidia_host_libraries.sh
@@ -67,6 +72,11 @@ Third, you run the helper script
     sudo bash -c "echo 'EESSI_202506_NVIDIA_OVERRIDE=/opt/eessi/2025.06/nvidia' >> /etc/cvmfs/default.local"
     ```
 
+!!! tip "Use a EESSI-specific CernVM-FS configuration file to configure the variant symlinks"
+    Instead of using `/etc/cvmfs/default.local` you can also put the symlink configuration in a local configuration file that is specific to the `software.eessi.io` repository
+    or to the `eessi.io` domain.
+    For the first you can use `/etc/cvmfs/config.d/software.eessi.io.local`, while for the latter you can use `/etc/cvmfs/domain.d/eessi.io.local`.
+
 !!! note "How does EESSI find the linked drivers?"
 
     The runtime linker provided by the EESSI [compatibility layer](../compatibility_layer.md) is configured to search an

From 6976d305c6025733bde921b14a5c6c400c339d4f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bob=20Dr=C3=B6ge?= <b.e.droge@rug.nl>
Date: Fri, 20 Feb 2026 20:07:26 +0100
Subject: [PATCH 2/6] add link to CVMFS tutorial

---
 docs/site_specific_config/gpu.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/site_specific_config/gpu.md b/docs/site_specific_config/gpu.md
index f63ffaeef6..c56d3e87b4 100644
--- a/docs/site_specific_config/gpu.md
+++ b/docs/site_specific_config/gpu.md
@@ -76,6 +76,8 @@ sudo cvmfs_config reload software.eessi.io
     Instead of using `/etc/cvmfs/default.local` you can also put the symlink configuration in a local configuration file that is specific to the `software.eessi.io` repository
     or to the `eessi.io` domain.
     For the first you can use `/etc/cvmfs/config.d/software.eessi.io.local`, while for the latter you can use `/etc/cvmfs/domain.d/eessi.io.local`.
+    For more details about the different configuration files, 
+    see [the configuration hierarchy page of our CernVM-FS tutorial](https://www.eessi.io/docs/training-events/2025/tutorial-best-practices-cvmfs-hpc/access/client/#configuration_hierarchy).
 
 !!! note "How does EESSI find the linked drivers?"
 

From 4554c09842c070b603b56a93e1e03ca9aa8f57cd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bob=20Dr=C3=B6ge?= <b.e.droge@rug.nl>
Date: Fri, 20 Feb 2026 20:08:15 +0100
Subject: [PATCH 3/6] page -> section

---
 docs/site_specific_config/gpu.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/site_specific_config/gpu.md b/docs/site_specific_config/gpu.md
index c56d3e87b4..1076cec895 100644
--- a/docs/site_specific_config/gpu.md
+++ b/docs/site_specific_config/gpu.md
@@ -77,7 +77,7 @@ sudo cvmfs_config reload software.eessi.io
     or to the `eessi.io` domain.
     For the first you can use `/etc/cvmfs/config.d/software.eessi.io.local`, while for the latter you can use `/etc/cvmfs/domain.d/eessi.io.local`.
     For more details about the different configuration files, 
-    see [the configuration hierarchy page of our CernVM-FS tutorial](https://www.eessi.io/docs/training-events/2025/tutorial-best-practices-cvmfs-hpc/access/client/#configuration_hierarchy).
+    see [the configuration hierarchy section of our CernVM-FS tutorial](https://www.eessi.io/docs/training-events/2025/tutorial-best-practices-cvmfs-hpc/access/client/#configuration_hierarchy).
 
 !!! note "How does EESSI find the linked drivers?"
 

From befb5e16d949a1623f8706d3f1ee0706fee6240a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bob=20Dr=C3=B6ge?= <b.e.droge@rug.nl>
Date: Fri, 20 Feb 2026 20:08:40 +0100
Subject: [PATCH 4/6] remove trailing colon

---
 docs/site_specific_config/gpu.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/site_specific_config/gpu.md b/docs/site_specific_config/gpu.md
index 1076cec895..e35f0de68d 100644
--- a/docs/site_specific_config/gpu.md
+++ b/docs/site_specific_config/gpu.md
@@ -95,7 +95,7 @@ Then, change to the correct directory:
 - For EESSI 2023.06: `/cvmfs/software.eessi.io/host_injections/${EESSI_VERSION}/compat/${EESSI_OS_TYPE}/${EESSI_CPU_FAMILY}/lib`
 Then, manually create the symlinks for each of the files in the aforementioned list (if they exist on your system) to the current directory.
 
-#### Runtime support when using EESSI in a container: {: #nvidia_eessi_container } 
+#### Runtime support when using EESSI in a container {: #nvidia_eessi_container } 
 
 If you are running your own [Apptainer](https://apptainer.org/)/[Singularity](https://sylabs.io/singularity) container,
 it is sufficient to use the [`--nv` option](https://apptainer.org/docs/user/latest/gpu.html#nvidia-gpus-cuda-standard)

From d889e542dfb780ea2ea8979cfe03ce0398be8821 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bob=20Dr=C3=B6ge?= <b.e.droge@rug.nl>
Date: Fri, 20 Feb 2026 20:09:38 +0100
Subject: [PATCH 5/6] fix rendering of bullet list

---
 docs/site_specific_config/gpu.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/site_specific_config/gpu.md b/docs/site_specific_config/gpu.md
index e35f0de68d..8880ac4571 100644
--- a/docs/site_specific_config/gpu.md
+++ b/docs/site_specific_config/gpu.md
@@ -91,8 +91,10 @@ sudo cvmfs_config reload software.eessi.io
 If, for some reason, the helper script is unable to locate the drivers on your system you _can_ link them manually.
 To do so, grab the list of libraries that need to be symlinked from [here](https://raw.githubusercontent.com/apptainer/apptainer/main/etc/nvliblist.conf).
 Then, change to the correct directory:
+
 - For EESSI 2025.06 and later: `/cvmfs/software.eessi.io/versions/${EESSI_VERSION}>/compat/${EESSI_OS_TYPE}/${EESSI_CPU_FAMILY}/lib/nvidia`,
 - For EESSI 2023.06: `/cvmfs/software.eessi.io/host_injections/${EESSI_VERSION}/compat/${EESSI_OS_TYPE}/${EESSI_CPU_FAMILY}/lib`
+
 Then, manually create the symlinks for each of the files in the aforementioned list (if they exist on your system) to the current directory.
 
 #### Runtime support when using EESSI in a container {: #nvidia_eessi_container } 

From e8cd23eb83cf3b20a97c333f1005ffa286ac397a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Bob=20Dr=C3=B6ge?= <b.e.droge@rug.nl>
Date: Fri, 20 Feb 2026 20:11:03 +0100
Subject: [PATCH 6/6] capitalize first letter

---
 docs/site_specific_config/gpu.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/site_specific_config/gpu.md b/docs/site_specific_config/gpu.md
index 8880ac4571..fea3ff23bb 100644
--- a/docs/site_specific_config/gpu.md
+++ b/docs/site_specific_config/gpu.md
@@ -154,7 +154,7 @@ Thus, you may want to periodically run this script to pick up on new CUDA and cu
     $ ls -l /cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/amd/zen3/software/CUDA/12.1.1/bin/nvcc
     lrwxrwxrwx 1 cvmfs cvmfs 109 Dec 21 14:49 /cvmfs/software.eessi.io/versions/2023.06/software/linux/x86_64/amd/zen3/software/CUDA/12.1.1/bin/nvcc -> /cvmfs/software.eessi.io/host_injections/2023.06/software/linux/x86_64/amd/zen3/software/CUDA/12.1.1/bin/nvcc
     ```
-    the `/cvmfs/software.eessi.io/host_injections` directory is special, since it is not part of the actual EESSI repository:
+    The `/cvmfs/software.eessi.io/host_injections` directory is special, since it is not part of the actual EESSI repository:
     it is a CernVM-FS [Variant Symlink](https://cvmfs.readthedocs.io/en/stable/cpt-repo.html#variant-symlinks) that points to
     a directory on the local system (`/opt/eessi` by default).
     The `install_cuda_and_libraries.sh` script installs CUDA and cuDNN in this local directory, thus un-breaking the symlinks.