HelloIt looks like the run-init fails if there are non-removable files outside of /
Accidentally the device that was used for mounting /root and /root are both in / so run-init works.
I cannot find any documentation for run-init except the usage that says to pass it the old root and the new root, nothing about requirements about their position in the fs hierarchy.
As this is undocumented and unintuitive I find this behaviour undesirable. It looks like run-init works more by accident than by design.
I attach a patch that both reports any files that are not removed for debugging purposes and continues the run-init process after all files are tried. Failure to remove a file or directory (be it /root, / root-device-node or /some/leftover/mount/point) does not stop run- init so the boot process continues.
Please consider at least the minimal change - continue run-init even if removing files from the old root fails.
Thanks Michal
klibc-run-init-nuke-debug.patch
Description: Binary data
