Re: [OE-core] read-only-rootfs and EFI configuration
On Wednesday, 9 May 2018 8:19:19 AM NZST Cal Sullivan wrote: > You're right. Since its adding to APPEND from rootfs-postcommands, which > is inherited by images, its in the local space instead of global and > won't be picked up by these recipes... > > Right now it won't actually affect anything out of the box, as that > method of booting isn't default due to lack of random UUID support, but > its something that will need to be solved in the future. I've filed the following bug to track this: https://bugzilla.yoctoproject.org/show_bug.cgi?id=12755 Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] read-only-rootfs and EFI configuration
Hi Cal On Wednesday, 9 May 2018 8:19:19 AM NZST Cal Sullivan wrote: > You're right. Since its adding to APPEND from rootfs-postcommands, which > is inherited by images, its in the local space instead of global and > won't be picked up by these recipes... > > Right now it won't actually affect anything out of the box, as that > method of booting isn't default due to lack of random UUID support, but > its something that will need to be solved in the future. OK, thanks I wasn't aware of that - I do see the bugzilla entry now. The question I have is what should we cover in the release notes in terms of the user-visible features you added? Thanks, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] read-only-rootfs and EFI configuration
You're right. Since its adding to APPEND from rootfs-postcommands, which is inherited by images, its in the local space instead of global and won't be picked up by these recipes... Right now it won't actually affect anything out of the box, as that method of booting isn't default due to lack of random UUID support, but its something that will need to be solved in the future. Thanks, Cal On 05/07/2018 08:39 PM, Paul Eggleton wrote: Hi folks, So I was looking at the following commit today: http://cgit.openembedded.org/openembedded-core/commit/?id=cfc09de06ecc12bb42181004689e881c75072665 Given we've just moved the creation of the configuration to its own recipe (grub-bootconf or systemd-bootconf depending on the bootloader selected) doesn't that now pose a problem for the effectiveness of this change given that it's setting it at the image level? Let me know if I'm missing something. Cheers, Paul -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] read-only-rootfs and EFI configuration
Hi folks, So I was looking at the following commit today: http://cgit.openembedded.org/openembedded-core/commit/?id=cfc09de06ecc12bb42181004689e881c75072665 Given we've just moved the creation of the configuration to its own recipe (grub-bootconf or systemd-bootconf depending on the bootloader selected) doesn't that now pose a problem for the effectiveness of this change given that it's setting it at the image level? Let me know if I'm missing something. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
