summaryrefslogtreecommitdiff
path: root/docs/customize-busybox-config.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/customize-busybox-config.txt')
-rw-r--r--docs/customize-busybox-config.txt20
1 files changed, 20 insertions, 0 deletions
diff --git a/docs/customize-busybox-config.txt b/docs/customize-busybox-config.txt
new file mode 100644
index 000000000..dc1c7abaa
--- /dev/null
+++ b/docs/customize-busybox-config.txt
@@ -0,0 +1,20 @@
+// -*- mode:doc; -*-
+// vim: set syntax=asciidoc:
+
+[[busybox-custom]]
+Customizing the Busybox configuration
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+http://www.busybox.net/[Busybox] is very configurable, and you may
+want to customize it. You can just configure it via +Package selection+,
++Base System+, +Busybox Configuration+. The menu based busybox configuration
+is mostly integrated into OpenADK. There are some options, which are not
+available and not supported. If you need to, you can change the defaults
+in +package/busybox/config+ and regenerate your OpenADK configuration.
+
+A change in the busybox configuration will rebuild the busybox package. If you
+choose another implementation of f.e. tar, which is provided by default from
+busybox, tar in busybox will be deactivated and the package will be
+automatically rebuilded, so that your resulting firmware images or archives
+will only contain a single tar program. Obviosly just the one you have
+selected.