From: Manoj Srivastava <[EMAIL PROTECTED]> Subject: Re: kernel-image with the same version Date: 17 Aug 2000 13:44:24 -0500
> To recap: > a) potato install installed 2.2.17. You now want a new kernel > b) You moved /lib/modules/2.2.17 to 2.2.17-old > c) you installed your own version of 2.2.17 > d) You now have one /boot/vmlinuz-2.2.17, and both /vmlinuz and > /vmlinuz.old link to it. Yes, these are exactly the problem I encountered. > There is o real way of avoiding this. Even if you moved > /boot/vmlinuz-2.2.17 to /boot/vmlinuz-2.2.17.old, that kernel may > not be bootable after step (c) since it shall continue to look for > its modules in /lib/modules/2.2.17 (which are totally different set > of modules). > > In these situations I download and create a 2.2.16 version, > test and ensure that works, and then install my 2.2.17 version. I > know this is suboptimal, but until we can tell a kernel-image at boot > time where to find it's modules, that's the best we can do. I see, I got your ponts. A rather complicated but safe enough methods! Thanks for your suggestion. Best Regards, 2000.8.18 -- Debian JP Developer - much more I18N of Debian Atsuhito Kohda <[EMAIL PROTECTED]> Department of Math., Tokushima Univ.
