Should not display warning about modules directory for official kernels
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kernel-package (Ubuntu) |
Fix Released
|
High
|
Matt Zimmerman |
Bug Description
It's about time to teach debconf to stop asking the following obsolete question
every time a new kernel is installed. It is triggered by the presence of
/lib/modules/
able to tell the difference !
>You are attempting to install a kernel image (version 2.6.9-1-686)
>However, the directory /lib/modules/
>directory belongs to a previous linux-image-
>you have deselected some modules, or installed standalone modules
>packages, this could be bad. However, if this directory exists because
>you are also installing some stand alone modules right now, and they
>got unpacked before I did, then this is pretty benign. Unfortunately,
>I can not tell the difference.
>If /lib/modules/
>linux-
>installation of this kernel image (nothing has been changed yet).
>If this directory is because of stand alone modules being installed
>right now, or if it does belong to an older linux-image-
>package but you know what you are doing, and if you feel that this
>image should be installed despite this anomaly, Please answer n to the
>question.
>Otherwise, I suggest you move /lib/modules/
>perhaps to /lib/modules/
>re-installing this image.
>Do you want to stop now? [Y/n]
This was fixed a long time ago for the right cases:
kernel-package (8.066) unstable; urgency=low
* to default target for mips(el) changed between 2.4 and 2.5. Applied a
closes: Bug#214590
patch from Guido Guenther <email address hidden> to fix this.
* Disable the "out of the way" warning in image.preinst
when these conditions are met:
1. This is an official kernel (perhaps a substitution in the preinst?)
2. This is an upgrade.
The reason is that when I make bug fix releases that do not change the
ABI, modules compiled for the previous kernel will continue to
work. Unfortunately, the users tend to be scared off by the "out of
the way" warning and end up aborting the install and filing a bug.
Made it so. closes: Bug#214529
-- Manoj Srivastava <email address hidden> Tue, 7 Oct 2003 11:23:43 -0500
Are you not using an official kernel?