link_in_boot (was: Bug#613200: linux-base: lilo.conf not updated to UUIDs for kernels not in /)
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
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.
The links in / are generally not very useful IMHO if /boot and / are
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org