Non-interactive interactive shell !!
Levend Sayar
levend.sayar at karel.com.tr
Mon Apr 9 15:15:19 UTC 2007
Denis,
Here is the tail of the log :
KLOG: readtoken called
KLOG: xxreadtoken called
KLOG: pgetc called
KLOG: preadbuffer called
KLOG: preadfd called
KLOG: safe_read(0,..) calling
rs_interrupt_single(4)... /d
rs_interrupt_single(4)... e
rs_interrupt_single(4)... v
rs_interrupt_single(4)... /
rs_interrupt_single(4)... tt
rs_interrupt_single(4)... y
rs_interrupt_single(4)... S
rs_interrupt_single(4)... 0
rs_interrupt_single(4)...
rs_interrupt_single(4)...
rs_interrupt_single(4)... re
rs_interrupt_single(4)... ad
rs_interrupt_single(4)... ..
rs_interrupt_single(4)... .
rs_interrupt_single(4)...
readlink(/proc/self/fd/0) -> /dev/ttyS0 as you see.
And what we see is just "read..." from safe_read.
What is good for busybox is this problem seems to be not due to busybox.
Since I statically compiled a simple app (myshell) from code below:
#include <unistd.h>
int main(int argc,char** argv)
{
char buf[64];
while (1) {
int ret = read(0,buf,sizeof(buf));
write(1,buf,ret);
}
return(0);
}
and when I give init=myshell, it behaves just like ash. Namely you can write
to the console, but it writes nothing back.
_lvnd_
(^_^)
-----------------------------------------------------------------------
Bu mesaj Karel MailScanner ile tehlikeli icerik ve virus kontrolunden gecirilmistir.
KAREL A.S. - Bilgi Teknolojileri Bolumu
This message has been scanned for viruses and dangerous content by Karel MailScanner, and is believed to be clean.
KAREL A.S. - Information Technologies Department
More information about the busybox
mailing list