[Buildroot] Login exited

Steven Woody narkewoody at gmail.com
Fri Sep 5 07:38:31 UTC 2008


Hi, All

I am now pretty sure that is the ash (as busybox applet) exited
somewhere in the function ash_main(...).  I got know this by inserted
many debug messages in the source of getty.c run_shell.c and ash.c.

And, I  attached my boot messages you for analysis, please check it
out. One file is for normal boot, another is for boot with
"init=/bin/sh". I will provide some other related information about my
build process, but because the message size limits for the list. I
have to post them in many other successive messages. Please check them
out too.

PS.  I just noticed, there is an error line when I run 'make' to get
my rootfs image, it is:
 ...
 rootdir=/root/buildroot/project_build_arm/uclibc/root
 table='target/generic/mini_device_table.txt'
 /root/buildroot/build_arm/cramfs-1.1/mkcramfs: invalid option -- l
 rm -f /root/buildroot/project_build_arm/uclibc/.fakeroot*

I checked, there is no a -l option for mkcramfs, but the buildroot
does try to use it.  Anyway, the cramfs is created successfully, but I
am not sure it is not a problem.



Regards,
narke
-------------- next part --------------
A non-text attachment was scrubbed...
Name: boot-msg.log
Type: application/octet-stream
Size: 4847 bytes
Desc: not available
Url : http://lists.busybox.net/pipermail/buildroot/attachments/20080905/f48ba68a/attachment-0004.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: boot-msg-with-init=bin-sh.log
Type: application/octet-stream
Size: 4588 bytes
Desc: not available
Url : http://lists.busybox.net/pipermail/buildroot/attachments/20080905/f48ba68a/attachment-0005.obj 


More information about the buildroot mailing list