Red Hat Bugzilla – Bug 493681
RFE: grubby should be able to add entries at the end as well as the beginning of grub.conf
Last modified: 2010-05-03 03:45:13 EDT
Description of problem:
It appears that grubby only knows how to add entries at the beginning of grub.conf, which is fine if only only needs to add kernels, and only in chronological order. But one might want to add kernels out of order, but have them properly sorted in grub.conf anyway. In addition, memtest86+ uses grubby to add the Memtest86+ entry, which should really be added at the end, but due to grubby's limitation it has to add it at the beginning (see bug #489110). It would be nice if grubby had enough extra flexibility to handle these situations somehow.
Version-Release number of selected component (if applicable):
For the memtest86+ case, it is also important
the ability of adding parameters not necessarily
at the end of the line, as exampled below:
kernel --type=netbsd /memtest86+-2.11
Comment from Bug Zapper
Thank you for your bug report. This looks to me like a future feature wish-list.
Requests for packaging/Feature requests are kept at:
Please add this package/Feature request to this list if it isn't there already.
I could change the status as CLOSED:NOTABUG, if someone else could approve my comment.
Fedora Bugzappers volunteer triage team
Since fixing bug #489110 depends on this additional functionality (unless the code of grubby is copied and modified in memtest86+, which would be a bad idea), I'm not sure this should be considered merely a feature wish-list. Please do not close this bug.
(In reply to comment #3)
> Since fixing bug #489110 depends on this additional functionality (unless the
> code of grubby is copied and modified in memtest86+, which would be a bad
> idea), I'm not sure this should be considered merely a feature wish-list.
> Please do not close this bug.
I must say the chance of someone finding the time to implement this is
rather small. Why can't the memtest86+ post install script just
grep for memtest86 in grub.conf and if it is not there already
just append the relevant lines using echo "...." >> /etc/grub.conf ?
Paulo, what do you think? I will close this as NOTABUG (and not even bother to add it to the feature wish-list) if you think you can fix bug #489110 using Hans de Goede's suggestion. Thinking about the issue of keeping kernels sorted, I realized that entries could be added by hand, and that if the existing entries were unsorted, there's no good way for grubby to fix that anyway.
Grubby is a C application (written by RedHat),
which is able to deal with grub and lilo.
This is the reason for memtest86+ using it, I guess.
Actually, the recent modifications for supporting the elf
version will not work with lilo (although I think lilo is no longer
supported in Fedora).
Furthermore, Warren Togami and Jeremy Katz are against updating grub.conf
(please, see the last comment on # 494157).
I know I can forget grubby at all, and easily add memtest entry
at the end of grub.conf, but it seems to me that a lot of people
will think this is an insecure/undesirable approach.
As soon as we reach to a consensus, I will be glad to implement
anything the community thinks it is the best.
This is a mass edit of all mkinitrd bugs.
Thanks for taking the time to file this bug report (and/or commenting on it).
As you may have heard in Fedora 12 mkinitrd has been replaced by dracut. In Fedora 12 the mkinitrd package is still around as some programs depend on
certain libraries it provides, but mkinitrd itself is no longer used.
In Fedora 13 mkinitrd will be removed completely. This means that all work
on initrd has stopped.
Rather then keeping mkinitrd bugs open and giving false hope they might get fixed we are mass closing them, so as to clearly communicate that no more work will be done on mkinitrd. We apologize for any inconvenience this may cause.
If you are using Fedora 11 and are experiencing a mkinitrd bug you cannot work around, please upgrade to Fedora 12. If you experience problems with the initrd in Fedora 12, please file a bug against dracut.
Seems to me a grubby feature rather than mkinitrd bug. Right?
Paulo, are you still willing to implement this?
...anyone, feel free to reopen and/or work on it, in case you're interested.