Do not limit supported file names of scripts to run-parts defaults

A file named foobar.sh won't be covered by "run-parts $DIRECTORY", which is stupid and unexpected behaviour.
grml · Sep 27, 2012 · 7ce3406 · 7ce3406
1 parent 12e47ae
commit 7ce3406
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 4 deletions.
diff --git a/autoconfig.functions b/autoconfig.functions
@@ -1703,7 +1703,7 @@ if checkbootparam 'scripts' || [ "$DCSMP" = "/mnt/grmlcfg" ]; then
        sh -c $SCRIPTS
      elif [ -d "$SCRIPTS" ]; then
        einfo "Bootparameter scripts found. Trying to execute from directory ${SCRIPTS}:"
-       run-parts $SCRIPTS
+       run-parts --regex '.*' $SCRIPTS
      else
        einfo "Bootparameter scripts found. Trying to execute ${SCRIPTS}:"
        sh -c $SCRIPTS

diff --git a/doc/grml-autoconfig.current.txt b/doc/grml-autoconfig.current.txt
@@ -101,9 +101,7 @@ scripts::
     relative to DCSDIR. If the path points to a file, this single file is
     executed. If no path is given, it defaults to scripts/grml.sh.
     If the given name points to a directory, all scripts inside it are
-    executed, but the run-parts name restrictions apply: script names must
-    consist entirely of upper and lower case letters, digits, underscores,
-    and hyphens. Usage examples:
+    executed. Usage examples:
 
   scripts               =>   run script DCSDIR/scripts/grml.sh
   scripts=foobar.sh     =>   run script foobar.sh in DCSDIR