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
