Bug 118060 – kernel-upgrade.xml improvements

• Product: [OLD] Docs-user
• Status: RESOLVED FIXED

[Description nm (RETIRED) 2006-01-06 09:09:01 UTC]

Based on what I've been seeing (and commenting on) in bug 117023, I thought I'd add a paragraph to the kernel upgrade guide. It's really a very handy quick description of the common use of module-rebuild. I only plan to cover "module-rebuild populate" and "module-rebuild rebuild"--bare usage tips. Anything else gets referred to "module-update --help". Patch should go up shortly.

[Comment 1 nm (RETIRED) 2006-01-06 09:20:22 UTC]

Created attachment 76358 [details, diff]
kernel-upgrade.xml.patch

A brief paragraph addition that should be very helpful.

[Comment 2 Xavier Neys (RETIRED) 2006-01-06 09:50:02 UTC]

*** Bug 117023 has been marked as a duplicate of this bug. ***

[Comment 3 Xavier Neys (RETIRED) 2006-01-06 09:50:44 UTC]

> Once you have finished upgrading or recompiling your kernel, run
> <c>module-rebuild rebuild</c> to rebuild the drivers for your new kernel.

Shouldn't we recommend it's done before rebooting?
Does module-rebuild rebuild for the running kernel or for whatever /usr/src/linux points to? The latter, I suppose.

[Comment 4 nm (RETIRED) 2006-01-06 10:06:08 UTC]

Created attachment 76362 [details, diff]
kernel-upgrade.xml.patch

Added reboot info and which modules are rebuilt. Surprisingly, it's actually for only the currently running kernel. For users that boot into whatever /usr/src/linux points to, this is not a problem, as this is obviously the kernel that will have its modules rebuilt if it is recompiled/upgraded. :)

[Comment 5 Xavier Neys (RETIRED) 2006-01-08 07:16:22 UTC]

In CVS.
Thanks.