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.
I tried
> try to execute ash instead of init
>mv /sbin/init /sbin/init.old
> echo "#!/bin/sh
>while true; /bin/ash; done" > /sbin/init
>chmod a+x /sbin/init
But,It gives
Going to execute /sbin/init
sh:
It gives blinking cursor.It does nothing afterwards.
Does it mean I have to execute init? I tried to type something, it
does nothing unlike normal shell.
Plz help me.
On 8/9/06, Roberto A. Foglietta <roberto.foglietta@xxxxxxxxx> wrote:
Bhagyashri Bijwe wrote:
>
> Hi,
> I made distribution for Soekris4521 using linux2.2.16,
> UClibc0.9.19 and busybox-1.00-pre4.
Why you use busybox-1.00-pre4?
The "pre4" means it is not stable but the 4th try to deliver
busybox-1.00. I suggest to use busybox-1.00
try to execute ash instead of init
mv /sbin/init /sbin/init.old
echo "#!/bin/sh
while true; /bin/ash; done" > /sbin/init
chmod a+x /sbin/init
or try this
> etc/init.d/rcS is
>
> mount -t proc none /proc
while true; /bin/ash; done
an try to execute init by hand
Cheers,
--
Roberto A. Foglietta
http://roberto.foglietta.name
http://linux.genova.it
--
***********************************************
Ms Bhagyashri Bijwe
Project Eng.
Networking and Internet Software Group,
Centre for Research and Development,
Pune,India
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
