[Bug 1788775] Re: updating grub can end up with loopback devices in grub.cfg
"If you are building an image and later transferring that image to bare metal" this is exactly how pre-generated configs are created during ubuntu image builds, I believe. I suppose an explicit flag could be introduced to allow loopback entry generation for use during image builds, but I don't think it is worth the trouble. ** Changed in: grub2 (Ubuntu) Status: Triaged => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788775 Title: updating grub can end up with loopback devices in grub.cfg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788775] Re: updating grub can end up with loopback devices in grub.cfg
How is this something relied on for building images? As it stands, such a boot entry is non functional since it doesn't tell grub to set up a loop mapping to the underlying file so the "disk" won't be found. If you are building an image and later transferring that image to bare metal, then it would work ( who does this? ), but does that use case only need to get the running system set up, or does it also need to be able to have os-prober add entries for other installations too? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788775 Title: updating grub can end up with loopback devices in grub.cfg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788775] Re: updating grub can end up with loopback devices in grub.cfg
** Changed in: grub2 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788775 Title: updating grub can end up with loopback devices in grub.cfg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788775] Re: updating grub can end up with loopback devices in grub.cfg
Hmm that's a fair point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788775 Title: updating grub can end up with loopback devices in grub.cfg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788775] Re: updating grub can end up with loopback devices in grub.cfg
Well, we do use loop devices and do expect them to be listed for building the images. I'm not sure if there'll be a way to differentiate between the image build case and normal case to be able to pass some parameter (--skip-loopback, whatever) as appropriate. Let's look into that. ** Changed in: grub2 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788775 Title: updating grub can end up with loopback devices in grub.cfg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
