From: Geoff Thorpe <Geoff.Thorpe@freescale.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Problems starting /init
Date: Wed, 4 Jan 2006 18:20:10 -0500 [thread overview]
Message-ID: <200601041820.10133.Geoff.Thorpe@freescale.com> (raw)
In-Reply-To: <43BC542F.5040302@comcast.net>
On January 4, 2006 06:03 pm, David H. Lynch Jr. wrote:
[snip]
> starting a c "Hello World" application that uses glibc, fputs,
> printf, fwrite, to display a string - again works fine.
>
> But I can not get busybox to output a thing either run as /init or
> run as /bin/sh.
busybox tries to open the console device and does fairly extensive
surgery with the stdio descriptors. So your apps that assume fds
0,1,2 to be stdin/stdout/stderr are functioning fine, but busybox is
probably choking because it's opening/configuring the console
devices. I've worked through this with someone before when we wanted
busybox to just run with the existing fds - we eventually beat it
into submission but then ended up changing/replacing the console
driver instead and going back to vanilla busybox. If you take a look
through the busybox source, you should find the various
fork/dup/ctrl/exit gymnastics and with a little patience, you might
be able to hack around it. But it might be easier in the long run to
figure out where the opening/manipulation of /dev/console (or
whatever it's opening) is going wrong.
Sorry I can't help you further. Good luck.
Cheers,
Geoff
--
Geoff Thorpe
Freescale Semiconductor
next prev parent reply other threads:[~2006-01-04 23:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 15:19 Need help for Linux hangs jimmy liu
2005-12-08 16:05 ` Vitaly Bordug
2005-12-08 23:21 ` Wolfgang Denk
2005-12-08 23:19 ` Wolfgang Denk
2006-01-04 7:05 ` Problems starting /init David H. Lynch Jr.
[not found] ` <6AD9F6A5F6E096408F0B703773355A070E705B@CHN-SNR-MBX01.wipro.com>
2006-01-15 9:13 ` Problems starting /sbin/init David H. Lynch Jr.
2006-01-04 23:03 ` Problems starting /init David H. Lynch Jr.
2006-01-04 23:20 ` Geoff Thorpe [this message]
2006-01-04 23:19 ` RESEND:Problems " David H. Lynch Jr.
2006-01-09 18:45 ` Shawn Jin
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=200601041820.10133.Geoff.Thorpe@freescale.com \
--to=geoff.thorpe@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.