link_in_boot (was: Bug#613200: linux-base: lilo.conf not updated to UUIDs for kernels not in /)
On Sun, 2011-02-13 at 20:24 +0100, Bjørn Mork wrote:
> Ben Hutchings <email@example.com> writes:
> > This has nothing to do with where the kernel images are (they are always
> > installed in /boot), but only to do with where the symlinks are created.
> > The default is to create them in /, but I recall there is an option (now
> > deprecated) to create them in /boot.
> Not related to this bug, but I was wondering: Why deprecate this
All configuration through kernel-img.conf is deprecated. It is a legacy
of kernel-package, and even current versions of kernel-package do not
> I find it very useful for systems where I keep /boot in a separate
> partition. Having the symlinks in the same partition allow you to
> configure boot loaders like extlinux with the generic symlink names.
They should be using hook scripts to generate a separate entry for each
installed kernel version.
> The links in / are generally not very useful IMHO if /boot and / are
> different partitions.
That depends on whether the symlink is resolved at installation time or
at boot time.
Once a job is fouled up, anything done to improve it makes it worse.