I've found a work around :now I never reboot any distant machine,
I never follow the stressing instructions provided :
You are attempting to install a kernel version that is the same as the version
you are currently running (version
> 2.6.18-4-686).
The modules list is quite likely to have been changed, and the modules
dependency file
> /lib/modules/2.6.18-4-686/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.
There are so many bugs indicating boot problems for so much different reasons (394608,334831,327335,422217,462221...)
that I can't take this risk on distant production servers until I get a solution to really double check the boot process
before running it for true.
I was unable to choose between yaird and kexec as the informations provided
were contradictory...
thanks for all anyway
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
