buildroot/system/Config.in, branch 2016.11

system: fix typo

2016-10-13T06:06:11+00:00

Signed-off-by: Matt Kraai Signed-off-by: Peter Korsgaard

add mksh to system shell choice

2016-10-01T21:22:18+00:00

Add mksh as a choice for system shells. Signed-off-by: Waldemar Brodkorb Signed-off-by: Peter Korsgaard

system: fix unmet dependencies

2016-09-11T13:45:24+00:00

Don't force remounting / read/write when using a customskeleton and systemd as init system, to fix the following unmet dependencies: warning: (BR2_INIT_SYSTEMD) selects BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW which has unmet direct dependencies (BR2_ROOTFS_SKELETON_DEFAULT) Signed-off-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

system: sysvinit needs MMU

2016-08-14T14:11:46+00:00

It uses spawn() and thus fork(), so it needs an MMU. Fixes a build issue reported on IRC for a cortex-m4 build: http://pastebin.com/dGCsy0sr Signed-off-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

system: zoneinfo usable by musl, too

2016-08-09T20:50:21+00:00

Currently, we limit installing zoneinfo to non-musl toolchain, by lack of knowledge on how it would work on musl. Turns out that musl uses the same zoneinfo format as glibc does. Make it possible to install the TZ info whatever the C library; for musl, use tzdata as for glibc. Thanks Rich! ;-) Signed-off-by: "Yann E. MORIN" Cc: Rich Felker Cc: Marc Khouri Signed-off-by: Thomas Petazzoni

system: move locale purging options to the "System configuration" menu

2016-08-03T19:17:21+00:00

The options to purge locales and to generate locale data are currently located in the toolchain menu. However, these options are not really related to the toolchain per-se, they are more system-level configuration options, much like the timezone selection option we already have in the "System configuration" menu. Therefore, it makes more sense to have the locale-related options in the "System configuration" menu as well. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

system: do not set hostname and issue for custom skeleton

2016-07-18T21:45:49+00:00

We expect the custom skeleton to be fully filled with the necessary files, now. There is definitely no reason we should handle setting the hostname and the issue file in there. A user using a custom skeleton should be fully responsible for providing a functional skeleton. Signed-off-by: "Yann E. MORIN" Reviewed-by: Romain Naour Signed-off-by: Thomas Petazzoni

system: do not handle network settings for custom skeleton

2016-07-18T21:45:34+00:00

We expect the custom skeleton to be fully filled with the necessary files, now. There is definitely no reason we should handle network settings in there. A user using a custom skeleton should be fully responsible for providing a functional skeleton. Signed-off-by: "Yann E. MORIN" Reviewed-by: Romain Naour Signed-off-by: Thomas Petazzoni

system: move the rootfs skeleton choice

2016-07-18T21:45:29+00:00

In the following commits, we'll be switching more options to be conditional on the default or custom skeleton. So, it makes sense that those options come after the choice of a skeleton. Signed-off-by: "Yann E. MORIN" Reviewed-by: Romain Naour Signed-off-by: Thomas Petazzoni

system: provide no default for custom skeleton path

2016-07-18T21:40:06+00:00

Being custom means that our default one is not suitable to start with. So there is no reason to offer it as the default path. Add a check that it is not empty. Add a separating empty line, for good measure, too. Signed-off-by: "Yann E. MORIN" Cc: Romain Naour Cc: Arnout Vandecappelle Reviewed-by: Romain Naour Signed-off-by: Thomas Petazzoni