read-only rootfs + boot parameters

Hello!

I noticed that APPEND is left unchanged when adding "read-only-rootfs" to IMAGE_FEATURES. The effect is (at least in refkit, which uses an initramfs based on initramfs-framework) that the rootfs initially gets mounted read/write and then gets remounted by systemd as read-only - but only after writing to /etc/machine-id.

Is that the desired behavior or an oversight?

To me, read-only means read-only, with no exceptions. The obvious fix
is:
APPEND_append = "${@ bb.utils.contains('IMAGE_FEATURES', 'read-only-rootfs', ' ro', '', d)} "

I'm just not sure whether that should go into image.bbclass or elsewhere.

--
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core