On Mon, Jun 18, 2018 at 11:55:28PM +0100, Tom Hughes wrote: > On 18/06/18 23:46, Javier Martinez Canillas wrote: > > On Mon, Jun 18, 2018 at 11:54 PM, Tom Hughes <tom@xxxxxxxxxx> wrote: > > > On 18/06/18 18:15, Peter Jones wrote: > > > > > > > That's true - though we actually shipped nearly all of the code to > > > > implement this stuff f28, minus some parts of the upgrade story and the > > > > anaconda bits to enable it by default. You can go run > > > > grub2-switch-to-blscfg today, and it will work. I hope :) > > > > > > > > > Unless you have /boot on your root partition like this machine > > > seems to have for some reason... Then it breaks because the loader > > > fragments use /vmlinuz... rather than /boot/vmlinuz etc. > > > > > > > Yes, /boot not being a mount point was an issue (and also /boot being > > a btrfs subvolme) but it got fixed [0] a couple of weeks ago. Now the > > 20-grub.install kernel-install script uses grub2-mkrelpath to get the > > relative path of the kernel and initramfs images, which is the same > > that's done by the /etc/grub.d/10_linux script. It's just that the > > grub2 update didn't made to F28 yet. > > Does that extend to grub2-switch-to-blscfg as well? That was what > broke my boot. Yes, I've already got that fixed in my git repo, and it'll be fixed to do that when I do the next f28 update. -- Peter _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/QESTGIFYYKKBHCBSVYZ4EURLVIO4QTZH/
