prevent ubuntu-modules & restricted-modules from breaking when custom kernels are used
If if the stock kernel image provided with *buntu is replaced with a custom compiled one, it essentially breaks ubuntu-modules and restricted-modules.
eg. Due to Bug #271595 I need to recompile the kernel image with certain features turned off.
Though I am using the kernel source used to compile the stock kernel, and the vanilla ubuntu & restricted modules, I am blocked off from further updates.
Recompiling them does not need much more than a few hacks in the rules/control files. However, this may not be known to the average user. Infact while there is documentation on custom restricted-modules, there is none of ubuntu-modules. I propose a simple metapackage that will compile and install a stock kernel, ubuntu modules & restrcited modules. This will not involve much except a few lines of sed/awk that make the appropriate abi number changes to the control & rules file to enable the user to compile ubuntu-modules and restricted-modules along with the kernel.
Possible restriction might be to force user to use the ubuntu provided kernel source, as using source too far upstream/downstream might itself cause *-modules to fail to compile. Not aimed at the novice user, though I think it will make for a very useful functionality for the intermediate user.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Anish Bhatt
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by