Arch Linux

I use MOD_BLACKLIST in the rc.conf so i hope it has a function and i hope it will survive. And for just the stats: The modules what i have 'blacklisted' don't get loaded so this function seems to work well.
Answer for your 'what is it for' part with a simple example: As the most pc's my pc has a parallel port but from my clients i print over the network because the printer is connected with the server. So i put 'lp parport parport_p' in the MOD_BLACKLIST array and none of them get loaded from udev. There is a wiki about the rc.conf too: http://wiki.archlinux.org/index.php/Rc.conf. I like this possibility.

isn't MOD_BLACKLIST=(module) the same as MODULES=(!module) ?

yes it is the same

This is an example that i want it to be deprecated... It doesn't have to be confusing to the user if the transition is explained fully...

This is an example that i want it to be deprecated... It doesn't have to be confusing to the user if the transition is explained fully...

Only my 2 cents: It is nice for the devs that this is the same code as '!module' but sorry, why do we want to eliminate a working solution? Is there really no one who can understand that not everybody knows what the '!' char means and for them (or people which have used a BLACKLIST functionality in their former distro) MOD_BLACKLISt is self-explanatory in contrast to have only a mixed MODULE array.

Atilla, it is only a problem if ! is not explained in the comment above the MODULE array like it isnt now. Familiarity is a good thing but it shouldn't go ahead of simplicity.

See around the forum and you'll see that there are also people being confused and misunderstand _because_ two competing solutions exist now -- I don't that is worth your familiarity when a simple explanation is really only the thing needed -- in the form of a comment.

Okay, i overseen the problem with the second line of the comment for the MODULES array ("- prefix a module with a ! to blacklist it") and from my view this "confusing" line is unneeded which is the simplest way including the fewest work. But i give it up and see what the future brings.

I have marked this as deprecated.
http://code.phraktured.net/?p=initscripts.git;a=commitdiff;h=ab5595c4f8cdea8e6b1813701828576cbfee2fc2

The next initscripts release will contain this. I may add an install message too. At some point we will remove it. Give people a little time to adjust.

Is this clear enough for everyone?

good enough for me.

Do i understand it right that you remove the line but i don't have to change my rc.conf because it will still works?

yup. not until it gets removed finally in an unforeseeable future... however if you want to be sure it will work in the future simply put all the modules you had in MOD_BLACKLIST into MODULES and put a ! infront of them :)

Thanks but here my next stupid question -): Can i split the line with a '\' at the end at example in this way?
MODULES=(!module1 \
module999)

It's bash syntax. Bash will allow that *but* bash arrays are special. You don't even need the \ in there

FOO=(a
b
c
d)

Is a perfectly valid bash array.

I don't mind answering questions here and all, but this IS a bug tracker, not a forum, so can we take these questions elsewhere?

Thanks for your answer and i will stop asking here.

i think we can close this, or not?

agree