diff options
author | Waldemar Brodkorb <wbx@openadk.org> | 2014-03-16 19:51:41 +0100 |
---|---|---|
committer | Waldemar Brodkorb <wbx@openadk.org> | 2014-03-16 19:51:41 +0100 |
commit | 9d097a780c0ffe2c9dbe146046d5b68123c47708 (patch) | |
tree | bf05111572c2a996d0c911c2fe30075aab6de496 /docs/customize-rootfs.txt | |
parent | f6161af2d6f3e0ed683fe77450aa2f9fe9ec100b (diff) |
add OpenADK manual.
Diffstat (limited to 'docs/customize-rootfs.txt')
-rw-r--r-- | docs/customize-rootfs.txt | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/docs/customize-rootfs.txt b/docs/customize-rootfs.txt new file mode 100644 index 000000000..b21b82209 --- /dev/null +++ b/docs/customize-rootfs.txt @@ -0,0 +1,23 @@ +// -*- mode:doc; -*- +// vim: set syntax=asciidoc: + +[[rootfs-custom]] +Customizing the generated target filesystem +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Besides changing one or another configuration through +make menuconfig+, +there are is a way to customize the resulting target filesystem. + +Create a new directory called +extra+ in the top OpenADK directory. +Put there a tree of directories and files that will be copied directly +over the target filesystem (+root_*+) after everything is build, but +before the firmware images or archives are created. + +You can also point to another directory via: +--------------- + $ make extra=/foo/bar +--------------- + +You can start with the example configuration files from +root_*+. +The +extra+ directory will never be deleted by any clean target to avoid +loss of customized configuration data. |