On Sat, Mar 02, 2002 at 09:50:02PM +0200, Shaul Karl wrote: > > > > Dumb question: why does Debian like to have a symlink, /vmlinuz, > > pointing to the kernel image in /boot? Does some program depend on being > > able to find the kernel at /vmlinuz? Would something break if I simply > > deleted this symlink? > > > > > I believe one reason is because that is how the kernel-package uses to > manage things. IIRC you can tell the kernel-package to behave > differently. You might want to read the kernel-package documentation > for more information about those links. > Not sure but another reason might be to let people who need it have a > small /boot partition.
Ahh, but if you use grub, you need the same path to point to the same files from within the linux environment and when booting just loading /boot. (/vmlinuz is on / from linux, but grub reads /boot and finds no or even *old* vmlinuz (in /boot!) and fails or boots wrong kernel) As things are now, you have to change the kernel package to putting that symlink into /boot. This is one of the first things I have to do on each new system installation... :( Are there any valid requirements to put the /vmlinuz symlink in / instead of /boot?
