buildroot/system/Config.in, branch 2016.02

system: Fix warning when selecting systemd and ensure merged /usr workarounds are enabled

2015-11-09T20:48:10+00:00

With systemd and a custom skeleton, we end up with the following warning: warning: (BR2_INIT_SYSTEMD) selects BR2_ROOTFS_MERGED_USR which has unmet direct dependencies (BR2_ROOTFS_SKELETON_DEFAULT) Which makes sense as the logic to install the symlinks to /usr is part of the default skeleton handling, but the BR2_ROOTFS_MERGED_USR symbol is ALSO used by packages to activate various workarounds for a merged /usr, so it should be always active when using systemd even with a custom rootfs skeleton (that by definition must use a merged /usr as required by systemd). So introduce a dummy symbol with the same name for the custom skeleton case, similar to how we handle the BR2_PACKAGE_BUSYBOX_SHOW_OTHERS option. This is a hidden option so it can only be activated by enabling systemd (and not if people just want to use a merged /usr with a custom skeleton but not systemd), but as this is really a legacy option that is probably good enough (if not, patches are welcome!). Signed-off-by: Peter Korsgaard

Revert "system: Fix warning when selecting systemd"

2015-11-09T20:40:32+00:00

This reverts commit b4718c3a28fc3b178253b24bd6fbb8540a724c7e. The BR2_ROOTFS_MERGED_USR symbol is used to activate various workarounds for a merged /usr by packages, so it should be active even with a custom rootfs skeleton. Signed-off-by: Peter Korsgaard

system: Fix warning when selecting systemd

2015-11-08T13:58:05+00:00

With systemd and a custom skeleton, you end up with the following warning: warning: (BR2_INIT_SYSTEMD) selects BR2_ROOTFS_MERGED_USR which has unmet direct dependencies (BR2_ROOTFS_SKELETON_DEFAULT) Signed-off-by: Maxime Hadjinlian Acked-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

system: add options for /bin /sbin and /lib to be symlinks into /usr

2015-10-14T20:50:03+00:00

systemd is increasingly expecting things to live in /usr/bin, /usr/sbin or /usr/lib nad not in /bin, /sbin or /lib. It has inherited those expectations from a Fedora change: https://fedoraproject.org/wiki/Features/UsrMove Note however, that systemd does support /usr being on a separate filesystem; it just expects an initramfs to mount it before the final switchroot over to the actual rootfs. But the traditional use-case for Buildroot is not to boot with an initramfs; although that is totally feasible, that's probably not what is commonly done in the vast majority of cases. However, a lot of packages still install stuff directly into /bin, /sbin or /lib, which systemd may need early-on in the boot process, even before it may have a chance to mount /usr. Even though we can tell systemd, at configure-time, where it should expect programs to be at runtime, it does not make sense to go head-first against an upstream wa^Hill. Add an option so that /bin, /sbin and /lib be symlinks to /usr/bin and /usr/sbin. That option is forcibly enabled when the init system is systemd. Note: we need not handle /lib32 or /lib64, as they already are symlinks to /lib, which means they will automatically be redirected to /usr/lib, as /usr/lib32 and /usr/lib64 already are. Furthermore, this means we're no longer supporting a split-usr setup, so the corresponding configure options have been removed as well for systemd and, when using a merged /usr, for eudev as well. In Buildroot, we decided (with this patch) not to support a split-usr when systemd is used as an init system. This is a design decision, not a systemd issue. Thus the select is with BR2_INIT_SYSTEMD rather than with BR2_PACKAGE_SYSTEMD. Signed-off-by: "Yann E. MORIN" Cc: Thomas Petazzoni Cc: Arnout Vandecappelle Cc: Mike Williams Cc: Vicente Olivert Riera Cc: Baruch Siach Tested-by: Mike Williams Signed-off-by: Thomas Petazzoni

system: clarify /dev management using devtmpfs + {mdev, eudev}

2015-10-04T10:23:14+00:00

The "Dynamic using mdev" and "Dynamic using eudev" /dev management methods are using devtmpfs, just like "Dynamic using devtmpfs only", on top of which they add either mdev or eudev. But their names might suggest they use mdev only or eudev only. Clarify their descriptions by adding "devtmpfs +" to make it unambiguous. [Thomas: rewrap the paragraphs in the manual. It makes the diff a lot less readable, but we actually want the result to be wrapped.] Signed-off-by: Luca Ceresoli Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

system: use a menuconfig for the getty options

2015-10-03T12:25:52+00:00

Making the getty option a menuconfig instead of a simple config automatically moves its dependees into a menu without the need to manually declare such a menu. Signed-off-by: "Yann E. MORIN" Acked-by: Arnout Vandecappelle (Essensium/Mind) Reviewed-by: Vicente Olivert Riera Tested-by: Vicente Olivert Riera Signed-off-by: Peter Korsgaard

system: make systemd's kernel headers comment fit

2015-09-10T20:06:55+00:00

The comment line that explains that systemd needs a glibc toolchain and kernel headers >= 3.10 doesn't fit in the dialog box, which makes it look as if headers >= 3.1 are needed. Abbreviate the comment a little by removing an 'an'. It still doesn't fit completely (only one trailing * is shown), but at least it's readable. While we're at it, change the quoting style to " like we always use. Reported-by: eschu on IRC Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Acked-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

initscripts: new package

2015-07-13T23:51:52+00:00

The folder init.d is currently installed by default since it's part of our skeleton. This patch creates a package out of it and make busybox/sysvinit depends on it. This way, if you chose another init, you don't end up with a useless init.d folder. [Thomas: - make the initscripts package selectable via a hidden bool - remove some unneeded changes in sysvinit.mk.] Signed-off-by: Maxime Hadjinlian Signed-off-by: Thomas Petazzoni

system: allow/disallow root login, accept encoded passwords

2015-07-04T10:46:43+00:00

Currently, there are only two possibilities regarding the root account: - it is enabled with no password (the default) - it is enabled, using a clear-text, user-provided password This is deemed insufficient in many cases, especially when the .config file has to be published (e.g. for the GPL compliance, or any other reason.). Fix that in two ways: - add a boolean option that allows/disallows root login altogether, which defaults to 'y' to keep backward compatibility; - accept already-encoded passwords, which we recognise as starting with either of $1$, $5$ or $6$ (resp. for md5, sha256 or sha512). Signed-off-by: Lorenzo M. Catucci [yann.morin.1998@free.fr: - don't add a choice to select between clear-text/encoded password, use a single prompt; - differentiate in the password hook itself; - rewrite parts of the help entry; - rewrite and expand the commit log ] Signed-off-by: Yann E. MORIN Cc: Thomas Petazzoni Cc: Arnout Vandecappelle Reviewed-by: Arnout Vandecappelle (Essensium/Mind) Tested-by: "Lorenzo M. Catucci" Acked-by: "Lorenzo M. Catucci" Tested-by: Gergely Imreh Signed-off-by: Thomas Petazzoni

system: make /bin/sh symlink use relative path

2015-06-21T07:36:00+00:00

The symlink created by buildroot for /bin/sh is the full path to a shell. This does not match what busybox and other Linux distributions do with using relative path symlinks. When handling files on the host system this will point to the host system's shell if present and not the target shell. This is fixed by changing the /bin/sh symlink to use a relative path. Fixes #8161. [Thomas: minor fixups to the commit log suggested by Yann E. Morin.] Signed-off-by: Matthew Starr Reviewed-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni