Bug 34844 - Document blacklisting of kernel modules
Document blacklisting of kernel modules
Status: CLOSED FIXED
Product: Z_Univention Corporate Client (UCC)
Classification: Unclassified
Component: Documentation
unspecified
Other Linux
: P5 enhancement
: UCC 2.0
Assigned To: Moritz Muehlenhoff
Erik Damrose
: interim-4
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-05-15 15:58 CEST by Moritz Muehlenhoff
Modified: 2014-06-12 09:20 CEST (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Muehlenhoff univentionstaff 2014-05-15 15:58:09 CEST
+++ This bug was initially created as a clone of Bug #30177 +++

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.
Comment 1 Moritz Muehlenhoff univentionstaff 2014-05-15 16:43:36 CEST
Documented in revision 50320 (along with UCR kernel/modules)
Comment 2 Erik Damrose univentionstaff 2014-05-23 10:08:38 CEST
Verified
Comment 3 Moritz Muehlenhoff univentionstaff 2014-06-12 09:20:02 CEST
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".