Am 02.03.2010 11:47, schrieb mb: > Hi Thomas, > On Tuesday 02 March 2010 11:18:27 Thomas Bächler wrote: >> This is not true. You didn't dig deep enough. Blacklisting in rc.conf >> works just fine. > no offence. My mail was never meant to be an accusation or something > similar. I should not have posted it as tautology but added the premise > that this is the case on at least my system. Sorry, for being imprecise. > I was just curious about this issue. My post in the bulletin board is a bit > more verbose maybe you can have a look at it and point out what's wrong > with my system. In the bulletin boards there was another user who observed > the same behaviour. > Fact is that on my system lsmod shows modules that are blacklisted in > rc.conf. To be more precise they appear just after the udev part in the > rc.sysinit. I'm happy to provide any assistance needed to explain (solve?) > this situation. > I keep my /etc/ in a git repository so it's quite impropable that some of my > config files are 'broken' but I won't say it's impossible. I reinstalled > initscripts to get the clean files but this changed nothing as well. I had a short look at the thread and there are two explanations: 1) The modules in question are not loaded by udev, but by something/someone else. 2) Your udev package is not Arch's udev package, or you include extra rules that are not provided by Arch. As you say that MOD_AUTOLOAD=no has no effect, only possibility 2) is left.
Attachment:
signature.asc
Description: OpenPGP digital signature
