569db40574
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>
38 lines
1.0 KiB
Plaintext
38 lines
1.0 KiB
Plaintext
// -*- mode:doc; -*-
|
|
// vim: set syntax=asciidoc:
|
|
|
|
== Beyond Buildroot
|
|
|
|
=== Boot the generated images
|
|
|
|
==== NFS boot
|
|
|
|
To achieve NFS-boot, enable _tar root filesystem_ in the _Filesystem
|
|
images_ menu.
|
|
|
|
After a complete build, just run the following commands to setup the
|
|
NFS-root directory:
|
|
|
|
-------------------
|
|
sudo tar -xavf /path/to/output_dir/rootfs.tar -C /path/to/nfs_root_dir
|
|
-------------------
|
|
|
|
Remember to add this path to +/etc/exports+.
|
|
|
|
Then, you can execute a NFS-boot from your target.
|
|
|
|
=== Chroot
|
|
|
|
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.
|