URL:
<http://savannah.gnu.org/bugs/?28843>
Summary: Running grub-mkconfig under busybox outputs
undesired configuration
Project: GNU GRUB
Submitted by: bookmarc
Submitted on: Mon 08 Feb 2010 07:02:30 PM GMT
Category: Configuration
Severity: Major
Priority: 5 - Normal
Item Group: Software Error
Status: None
Privacy: Public
Assigned to: None
Originator Name: Marc
Originator Email: [email protected]
Open/Closed: Open
Discussion Lock: Any
Release:
Release: 1.97
Reproducibility: Every Time
Planned Release: None
_______________________________________________________
Details:
Hi,
I am currently using grub version 1.97.1.
I work on a small linux distro based on busybox and I recently observed a
strange behavior from grub-mkconfig. It seems that running grub-mkconfig on a
platform that doesn't have the /dev/disk/by-uuid/UUID nodes yields a grub
config that uses the kernel device name /dev/sdXN instead of the device UUID
even if this UUID is available through grub-probe.
This can be observed with the root=/dev/sdXY argument of the kernel boot
parameters.
This means that grub-mkconfig is dependant on whatever event system is
present on the system. For example, busybox uses mdev to create device nodes
under /dev, ubuntu-like distros use udev. mdev doesn't create the uuid
symlinks in /dev unlike udev.
IMHO, it would be desirable to use the UUID provided by grub-probe _even_ if
the device node UUID does not exists. This would ensure that grub works on a
wider range of linux platforms.
I was able to fix this on my platform by removing the:
test -e "/dev/disk/by-uuid/${GRUB_DEVICE_UUID}"
line in /etc/grub.d/10_linux.
Regards,
Marc
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?28843>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-grub mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-grub
