Re: ifupdown writes to /etc... a bug?
On Wed, Mar 12, 2003 at 11:02:06AM +1100, Brian May wrote:
> On Tue, Mar 11, 2003 at 11:19:24AM -0500, Matt Zimmerman wrote:
> > I believe the problem is that these dependencies cannot be properly
> > calculated until the corresponding kernel is running. I do not know whether
> > this is a limitation in the design or the implementation.
> I heard somewhere that if depmod produces unreliable results when
> running a different kernel, then the initrd image that mkinitrd builds
> will be faulty. Or does ther initrd image also have a copy of depmod?
> So I presume that any problems that use to occur no longer occur.
> I thought the solution was to tell depmod to use the System.map
> file of the appropriate kernel.
> Of course, I could be mistaken... I hardly keep up-to-date here.
kernel-package certainly believes that this is still true.
print STDERR <<"EOFERR";
You are attempting to install a kernel version that is the same as
the version you are currently running (version $running). The modules
list is quite likely to have been changed, and the modules dependency
file /lib/modules/$version/modules.dep needs to be re-built. It can
not be built correctly right now, since the module list for the
running kernel are likely to be different from the kernel installed.
I am creating a new modules.dep file, but that may not be
correct. It shall be regenerated correctly at next reboot.
I repeat: you have to reboot in order for the modules file to be
created correctly. Until you reboot, it may be impossible to load
some modules. Reboot as soon as this install is finished (Do not
reboot right now, since you may not be able to boot back up until
installation is over, but boot immediately after). I can not stress
that too much. You need to reboot soon.