Red Hat Bugzilla – Bug 1012686
package request: install BFO in grub (boot.fedora.org)
Last modified: 2017-11-16 13:50:49 EST
BFO is cool. A rpm package that would install it on grub would be nice.
Its easy to do manually:
> wget -O/boot/bfo.lkrn http://dl.fedoraproject.org/pub/alt/bfo/bfo.lkrn
> grubby --add-kernel=/boot/bfo.lkrn --title="Boot BFO"
If it was a package, I wouldn't have to remember to do it everytime I reinstall fedora. c.f., memtest86+.
Not a bad idea... I'm afraid I don't have time to work on it currently however.
Would you (or someone you know) be interested in creating the package? I could help review.
Created attachment 812243 [details]
Here's my rough attempt.
* Foolishly, I haven't actually tested booting the result (next time I have an ethernet connection...)
* Here's the SRPM:
* I've got the spec file and other bits and pieces on github:
* rpmlint reports errors, other issues noted in TODO.md on github.
So, a few things... do we want the package to build the file, or just have some kind of wrapper that asks the user when they run it to download the one already built on boot.fedoraproject.org? On one hand it would need net and prompting, on the other it would avoid different versions.
Instead of grub2-mkconfig you likely want to call 'grubby' to add the entry.
I don't have a strong opinion but here's my thinking:
1) Fedora documentation suggests packages should be able to build
2) We can control what checkout from ipxe is used so controlling
versions should be easy.
3) I tried to have an RPM that does the steps in:
So one could in the future use the RPM intead of those instructions...
4) You could put the .spec file and other bits info the
Re: grubby. I put the entry in /etc/grub.d/ but then I don't know what grubby command rebuilds grub2.cfg. I did take a quick look at the kernel rpm's but I didn't see how to do it.
FWIW, I think the grubby instructions at http://boot.fedoraproject.org/faq are suboptimal b/c AFAICT the command modifies grub2.cfg *directly* (and thus will not survive recreating grub2.cfg). Putting files into /etc/grub.d/ seems to be The Right Way.
sorry, I meant /boot/grub2/grub.cfg
Created attachment 812851 [details]
Created attachment 812856 [details]
bfo.spec, fix changelog
I guess the 'official' way to add/update the bootloader these days is to call /sbin/new-kernel-pkg with the right arguments. That would call grubby if grub was used, extlinux updated if thats in use, etc.
1) I honestly can't tell what is "official". I also see this:
But at any rate, both "new-kernel-pkg" and "kernel-install" concentrate on *kernels*, i.e., initrd's etc. I just want to update the /boot/grub2/grub.cfg file ;-)
My current plan is watch memtest86:
Once its sorted there, I'll try to do whatever they do.
2) I assume Fedora has these extra layers of grubby/new-kernel-pkg/kernel-install etc because we support multiple bootloaders (I can't think of any other reason!) But does that mean this BFO package needs to support those other bootloaders? They must each have their equivalent of /etc/grub.d/20_bfo files...
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
@Kevin: do you think there is still interest in BFO? It still works my bios rawhide VM... but haven't tested on my EFI laptop.
Assuming there is still interest, maybe I should stop building from source and just grab the current "bfo.lkrn"... I.e., I could do a much simpler package:
1. install a "bfo-setup" script (c.f., memtest86+)
2. bfo-setup would "wget" the latest bfo.lkrn
3. bfo-setup would write the "etc/grub.d/20_bfo" file
4. It would tell inform the user to do "grub2-mkconfig -o /boot/grub2/grub.cfg"
(3 and 4 are what memtest86+ still does so its not too unreasonable).
(In reply to Colin Macdonald from comment #12)
> @Kevin: do you think there is still interest in BFO? It still works my bios
> rawhide VM... but haven't tested on my EFI laptop.
Hard to say. ;) EFI isn't working sadly, see:
> Assuming there is still interest, maybe I should stop building from source
> and just grab the current "bfo.lkrn"... I.e., I could do a much simpler
> 1. install a "bfo-setup" script (c.f., memtest86+)
> 2. bfo-setup would "wget" the latest bfo.lkrn
> 3. bfo-setup would write the "etc/grub.d/20_bfo" file
> 4. It would tell inform the user to do "grub2-mkconfig -o
> (3 and 4 are what memtest86+ still does so its not too unreasonable).
That would work for me.
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.