Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#25396 - [archboot] Modules from /etc/rc.conf got blacklisted
Attached to Project:
Arch Linux
Opened by dauerbaustelle (dauerbaustelle) - Thursday, 04 August 2011, 09:55 GMT
Last edited by Ionut Biru (wonder) - Thursday, 04 August 2011, 10:11 GMT
Opened by dauerbaustelle (dauerbaustelle) - Thursday, 04 August 2011, 09:55 GMT
Last edited by Ionut Biru (wonder) - Thursday, 04 August 2011, 10:11 GMT
|
Details/etc/modprobe.d/blacklist_{net,sound}.conf were automatically created (I did NOT create them; in fact, I didn't even know how to blacklist modules) with MODULES I blacklisted using the deprecated !bang syntax for debugging purposes. However, after removing the '!' the modules were still blacklisted because of the modprobe files that were generated.
I think that's very confusing. You should either 1) have full backwards compatibility for the !blacklisted syntax by removing those entries from the modprobe files if the exclamation mark was removed 2) or have no backwards compatibility at all, ignoring the exclamation marks/complaining. |
This task depends upon
Closed by Ionut Biru (wonder)
Thursday, 04 August 2011, 10:11 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#25308
Thursday, 04 August 2011, 10:11 GMT
Reason for closing: Duplicate
Additional comments about closing: