diff options
| -rw-r--r-- | docs/manual/beyond-buildroot.txt | 38 | ||||
| -rw-r--r-- | docs/manual/manual.txt | 2 |
2 files changed, 40 insertions, 0 deletions
diff --git a/docs/manual/beyond-buildroot.txt b/docs/manual/beyond-buildroot.txt new file mode 100644 index 000000000..12ce78cc2 --- /dev/null +++ b/docs/manual/beyond-buildroot.txt @@ -0,0 +1,38 @@ +// -*- mode:doc; -*- + +Beyond Buildroot +================ + +Boot the generated images +------------------------- + +NFS boot +~~~~~~~~ + +To achieve NFS-boot, enable _tar root filesystem_ in the _Filesystem +images_ menu. + +After 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 +------------------- + +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. diff --git a/docs/manual/manual.txt b/docs/manual/manual.txt index a1ee68ad3..c34e0ca46 100644 --- a/docs/manual/manual.txt +++ b/docs/manual/manual.txt @@ -25,6 +25,8 @@ include::developer-guide.txt[] include::legal-notice.txt[] +include::beyond-buildroot.txt[] + include::get-involved.txt[] include::contribute.txt[] |