To have it take effect as early as possible.
Signed-off-by: Tormod Volden <debian.tor...@gmail.com>
---
Now that I am looking at it, wouldn't it make sense to build the
blacklist file already in init-top? I don't see why init-premount
was chosen instead, but maybe I am missing something.
This patch is on top of the previous one.
Tormod
scripts/init-premount/blacklist | 25 -------------------------
scripts/init-top/blacklist | 25 +++++++++++++++++++++++++
2 files changed, 25 insertions(+), 25 deletions(-)
delete mode 100755 scripts/init-premount/blacklist
create mode 100755 scripts/init-top/blacklist
diff --git a/scripts/init-premount/blacklist b/scripts/init-premount/blacklist
deleted file mode 100755
index 2164906..0000000
--- a/scripts/init-premount/blacklist
+++ /dev/null
@@ -1,25 +0,0 @@
-#!/bin/sh
-
-PREREQ=""
-
-prereqs()
-{
- echo "$PREREQ"
-}
-
-case $1 in
-# get pre-requisites
-prereqs)
- prereqs
- exit 0
- ;;
-esac
-
-# sanity check
-[ -z "${blacklist}" ] && exit 0
-
-# write blacklist to modprobe.d
-IFS=','
-for b in ${blacklist}; do
- echo "blacklist $b" >> /etc/modprobe.d/initramfs.conf
-done
diff --git a/scripts/init-top/blacklist b/scripts/init-top/blacklist
new file mode 100755
index 0000000..2164906
--- /dev/null
+++ b/scripts/init-top/blacklist
@@ -0,0 +1,25 @@
+#!/bin/sh
+
+PREREQ=""
+
+prereqs()
+{
+ echo "$PREREQ"
+}
+
+case $1 in
+# get pre-requisites
+prereqs)
+ prereqs
+ exit 0
+ ;;
+esac
+
+# sanity check
+[ -z "${blacklist}" ] && exit 0
+
+# write blacklist to modprobe.d
+IFS=','
+for b in ${blacklist}; do
+ echo "blacklist $b" >> /etc/modprobe.d/initramfs.conf
+done
--
1.6.3.3
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
