Eibo Thieme:
> Putting a
>
> /bin/sh
>
> in the first rc script enabled me to test for the error with everything
> disabled, it is there and it it is triggered just the same.
Ok.
It looks like /etc/fstab is unrelated. And we should focus what the last
line of initramfs executes.
exec /bin/run-init ${TARGET} /sbin/init "$@" <${TARGET}/dev/console
>${TARGET}/dev/console
If you can try "strace -f -o ${TARGET}/somewhere/log /bin/run-init ..."
And where can I get the source code of run-init?
> I will try to have a closer look at the mechanics of switching over from
> initramfs, maybe I can get it to trigger even there. One other option of
> debugging is the question, why does ls /aufs/server trigger the error
> and ls /aufs/client not. Both directories as mounted in the same way,
> client will be ro+wh in the aufs mount, server ro only, will have a look
> there as well, probably over the weekend.
Currently I don't know why two "ls"-es affect the problem. Are they
really related?
And, of course, I will never hush you. :-)
J. R. Okajima
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
