busybox: oops forgot the new Config.in file

1 files changed, 43 insertions, 0 deletions

diff --git a/package/busybox/config/klibc-utils/Config.in b/package/busybox/config/klibc-utils/Config.in
new file mode 100644
index 000000000..8121e605f
--- /dev/null
+++ b/package/busybox/config/klibc-utils/Config.in
@@ -0,0 +1,43 @@
+# DO NOT EDIT. This file is generated from Config.src
+#
+# For a description of the syntax of this configuration file,
+# see docs/Kconfig-language.txt.
+#
+
+menu "klibc-utils"
+
+config BUSYBOX_MINIPS
+	bool "minips (11 kb)"
+	default n  # for god's sake, just use "ps" name in your scripts
+	help
+	Alias to "ps".
+config BUSYBOX_NUKE
+	bool "nuke (2.9 kb)"
+	default y
+	help
+	Alias to "rm -rf".
+config BUSYBOX_RESUME
+	bool "resume (3.2 kb)"
+	default y
+	help
+	Resume from saved "suspend-to-disk" image
+config BUSYBOX_RUN_INIT
+	bool "run-init (7.7 kb)"
+	default y
+	select BUSYBOX_PLATFORM_LINUX
+	help
+	The run-init utility is used from initramfs to select a new
+	root device. Under initramfs, you have to use this instead of
+	pivot_root.
+
+	Booting with initramfs extracts a gzipped cpio archive into rootfs
+	(which is a variant of ramfs/tmpfs). Because rootfs can't be moved
+	or unmounted, pivot_root will not work from initramfs. Instead,
+	run-init deletes everything out of rootfs (including itself),
+	does a mount --move that overmounts rootfs with the new root, and
+	then execs the specified init program.
+
+	util-linux has a similar tool, switch-root.
+	run-init differs by also having a "-d CAPS_TO_DROP" option.
+
+endmenu