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.
/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
Bug #168715 is a very good example of why this change would be useful:
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?