From 459555f07c1948f50ceeae13fec7d9c201fb15d2 Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Fri, 13 May 2011 15:57:59 +0200 Subject: [PATCH] title change, a sunny day, isn't it? Signed-off-by: Nico Schottelius --- ...ftware-with-environment-modules-in-the-systems-group.mdwn} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename blog/{modular-use-of-environment-modules-in-the-systems-group.mdwn => managing-custom-software-with-environment-modules-in-the-systems-group.mdwn} (95%) diff --git a/blog/modular-use-of-environment-modules-in-the-systems-group.mdwn b/blog/managing-custom-software-with-environment-modules-in-the-systems-group.mdwn similarity index 95% rename from blog/modular-use-of-environment-modules-in-the-systems-group.mdwn rename to blog/managing-custom-software-with-environment-modules-in-the-systems-group.mdwn index 097a0da5..0d20f512 100644 --- a/blog/modular-use-of-environment-modules-in-the-systems-group.mdwn +++ b/blog/managing-custom-software-with-environment-modules-in-the-systems-group.mdwn @@ -1,4 +1,4 @@ -[[!meta title="Modular use of environment modules in the Systems Group"]] +[[!meta title="Managing custom software with environment modules in the Systems Group"]] ## The problem @@ -79,7 +79,7 @@ modulefiles directory: ### Using env modules To actually make use of the new modules, you need to add env modules into your -shell. The following commands illustrates the way for the **bash**: +shell. The following commands illustrate the way for the **bash**: % . /pub/env-modules/Modules/3.2.8/init/bash % module avail