From: Steven Woody <narkewoody@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Login exited
Date: Fri, 5 Sep 2008 15:38:31 +0800 [thread overview]
Message-ID: <ed4892840809050038j3d0be1edjca3226465afedfdb@mail.gmail.com> (raw)
In-Reply-To: <20080905010758.GA22747@cloud.net.au>
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://busybox.net/lists/buildroot/attachments/20080905/f48ba68a/attachment.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://busybox.net/lists/buildroot/attachments/20080905/f48ba68a/attachment-0001.obj
next prev parent reply other threads:[~2008-09-05 7:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 8:02 [Buildroot] Login exited Steven Woody
2008-09-02 0:47 ` Steven Woody
2008-09-02 6:24 ` Emil Kruper
2008-09-02 11:26 ` Steven Woody
2008-09-02 13:07 ` Hamish Moffatt
2008-09-02 15:09 ` Steven Woody
2008-09-02 15:10 ` Steven Woody
2008-09-03 1:00 ` Hamish Moffatt
2008-09-03 0:59 ` Hamish Moffatt
2008-09-03 3:55 ` Steven Woody
[not found] ` <200809031950.49148.vda.linux@googlemail.com>
2008-09-04 1:50 ` Steven Woody
2008-09-04 2:00 ` Hamish Moffatt
2008-09-04 5:34 ` Steven Woody
2008-09-04 14:29 ` Hamish Moffatt
2008-09-04 15:49 ` Steven Woody
2008-09-05 1:07 ` Hamish Moffatt
2008-09-05 7:38 ` Steven Woody [this message]
2008-09-05 13:09 ` Hamish Moffatt
2008-09-07 5:44 ` Steven Woody
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ed4892840809050038j3d0be1edjca3226465afedfdb@mail.gmail.com \
--to=narkewoody@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox