All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian SCHWARZ <christian.schwarz@st.com>
To: buildroot@busybox.net
Subject: [Buildroot] link to busybox
Date: Tue, 06 May 2008 09:23:15 +0200	[thread overview]
Message-ID: <48200763.6090600@st.com> (raw)
In-Reply-To: <d6cda7730805052216v18ea7bd1l7681744d84d78b13@mail.gmail.com>

The respawn problem typically is not related to a specific shell, but 
either to a misconfiguration of the /etc files (especially rc.S) or, 
more probable, missing /dev/tty??
You might want to check those messages.
In my case, I had to add several special devices by hand, not added by 
buildroot (and I also replaced all the files in /etc with a single rc.S 
one, which resolved several other problems). The platform is an ARMv6 board.

cheers,
Christian

Thiago A. Corr?a wrote:
>>  I am using buildroot for an arm board.
>>
>>  Is it common to have all my executables as links to busybox?
> 
> Yes, that's how busybox works, it's a single binary file for all the
> tools, so it shares code and reduces total size.
> 
>>  The issue I am facing is that I am not able to get the shell prompt. It keeps on respawning the getty when I try to login.
>>
> 
> I don't use arms, but AVR32 instead. I had a similar issue a while
> back and it was something to do with bash, once I removed bash from
> the build, everything worked ok. You might want to try that.
> 
> Kind Regards,
>    Thiago A. Correa
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
> 

  reply	other threads:[~2008-05-06  7:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06  5:11 [Buildroot] link to busybox Tiju Jacob
2008-05-06  5:16 ` Thiago A. Corrêa
2008-05-06  7:23   ` Christian SCHWARZ [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-07  5:33 Tiju Jacob
2008-05-07  7:15 ` Christian SCHWARZ

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=48200763.6090600@st.com \
    --to=christian.schwarz@st.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 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.