From 0f24d677afadae00d15109358316b6c42df8719a Mon Sep 17 00:00:00 2001 From: "Sebastian J. Bronner" Date: Tue, 7 Mar 2017 10:07:49 +0100 Subject: [PATCH] Fix command for linking modules in mods-enabled. Running `ln -s mods-available/foo mods-enabled/foo` will result in a dead link: `mods-enabled/foo` will point to `mods-enabled/mods-available/foo`, which doesn't exist. The link is relative from its location, not from the current directory from which it was created. The easiest method that allows using tab completion is to link from within `mods-enabled`. The second parameter to `ln` can be left off in that case, as well. This is the change I have proposed. Another alternative would be to run `ln -s ../mods-available/foo mods-enabled/foo` from the `raddb` directory. --- raddb/README.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/raddb/README.rst b/raddb/README.rst index c77a95b4b6a..858a6d4573c 100644 --- a/raddb/README.rst +++ b/raddb/README.rst @@ -76,8 +76,8 @@ ordering when the modules are loaded. Modules can be enabled by creating a soft link. For module ``foo``, do:: - $ cd raddb - $ ln -s mods-available/foo mods-enabled/foo + $ cd raddb/mods-enabled + $ ln -s ../mods-available/foo To create "local" versions of the modules, we suggest copying the file instead. This leaves the original file (with documentation) in the -- 2.47.3