buildroot/system, branch 2016.05

system: add help entry to "none" init system

2016-05-28T08:58:34+00:00

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" Cc: Thomas Petazzoni Cc: Peter Korsgaard Signed-off-by: Thomas Petazzoni

skeleton: Recreate /var/run symlink

2016-02-11T22:20:38+00:00

It was the only one with a trailing slash, it's only for coherence's sake. Signed-off-by: Maxime Hadjinlian Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

skeleton: Rename /etc/profile.d/umask to umask.sh

2016-02-10T06:49:04+00:00

/etc/profile only sources files that matches the /etc/profile.d/*.sh pattern, so /etc/profile.d/umask was never sourced. Signed-off-by: Nicolas Cavallari Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

Makefile: drop ldconfig handling

2016-01-03T20:46:07+00:00

The ldconfig handling in the main Makefile is utterly broken, as it calls the build machine ldconfig to generate the ld.so.cache of the target. Unfortunately, the format of the ld.so.cache is architecture specific, and therefore the build machine ldconfig cannot be used as-is. This patch therefore simply drops using ldconfig entirely, and removes /etc/ld.so.conf.d/ from the target skeleton. The idea is that all libraries that should be loaded by the dynamic linker must be installed in paths where the dynamic linker searches them by default (typically /lib or /usr/lib). This might potentially break a few packages, but the only way to know is to actually stop handling ldconfig. In order to be notified of such cases, we add a check in target-finalize to verify that there is no /etc/ld.so.conf file as well as no /etc/ld.so.conf.d directory. Signed-off-by: Thomas Petazzoni Acked-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

Merge branch 'next'

2015-12-01T22:24:07+00:00

Signed-off-by: Peter Korsgaard

readline: install configuration file from package recipe

2015-11-17T21:19:15+00:00

/etc/inputrc is configuration file for readline. However, until now, it was provided by skeleton. This patch install /etc/inputrc from readline recipe. Signed-off-by: Jérôme Pouiller Acked-by: Gustavo Zacarias Signed-off-by: Thomas Petazzoni

skeleton: remove unused /etc/issue

2015-11-17T20:59:31+00:00

/etc/issue is managed with BR2_TARGET_GENERIC_ISSUE. In case BR2_TARGET_GENERIC_ISSUE is set (which is default), /etc/issue is overwritten. In case BR2_TARGET_GENERIC_ISSUE is not set, we don't want /etc/issue exist. Finaly, remove /etc/issue from skeleton. Signed-off-by: Jérôme Pouiller Reviewed-by: "Maxime Hadjinlian" Signed-off-by: Peter Korsgaard

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