Hi Alejandro
On 02.02.2022 07:58, Alejandro Hernandez wrote:
Hey Vyacheslav,
...I definitely tried extending the overlay-etc class but it simply
does not work for this, since the rootfs becomes inaccessible once the
system has booted, ...
That's what I meant. What if we added another parameter, let's say
OVERLAY_OLDROOT_MOUNT. If it's set, then lower layer can bind mounted to
that mount point. In that case -etc part of overlayfs-etc has to be
changed for something else, of course, to make it more general purpose
class. Perhaps overlayfs.bbclass can be renamed to
overlayfs-systemd.bbclass then?
What do you think?
... but it is a different use case and boot flow so I believe both can
co-exist for different workflows depending on the user needs...
My concern here is code duplication :) If we find an issue in one place,
we would need to change it in two places.
Thanks,
Vyacheslav
Cheers,
Alejandro
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161183):
https://lists.openembedded.org/g/openembedded-core/message/161183
Mute This Topic: https://lists.openembedded.org/mt/88773634/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
