Univention Bugzilla – Bug 30177
Blacklist kernel modules using UCR
Last modified: 2014-06-12 09:19:37 CEST
Especially when dealing with wireless network drivers there are numerous concurrent drivers with different features and licenses available. It is therefor sometimes unavoidable to disable certain drivers to enforce the usage of a specific driver. This can most often be achieved by blacklisting the respective kernel module. Blacklisting should therefore be configurable using UCR to efficiently set the blacklists across multiple devices without forcing the Administrator to provide different images to deal with these issues.
This is supported in UCS 3.2 with kernel/blacklist. Since the UCR templates in UCC 1.1 will be updated to the versions in 3.2, this will be fixed along.
(In reply to Moritz Muehlenhoff from comment #1) > This is supported in UCS 3.2 with kernel/blacklist. > > Since the UCR templates in UCC 1.1 will be updated to the versions in 3.2, > this will be fixed along. univention-base-files was updated in Bug 33760 Setting e.g. kernel/blacklist=btrfs prevents the autoload of the btrfs kernel module (which is loaded by default for some reason)
For the QA: - Run lsmod, btrfs should be loaded. - Set the UCR variable kernel/blacklist=btrfs in a UCR policy - After a reboot of the client the btrfs module should not be loaded.
(In reply to Moritz Muehlenhoff from comment #3) > For the QA: > > - Run lsmod, btrfs should be loaded. > - Set the UCR variable kernel/blacklist=btrfs in a UCR policy > - After a reboot of the client the btrfs module should not be loaded. Working. Changelog entry exists
UCC 2.0 has been released: http://docs.univention.de/release-notes-ucc-2.0.html If this error occurs again, please use "Clone This Bug".