Re: Multi-level symlinks for default kernel
Hi, On Tue, 22 Jul 2003 16:29:59 -0700, Mike Fedyk [EMAIL PROTECTED] said: Hi, I am wondering if anyone else is having the same problems I am with debian keeping the vmlinuz symlink in /. I have several systems where /boot is the only filesystem accessable by the boot loader because of software raid, or possibly lvm (haven't done this yet, but thinking about it). I regularly build my own kernels with make-kpkg, so I changed it to put the vmlinuz symlink in /boot, and changed my menu.lst file in grub to use this symlink to boot from. From man kernel-img.conf: link_in_boot Set to Yes if you want the symbolic link to the kernel image, namely, vmlinuz in /boot rather than the default /. The old, and very confusing, name image_in_boot is deprecated, since it is the symbolic link that is usually being relocated. Defaults to No. manoj -- The truth you speak has no past and no future. It is, and that's all it needs to be. 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: Multi-level symlinks for default kernel
debian-policy@lists.debian.org Bcc: [EMAIL PROTECTED] Subject: Re: Multi-level symlinks for default kernel Reply-To: In-Reply-To: [EMAIL PROTECTED] On Fri, Jul 25, 2003 at 01:17:27AM -0500, Manoj Srivastava wrote: Hi, On Tue, 22 Jul 2003 16:29:59 -0700, Mike Fedyk [EMAIL PROTECTED] said: I regularly build my own kernels with make-kpkg, so I changed it to put the vmlinuz symlink in /boot, and changed my menu.lst file in grub to use this symlink to boot from. From man kernel-img.conf: link_in_boot Set to Yes if you want the symbolic link to the kernel image, namely, vmlinuz in /boot rather than the default /. Yes, that's the one. I didn't spell it out because I didn't want the discussion to fragment to OT.
Re: Multi-level symlinks for default kernel
On Tue, Jul 22, 2003 at 07:48:33PM -0400, Morgon Kanter wrote: I am wondering if anyone else is having the same problems I am with debian keeping the vmlinuz symlink in /. I have several systems where /boot is the only filesystem accessable by the boot loader because of software raid, or possibly lvm (haven't done this yet, but thinking about it). I regularly build my own kernels with make-kpkg, so I changed it to put the vmlinuz symlink in /boot, and changed my menu.lst file in grub to use this symlink to boot from. In this situation, why don't you just forget about the /vmlinuz symlink altogether and just have /boot/vmlinuz point to the proper kernel image? That is exactly what I want. But /vmlinuz - /boot/vmlinuz, and vmlinuz.old - /boot/vmlinuz.old is there for compatability, and upgradability. Later at any point /vmlinuz and /vmlinuz.old can be unused completely, either way it doesn't matter if they're used or not once they point to the symlinks in /boot. (on my system there is no symlink, I just update grub to point to a new kernel image). I don't see what grub has to be patched for. Bug #168715 is a very good example of why this change would be useful: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=168715 Currently there are no symlinks created in /boot by default, and not needing to run update-grub at each kernel update is a great advantage (no need to edit the menu manually from the boot menu just because you forgot to run update-grub before rebooting). And by making this change generic, other boot loaders can benefit from this also by default, and it leaves lilo to work as it does now. Also maybe debian-user isn't the right list, is there another list more appropriate for this? Maybe debian-policy?
Re: Multi-level symlinks for default kernel
I am wondering if anyone else is having the same problems I am with debian keeping the vmlinuz symlink in /. I have several systems where /boot is the only filesystem accessable by the boot loader because of software raid, or possibly lvm (haven't done this yet, but thinking about it). I regularly build my own kernels with make-kpkg, so I changed it to put the vmlinuz symlink in /boot, and changed my menu.lst file in grub to use this symlink to boot from. In this situation, why don't you just forget about the /vmlinuz symlink altogether and just have /boot/vmlinuz point to the proper kernel image? (on my system there is no symlink, I just update grub to point to a new kernel image). I don't see what grub has to be patched for. Morgon -- Man is the only creature capable of hating itself -- Governor of Japan in The End of Evangelion
Re: Multi-level symlinks for default kernel
On Tue, Jul 22, 2003 at 07:48:33PM -0400, Morgon Kanter wrote: I am wondering if anyone else is having the same problems I am with debian keeping the vmlinuz symlink in /. I have several systems where /boot is the only filesystem accessable by the boot loader because of software raid, or possibly lvm (haven't done this yet, but thinking about it). I regularly build my own kernels with make-kpkg, so I changed it to put the vmlinuz symlink in /boot, and changed my menu.lst file in grub to use this symlink to boot from. In this situation, why don't you just forget about the /vmlinuz symlink altogether and just have /boot/vmlinuz point to the proper For compatability with other boot loaders that do use /vmlinuz, and old installations. Last time I posted something comprehensive, they nit picked the hell out of it on the list. So I'm going for the incremental style. kernel image? (on my system there is no symlink, I just update grub to point to a new kernel image). I don't see what grub has to be patched for. Because the default kernel build gives you /boot/vmlinuz, and /boot/vmlinuz.old (what /boot/vmlinuz pointed to previously), which lilo uses. It would just add two boot entries for vmlinuz and vmlinuz.old Also, it would make it more standards compliant. And if the kernel build system isn't a standard, I don't know what is. Mike
