Description of Problem:
Steps to Reproduce:
1. edit /boot/grub/grub.config to include a initrd, set its path to say
2. reboot, and it fails of course
I initially used a "absolute" path, which is incorrect.
However, the use of relative paths in this case is a bit odd, in
my opinion. The comment in the default grub.conf of:
# NOTICE: You have a /boot partition. This means that
# all kernel paths are relative to /boot/
Doesnt really help any. Since grub wants the path name in
the form "/initrd-foo.img". Which seems like an absolute
path to me (paths starting with / are generally absolute
paths to my brain...)
If you ignore that bit, the path still works out mentally
as /boot//initrd-foo.img, which while valid, is a bit strange.
I suspect changing this odd behaviour in grub is painful,
so a better comment wouldnt hurt (with example?). Some info
in the grub interactive editing screen wouldnt hurt either.
Adding a more descriptive comment would be a good thing.
We (Red Hat) should try to fix this for the next release.
Ask and ye shall receive... added an example stanza for both cases (having a
/boot and not having a /boot) commented out at the top with an initrd line.