Bug#621137: Random exec failures on ARM; breaks boot -- /init: exec: line 306: run-init: Unknown error 2372692
First of all, big, LARGE Thank you Loïc, for the great work
you've done about this bug.
Somehow I haven't received earlier messages for #621137 even
when I'm subscribed, or else I'd reply sooner.
I wanted to get rid of that patch completely, together with
CONFIG_STANDALONE_SHELL busybox config option (which makes
its shell to search for commands internally first and in
$PATH second), but unfortunately initramfs-tools relies on
this hack still (I submitted a patch for that to initramfs-
tools a while back) hence it stays for now.
I very much hope this all will be sorted out for good for
wheezy, whithout applets-fallback.patch and other hackery.
But so far, since the thing is still needed, and since gcc
isn't yet in good state, your patch is necessary, and it
looks good too - excellent spot. This code (in applets-
fallback.patch) has bit-rotted for a bit. Quite interesting
effect on gcc too ;)
08.04.2011 04:06, Loïc Minier wrote:
[]
> Ah I should have submitted the changes in a branch of busybox.git;
> didn't spot the git repo -- my bad.
>
> Indeed the layout isn't too conventional: no pristine-tar branch, no
> upstream files in the repo, no upstream branch with e.g. imported
> tarballs or upstream history. Putting busybox_1.18.4-1.dsc from the
Yes the proper conversion into gbp hasn't been done in the
git.debian.org busybox repository, -- only debian branch is
there, no upstream etc. The reason - in addition to the
usual "not yet done" - is actually a bit deeper - I wanted
to clone upstream git repository into debian busybox.git,
instead of using git-import-orig, which is, at my opinion,
a step backwards compared with how git can work. But I
can't figure out how to have a "tree" of upstreams, since
upstream itself has not just single branch but many stable
subbranches which gbo does not handle well either. So the
conversion process stalled somewhat, I did lots of experiments
locally but am not satisfied with results.
So, thank you again, thank you very much for your great work
with all this stuff - both the original problem and packaging
issues. Busybox needs quite some love ;)
/mjt
Reply to: