----- Original Message ----- > OK part of my confusion is that 'grub2-mkconfig' does not work when > called directly. Doing that results in a malformed grub.cfg. > > What is the correct way, on atomic builds, to recreate the grub.cfg? > How does rpm-ostree do this? Yeah, I've been confused by that as well. I haven't bothered investigating more, but it seems like running grub2-mkconfig on a fresh boot works, whereas calling it after some rpm-ostree operation such as upgrade/rebase will cause no output from 15_ostree. > The closest I get to a command is 'ostree admin instutil > grub2-generate' but this fails with > ** > ERROR:src/libostree/ostree-bootloader-grub2.c:154:_ostree_bootloader_grub2_generate_config: > assertion failed: (grub2_boot_device_id != NULL) > Aborted (core dumped) > > I'm not sure what it wants. It's only meant to be called by the /etc/grub.d/15_ostree script, which sets up some env vars for it. That said, it should probably error out more gracefully. Jonathan _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
