I see. Makes sense. But then I expect /boot to make RO and to enable the overlayfs in one step by raspi-config and I have to revert this when I want to update my OS. But why can I enable the overlayfs but keep /boot RW?The kernel will be updated in /boot/firmware, as will the initramfs - and the kernel modules in /lib/modules. However those modules are on the overlayfs and will be lost at the next boot (as will any other updates).
Because you might want to? For things like editing config.txt, cmdline.txt and other config files.
Last time I used raspi-config to do this, enabling the overlay also prompted for whether you wanted to make the boot partition be mounted ro so only a single reboot is need.
You can't do this when disabling it. You need one reboot to make the root partition rw then a second reboot after fstab has been update to mount the boot partition rw.
TBH, if you don't want to boot partition written to don't mount it and set the mount point for it as ro and/or immutable. Aside from kernel and firmware updates it doesn't need to be mounted for the system to run.
Statistics: Posted by thagrol — Wed Jul 03, 2024 9:46 pm