Re: kernel-image with the same version
Hi, 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. 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. manoj -- Humor in the Court: Q: ...any suggestions as to what prevented this from being a murder trial instead of an attempted murder trial? A: The victim lived. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Re: kernel-image with the same version
Atsuhito == Atsuhito Kohda [EMAIL PROTECTED] writes: Atsuhito From: Ben Collins [EMAIL PROTECTED] Atsuhito Subject: Re: kernel-image with the same version Atsuhito Date: Tue, 15 Aug 2000 18:54:29 -0400 Edit /etc/kernel-img.conf and add this line: reverse_symlink := yes Atsuhito Okay I will try later. BTW, /etc/kernel-img.conf might Atsuhito be /etc/kernel-pkg.conf Umm, /etc/kernel-pkg.conf is what is looked at when one is creating the kernel-image.deb; /etc/kernel-img.conf is looked at on the system the kenel-image is being installed on. Two different files. manoj -- QOTD: When she hauled ass, it took three trips. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Re: kernel-image with the same version
On Thu, Aug 17, 2000 at 01:44:24PM -0500, Manoj Srivastava wrote: Hi, 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. There is o real way of avoiding this. Even if you moved However, there _is_ a way to avoid this. You can create different Flavours of the same kernel which may be named 2.2.17-1, 2.2.17-2, and so on. Read about this in /usr/share/doc/kernal-package/Flavours.gz However you need some handwork to patch the toplevel Makefile, but after that you can generate different kernel-flavours with make-kpkg --falvour=... ... or even make FLAVOUR=... Ingo -- I am the ILOVEGNU signature virus. Just copy me to your signature. This email was infected under the terms of the GNU General Public License.
Re: kernel-image with the same version
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.
Re: kernel-image with the same version
From: Manoj Srivastava [EMAIL PROTECTED] Subject: Re: kernel-image with the same version Date: 17 Aug 2000 13:50:13 -0500 Atsuhito Okay I will try later. BTW, /etc/kernel-img.conf might Atsuhito be /etc/kernel-pkg.conf Umm, /etc/kernel-pkg.conf is what is looked at when one is creating the kernel-image.deb; /etc/kernel-img.conf is looked at on the system the kenel-image is being installed on. Two different files. Yes, I first searched kernel-* file in /etc and found only kernel-pkg.conf so I misunderstood that the mentioned file should be this one. But afterward I read through /usr/share/doc/kernel-package/README.gz and found that /etc/kernel-pkg.conf is related with make-kpkg command but I missed the comment on /etc/kernel-img.conf which was written just after the comment on kernel-pkg.conf. Thanks for your comment. Best Regards, 2000.8.18 -- Debian JP Developer - much more I18N of Debian Atsuhito Kohda [EMAIL PROTECTED] Department of Math., Tokushima Univ.
Re: kernel-image with the same version
Hi, Atsuhito == Atsuhito Kohda [EMAIL PROTECTED] writes: Atsuhito I installed recently potato from scratch. Rescue disk installed Atsuhito kernel 2.2.17 and I rebuild kernel-image with kerne-source 2.2.17 Atsuhito so the version of kernel was same for both. Umm. This should not happen. Since /lib/modules/2.2.17 shall be clobbered with the new modules. If the modules were the same, you should have been warned on install. Atsuhito When I installed kernel-image-2.2.17*.deb which I rebuild Atsuhito then /vmlinuz and /vmlinuz.old were created but both Atsuhito pointed to the same /boot/vmlinuz-2.2.17. This means no Atsuhito back-up of old kernel was retained. If the modules were actually clobbered, you may not have a bootable old image left. Indeed, you shall not, since there is only one /boot/vmlinuz-2.2.17 Atsuhito In my case, new kernel seemed to work fine so there was no problem, Atsuhito I guessed, but this might cause problems. Atsuhito Is this inevitable or I am missing something? I think something is missing. If you replace a kernel with the same version, you end up with one /boot/vmlinuz-$VERSION, and one /lib/modules/$VERSION. You can move the /boot/vmlinuz-* around, but the kernel shall still look in the same old place for its modules. manoj -- Sendmail can safely be made setuid to root. Eric Allman, Sendmail Install Operation Guide Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Re: kernel-image with the same version
From: Manoj Srivastava [EMAIL PROTECTED] Subject: Re: kernel-image with the same version Date: 16 Aug 2000 00:31:48 -0500 Atsuhito I installed recently potato from scratch. Rescue disk installed Atsuhito kernel 2.2.17 and I rebuild kernel-image with kerne-source 2.2.17 Atsuhito so the version of kernel was same for both. Umm. This should not happen. Since /lib/modules/2.2.17 shall be clobbered with the new modules. If the modules were the same, you should have been warned on install. Yes, of course I moved /lib/modules/2.2.17 to 2.2.17-old before I installed kernel-image-2.2.17*.deb so there was no warning on installation. Atsuhito When I installed kernel-image-2.2.17*.deb which I rebuild Atsuhito then /vmlinuz and /vmlinuz.old were created but both Atsuhito pointed to the same /boot/vmlinuz-2.2.17. This means no Atsuhito back-up of old kernel was retained. If the modules were actually clobbered, you may not have a bootable old image left. Indeed, you shall not, since there is only one /boot/vmlinuz-2.2.17 As I expalined above, the modules were not clobbered, but there was only one /boot/vmlinuz-2.2.17 and both /vmlinuz and /vmlunuz.old were linked to this /boot/vmlinuz-2.2.17. I wanted to ask how to avoid this problem... I think something is missing. If you replace a kernel with the same version, you end up with one /boot/vmlinuz-$VERSION, and one /lib/modules/$VERSION. You can move the /boot/vmlinuz-* around, but the kernel shall still look in the same old place for its modules. Yes it might be so. But if one install with the current rescue disk of potato then the kernel installed is of 2.2.17 and the provided kernel-source of the latest version is of 2.2.17 so if one wants to rebuild the kernel (and generally one wants to!) then one encounters the same situation, at least for a while. Best Regards, 2000.8.16 -- Debian JP Developer - much more I18N of Debian Atsuhito Kohda [EMAIL PROTECTED] Department of Math., Tokushima Univ.
Re: kernel-image with the same version
From: Ben Collins [EMAIL PROTECTED] Subject: Re: kernel-image with the same version Date: Tue, 15 Aug 2000 18:54:29 -0400 Edit /etc/kernel-img.conf and add this line: reverse_symlink := yes Okay I will try later. BTW, /etc/kernel-img.conf might be /etc/kernel-pkg.conf Thanks for your kind advice. Best Regards, 2000.8.16 -- Debian JP Developer - much more I18N of Debian Atsuhito Kohda [EMAIL PROTECTED] Department of Math., Tokushima Univ.
Re: kernel-image with the same version
On Wed, Aug 16, 2000 at 07:43:14AM +0900, Atsuhito Kohda wrote: Hi all, I installed recently potato from scratch. Rescue disk installed kernel 2.2.17 and I rebuild kernel-image with kerne-source 2.2.17 so the version of kernel was same for both. When I installed kernel-image-2.2.17*.deb which I rebuild then /vmlinuz and /vmlinuz.old were created but both pointed to the same /boot/vmlinuz-2.2.17. This means no back-up of old kernel was retained. In my case, new kernel seemed to work fine so there was no problem, I guessed, but this might cause problems. Is this inevitable or I am missing something? Edit /etc/kernel-img.conf and add this line: reverse_symlink := yes That will make /vmlinux the actual file, and the ones in /boot will be the symlinks. That may solve your problem (try installing the kernel again to test). -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
