I'm using a unionfs'd root-fs (via NFS), (btw: it works pretty fine for me) So actually my root-fs is read-only but after the union (e.g. ro root-fs + rw ramfs) has been established (initramfs did this) it's (or at least seems to be) writeable again... :-) :-/ :-( :-/ :-) Some details on the problem: ==> checkroot init-script checks (by touching) / whether root-fs is writeable. If so it will (try to) remount / read-only (that causes errors for my nfs-based root-fs) As a workaround I enhanced "checkroot" a little bit (more ugly than perfect) to detect union'd root-fs. The hack forces checkroot to skip any action in case it's a union. My hack is more a kind of case-study / proof-of-concept than a nice solution. In my opinion there should be a better solution. E.g. enhancing functions.sh with a function similar to is_net_fs: "is_union_fs". You are the baselayout-expert's so I leave it to you whether and if so how to realize/integrate this workaround. ;-) I also have filled a (informational-only) bugreport 129971 for the "genkernel-maintainers" please also have a look there for further details...
Created attachment 84662 [details, diff] ugly checkroot hack to detect union'd root-fs and afterwards ignoring them
I've put a cleaner fix in 1.12.0-r1, but I've credited you in the Changelog - thanks :)
