Hi, I have a board that has highly specific boot process. I managed to get the chain working up to boot a kernel, but now (on the unsquashed minimal install cd fs), it won't execute /sbin/init because it is not a static executable. It would be really nice to have it static. Would it be complicated? Reproducible: Always
I think you need to provide a more thorough explanation for why you need init to be static.
(In reply to Mike Gilbert from comment #1) > I think you need to provide a more thorough explanation for why you need > init to be static. That would make the install cd usable even if another kernel (possibly patched) is needed to boot.
Sorry, but that makes no sense.
It does actually, as having a minimal install rootfs, also usable by a different kernel, breaks the chicken-and-egg problem of having a suitable rootfs to build an installation.
Are you using a kernel that is incapable of running a dynamically linked binary?
(In reply to Étienne Buira from comment #2) > (In reply to Mike Gilbert from comment #1) > > I think you need to provide a more thorough explanation for why you need > > init to be static. > > That would make the install cd usable even if another kernel (possibly > patched) is needed to boot. We understand that you're saying that it's necessary to make the system boot. But we don't understand why that is. Why does /sbin/init need to be static for your custom kernel to use it?
Sorry, i shall resolve the errno before filing a bug. This were due to missing permissions while i always thought it was mandatory for init to be static.
