path: root/system
diff options
authorGravatar Yann E. MORIN <yann.morin.1998@free.fr>2016-05-27 22:53:53 +0200
committerGravatar Thomas Petazzoni <thomas.petazzoni@free-electrons.com>2016-05-28 10:58:34 +0200
commit4d185e5ec51bd10ec2e895968e3e2454c7028ee8 (patch)
tree9565c4281716ecd20a33df9351802dfa6cb62bd3 /system
parent03fef14fb892a5fdec1863667a7ec2f448228ae8 (diff)
system: add help entry to "none" init system
It can be a little bit misleading to have no init system... Add a comment that states the user has to provide his own init system, either via a package or a rootfs overlay. It is expected that such a user will know what to provide, so we don't really need to specify that it should be /init or /sbin/init or any arbitrary executable pointed to by the kernel command line "init=..." or anything else... Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'system')
1 files changed, 4 insertions, 0 deletions
diff --git a/system/Config.in b/system/Config.in
index 2e14971ba7..9441467435 100644
--- a/system/Config.in
+++ b/system/Config.in
@@ -101,6 +101,10 @@ comment "systemd needs (e)glibc toolchain, headers >= 3.10"
config BR2_INIT_NONE
bool "None"
+ help
+ Buildroot will not install any init system. You will
+ have to provide your own, either with a new package
+ or with a rootfs-overlay.