On Fri, Feb 22, 2008 at 1:45 AM, Xavier <shiningxc@gmail.com> wrote:
Aaron Griffin wrote:
On Thu, Feb 21, 2008 at 4:08 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
Idea #1: $ cat /etc/udev/rules.d/00-load-blacklist.rules ENV{MOD_AUTOLOAD} == "", IMPORT{program} = "/lib/udev/mod-blacklist.sh"
This should only execute it when the env var isn't set. Would someone mind testing, I won't be home to watch a boot process for a bit
What is idea #2? ;) I tried this, and it didn't seem to work. Don't ask me why, I don't have the slightest idea how to debug this stuff.
Idea #2: $ mv /etc/udev/rules.d/00-load-blacklist.rules /etc/udev/rules.d/00-load-blacklist.rules.disabled in /etc/rc.sysinit, add ". /lib/udev/mod-blacklist.sh" and "export BLACKLSIT MOD_AUTOLOAD" right before the udevd --daemon call comment out the echo lines in the mod-blacklist script if you care Hopefully the environment vars that udev sees are also seen by scripts that it executes...