Package: grub Version: 0.97-59 Severity: important When a system has /boot on a separate partition the created grub.cfg will fail to load the system since it creates absolut paths containing /boot/.. When a system boots and /boot is on a separate partition files can only be found like this: /...
An example: linux /boot/vmlinuz-2.6.30-2-amd64 root=UUID=bfc2cb3a-22ab-433f-bd19-685cb628d6fd ro quiet But when booting the file must be accessed this way since /boot will be an empty mount point on /: linux /vmlinuz-2.6.30-2-amd64 root=UUID=bfc2cb3a-22ab-433f-bd19-685cb628d6fd ro quiet -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages grub depends on: ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy ii grub-pc 1.97+20091125-1 GRand Unified Bootloader, version grub recommends no packages. grub suggests no packages. -- debconf information: * grub/migrate_from_legacy: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org