From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] My own init. How?
Date: Thu, 21 Aug 2014 12:20:47 +0200 [thread overview]
Message-ID: <20140821102047.GD3891@free.fr> (raw)
In-Reply-To: <CAEzGmjCb2F_8vMuSkVYF5MNwKk-Qxt5Snx9pOJ-eozFpLz+Xuw@mail.gmail.com>
Lennart, All,
On 2014-08-21 10:37 +0200, Lennart Ramberg spake thusly:
> I built a system successfully and used grub-bios-setup;
> $ sudo ./output/host/usr/sbin/grub-bios-setup -b
> ./output/host/usr/lib/grub/i386-pc/boot.img -c ./output/images/grub.img -d
> . /dev/sdX
> I have disabled the 'Run a getty (login prompt) after boot.'
>
> When my targetsystem thus has booted, I get a blank line.
> Typing echoes to the display including pressing Enter giving a new blank
> line.
> That seems well, though I don't know what to expect to see from Busybox
> init.
>
> Now, I want to try my own init, a 'Hello, world'. Busybox FAQ says: '...
> boot your device with an "init=" argument pointing to your hello world
> program'.
> How do I do that?
You should pass this 'init=/path/to/your/hello-world' on the kernel
command line.
Since you're using grub, you need to edit output/target/boot/menu.lst .
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2014-08-21 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 8:37 [Buildroot] My own init. How? Lennart Ramberg
2014-08-21 10:20 ` Yann E. MORIN [this message]
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=20140821102047.GD3891@free.fr \
--to=yann.morin.1998@free.fr \
--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