Bug#558286: grub.cfg is wrong if /boot is on a separet partition as /

Felix Zielcke fzielcke at z-51.de
Fri Nov 27 20:39:42 UTC 2009


reassign 558286 grub-common
forcemerge 558286 558255
thanks

Am Freitag, den 27.11.2009, 17:06 +0100 schrieb Michael Rasmussen:
> 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
> 

Please see http://bugs.debian.org/558042
Someone provided a /etc/grub.d/10_linux which fixes this.

-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer






More information about the Pkg-grub-devel mailing list