From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] No response after "Freeing init memory"
Date: Tue, 22 Feb 2011 19:25:38 +0100 [thread overview]
Message-ID: <20110222192538.6720529a@surf> (raw)
In-Reply-To: <AANLkTi=pxm_KCKqhFr0c7kMs_DU6m1wE49V5K6ShE=WQ@mail.gmail.com>
On Tue, 22 Feb 2011 09:06:34 +0100
Zden?k Materna <zdenek.materna@gmail.com> wrote:
> -------------- inittab ---------------------------------------------------
>
> # /etc/inittab
> #
> # This inittab is a basic inittab sample for sysvinit, which mimics
> # Buildroot's default inittab for Busybox.
Aah, you have enabled sysvinit. Could you disable it, make clean &&
make, and retry ?
Busybox already contains a default init, and it's the one most of us
test and use on a daily basis.
I've written this sysvinit inittab not long ago, it was working for me,
but it definitely does not receive as much testing as the sysvinit one
gets.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-02-22 18:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 20:53 [Buildroot] No response after "Freeing init memory" Zdeněk Materna
2011-02-21 20:57 ` Belisko Marek
2011-02-22 8:06 ` Zdeněk Materna
2011-02-22 18:25 ` Thomas Petazzoni [this message]
2011-02-22 19:04 ` ANDY KENNEDY
2011-02-23 10:50 ` Zdeněk Materna
2011-02-23 11:00 ` Zdeněk Materna
2011-02-23 15:23 ` Peter Korsgaard
2011-02-23 15:54 ` Zdeněk Materna
2011-02-23 16:38 ` ANDY KENNEDY
2011-02-23 17:05 ` Zdeněk Materna
2011-02-21 21:23 ` Charles Krinke
2011-02-21 21:27 ` Daniel Nyström
2011-02-21 22:21 ` Thomas Petazzoni
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=20110222192538.6720529a@surf \
--to=thomas.petazzoni@free-electrons.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