From 6bfca5d635c1f9586381c074fab0accfbdd7fb76 Mon Sep 17 00:00:00 2001 From: TopRichard <121792457+TopRichard@users.noreply.github.com> Date: Thu, 17 Oct 2024 13:37:38 +0200 Subject: [PATCH] Update docs/using_eessi/setting_up_environment.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Thomas Röblitz --- docs/using_eessi/setting_up_environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/using_eessi/setting_up_environment.md b/docs/using_eessi/setting_up_environment.md index 3bf9bc76a..ef3a5d053 100644 --- a/docs/using_eessi/setting_up_environment.md +++ b/docs/using_eessi/setting_up_environment.md @@ -9,7 +9,7 @@ There are a few different scenarios where you may want to set up the EESSI envir 1. You are already using Lmod with version >= 8.6 In this case, we recommend unsetting the `MODULEPATH`, because EESSI is not designed to mix modules coming from EESSI and from your system. - since they are effectively two different OSes (though this may not be possible at some sites, and some compromise may be necessary): + The underlying reason is that very likely EESSI and your system are based on two different operating system distributions - EESSI uses Gentoo, your system likely uses some other distribution. Note, unsetting `MODULEPATH` may not be possible at some sites, and some compromise may be necessary: ``` { .bash .copy } unset MODULEPATH