From: Ciro Santilli <ciro.santilli@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] manual: add QEMU demo to quick start
Date: Wed, 10 Oct 2018 08:50:21 +0100 [thread overview]
Message-ID: <20181010075021.749-1-ciro.santilli@gmail.com> (raw)
---
OK, me learning to ues crappy mailing lists now >:-), will this appear v2
on the same thread?
Your software is awesome, and many more people would see that if the
quickstart actually told them how to quickstart and see something happen ;-)
docs/manual/quickstart.txt | 36 +++++++++++++++++++++++++++++++-----
1 file changed, 31 insertions(+), 5 deletions(-)
diff --git a/docs/manual/quickstart.txt b/docs/manual/quickstart.txt
index 74158ae249..00afe09e6b 100644
--- a/docs/manual/quickstart.txt
+++ b/docs/manual/quickstart.txt
@@ -8,12 +8,38 @@ is no need to be root to configure and use Buildroot. By running all
commands as a regular user, you protect your system against packages
behaving badly during compilation and installation.
-The first step when using Buildroot is to create a configuration.
-Buildroot has a nice configuration tool similar to the one you can
-find in the http://www.kernel.org/[Linux kernel] or in
-http://www.busybox.net/[BusyBox].
+=== Try it out with QEMU
-From the buildroot directory, run
+If you just want to emulate a simple generic QEMU system to see
+Buildroot at work immediately, run from the buildroot directory:
+
+--------------------
+make qemu_x86_64_defconfig
+make BR2_JLEVEL="$(nproc)"
+qemu-system-x86_64 \
+ -M pc \
+ -kernel output/images/bzImage \
+ -drive file=output/images/rootfs.ext2,if=virtio,format=raw \
+ -append "root=/dev/vda" \
+ -net nic,model=virtio \
+ -net user
+--------------------
+
+Once QEMU boots, login with +root+, and you are now left inside a minimal
+BusyBox based Linux distribution.
+
+The initial build can take several minutes to a few hours since we download
+and compile GCC, the Linux kernel and other basic system components from
+source.
+
+The QEMU command to use is also documented at: +board/qemu/x86/readme.txt+
+
+=== Day-to-day workflow
+
+In your day-to-day workflow, the first step when using Buildroot is to
+create a custom configuration. Buildroot has a nice configuration tool
+similar to the one you can find in the http://www.kernel.org/[Linux kernel]
+or in http://www.busybox.net/[BusyBox]:
--------------------
$ make menuconfig
--
2.19.0
next reply other threads:[~2018-10-10 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 7:50 Ciro Santilli [this message]
2018-10-10 8:33 ` [Buildroot] [PATCH v2] manual: add QEMU demo to quick start Thomas Petazzoni
2018-10-10 14:13 ` Ciro Santilli
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=20181010075021.749-1-ciro.santilli@gmail.com \
--to=ciro.santilli@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