No more tasks for init ---- sleeping forever
Rob Landley
rob at landley.net
Wed Aug 16 22:14:55 UTC 2006
On Wednesday 09 August 2006 4:27 am, Bhagyashri Bijwe wrote:
> Hi,
> Thanks for reply.
> I am using busybox-1.00-pre4 instead of busybox-1.00 because I
> have product on gcc version 2.96 and busybox-1.00 required GLIBC_2.3.
It should be quite happy with a recent version of uClibc instead. (And you
can statically link the sucker against uClibc if you don't want to modify the
libraries you've already got on the system. Wastes some space, but it's
compatible.)
> Going to execute /sbin/init
> sh:
>
> It gives blinking cursor.It does nothing afterwards.
Not a clue.
Some combinations of kernels and busybox don't want to run busybox sh as
#!/bin/sh because the kernel doesn't set argv[0] to /bin/sh but instead sets
it to the name of your script. I'm still working on that. (The current
scripts/individual work is one way to address it. Possibly adding optional
code to busybox.c to look at argv[1] and do something intelligent, dunno
yet.)
> Does it mean I have to execute init? I tried to type something, it
> does nothing unlike normal shell.
I'd stick printf() calls into init.c to see what it's doing. I believe stdout
should point to /dev/console...
Rob
--
Never bet against the cheap plastic solution.
More information about the busybox
mailing list