2012-11-11 04:15:01 +01:00
|
|
|
// -*- mode:doc; -*-
|
2013-02-13 13:59:02 +01:00
|
|
|
// vim: set syntax=asciidoc:
|
2012-11-11 04:15:01 +01:00
|
|
|
|
manual: high-level restructuring
The structure of the buildroot manual is not always clear. There is a large
number of chapters, and some chapters seem to overlap. The distinction
between general usage and developer information is not always clear.
This patch restructures the manual into four large parts:
- getting started
- user guide
- developer guide
- appendix
Except for the names of these parts, the section names are not yet changed.
Content-wise there are no changes yet either. This will be handled in
subsequent patches.
In order to achieve the introduction of a new level 'parts' above
'chapters', the section indicators (=, ==, ===, ...) of several sections
have to be moved one level down. Additionally, the leveloffset indication to
asciidoc has to be removed. Finally, to maintain more or less the same level
of detail in the table of contents, the toc.section.depth attribute is
reduced as well. Note that for some sections, less detail is visible now.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-08-12 22:20:06 +02:00
|
|
|
== Beyond Buildroot
|
2012-11-11 04:15:01 +01:00
|
|
|
|
manual: high-level restructuring
The structure of the buildroot manual is not always clear. There is a large
number of chapters, and some chapters seem to overlap. The distinction
between general usage and developer information is not always clear.
This patch restructures the manual into four large parts:
- getting started
- user guide
- developer guide
- appendix
Except for the names of these parts, the section names are not yet changed.
Content-wise there are no changes yet either. This will be handled in
subsequent patches.
In order to achieve the introduction of a new level 'parts' above
'chapters', the section indicators (=, ==, ===, ...) of several sections
have to be moved one level down. Additionally, the leveloffset indication to
asciidoc has to be removed. Finally, to maintain more or less the same level
of detail in the table of contents, the toc.section.depth attribute is
reduced as well. Note that for some sections, less detail is visible now.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-08-12 22:20:06 +02:00
|
|
|
=== Boot the generated images
|
2012-11-11 04:15:01 +01:00
|
|
|
|
manual: high-level restructuring
The structure of the buildroot manual is not always clear. There is a large
number of chapters, and some chapters seem to overlap. The distinction
between general usage and developer information is not always clear.
This patch restructures the manual into four large parts:
- getting started
- user guide
- developer guide
- appendix
Except for the names of these parts, the section names are not yet changed.
Content-wise there are no changes yet either. This will be handled in
subsequent patches.
In order to achieve the introduction of a new level 'parts' above
'chapters', the section indicators (=, ==, ===, ...) of several sections
have to be moved one level down. Additionally, the leveloffset indication to
asciidoc has to be removed. Finally, to maintain more or less the same level
of detail in the table of contents, the toc.section.depth attribute is
reduced as well. Note that for some sections, less detail is visible now.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-08-12 22:20:06 +02:00
|
|
|
==== NFS boot
|
2012-11-11 04:15:01 +01:00
|
|
|
|
|
|
|
|
To achieve NFS-boot, enable _tar root filesystem_ in the _Filesystem
|
|
|
|
|
images_ menu.
|
|
|
|
|
|
2012-11-16 05:54:19 +01:00
|
|
|
After a complete build, just run the following commands to setup the
|
2012-11-11 04:15:01 +01:00
|
|
|
NFS-root directory:
|
|
|
|
|
|
|
|
|
|
-------------------
|
|
|
|
|
sudo tar -xavf /path/to/output_dir/rootfs.tar -C /path/to/nfs_root_dir
|
|
|
|
|
-------------------
|
|
|
|
|
|
2012-11-27 12:59:17 +01:00
|
|
|
Remember to add this path to +/etc/exports+.
|
|
|
|
|
|
2012-11-11 04:15:01 +01:00
|
|
|
Then, you can execute a NFS-boot from your target.
|
|
|
|
|
|
2015-01-19 20:52:57 +01:00
|
|
|
==== Live CD
|
|
|
|
|
|
|
|
|
|
To build a live CD image, enable the _iso image_ option in the
|
|
|
|
|
_Filesystem images_ menu. Note that this option is only available on
|
|
|
|
|
the x86 and x86-64 architectures, and if you are building your kernel
|
|
|
|
|
with Buildroot.
|
|
|
|
|
|
|
|
|
|
You can build a live CD image with either IsoLinux, Grub or Grub 2 as
|
|
|
|
|
a bootloader, but only Isolinux supports making this image usable both
|
|
|
|
|
as a live CD and live USB (through the _Build hybrid image_ option).
|
|
|
|
|
|
|
|
|
|
You can test your live CD image using QEMU:
|
|
|
|
|
|
|
|
|
|
-------------------
|
|
|
|
|
qemu-system-i386 -cdrom output/images/rootfs.iso9660
|
|
|
|
|
-------------------
|
|
|
|
|
|
2015-07-10 19:17:02 +02:00
|
|
|
Or use it as a hard-drive image if it is a hybrid ISO:
|
2015-01-19 20:52:57 +01:00
|
|
|
|
|
|
|
|
-------------------
|
|
|
|
|
qemu-system-i386 -hda output/images/rootfs.iso9660
|
|
|
|
|
-------------------
|
|
|
|
|
|
2015-07-10 19:17:02 +02:00
|
|
|
It can be easily flashed to a USB drive with +dd+:
|
2015-01-19 20:52:57 +01:00
|
|
|
|
|
|
|
|
-------------------
|
|
|
|
|
dd if=output/images/rootfs.iso9660 of=/dev/sdb
|
|
|
|
|
-------------------
|
|
|
|
|
|
manual: high-level restructuring
The structure of the buildroot manual is not always clear. There is a large
number of chapters, and some chapters seem to overlap. The distinction
between general usage and developer information is not always clear.
This patch restructures the manual into four large parts:
- getting started
- user guide
- developer guide
- appendix
Except for the names of these parts, the section names are not yet changed.
Content-wise there are no changes yet either. This will be handled in
subsequent patches.
In order to achieve the introduction of a new level 'parts' above
'chapters', the section indicators (=, ==, ===, ...) of several sections
have to be moved one level down. Additionally, the leveloffset indication to
asciidoc has to be removed. Finally, to maintain more or less the same level
of detail in the table of contents, the toc.section.depth attribute is
reduced as well. Note that for some sections, less detail is visible now.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-08-12 22:20:06 +02:00
|
|
|
=== Chroot
|
2012-11-11 04:15:01 +01:00
|
|
|
|
|
|
|
|
If you want to chroot in a generated image, then there are few thing
|
|
|
|
|
you should be aware of:
|
|
|
|
|
|
|
|
|
|
* you should setup the new root from the _tar root filesystem_ image;
|
|
|
|
|
|
|
|
|
|
* either the selected target architecture is compatible with your host
|
|
|
|
|
machine, or you should use some +qemu-*+ binary and correctly set it
|
|
|
|
|
within the +binfmt+ properties to be able to run the binaries built
|
|
|
|
|
for the target on your host machine;
|
|
|
|
|
|
|
|
|
|
* Buildroot does not currently provide +host-qemu+ and +binfmt+
|
|
|
|
|
correctly built and set for that kind of use.
|
