NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
eb56420674
kumquat-buildroot/system/Config.in

463 lines
14 KiB
Plaintext
Raw Normal View History

Re-add target/generic/Config.in options to menuconfig The options to customize the hostname, the banner and the serial port configuration are now inside a menu named 'System configuration'. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-12-05 21:52:44 +01:00
menu "System configuration"
buildroot: reinstate /etc/{hostname,issue} kconfig when using generic target These got lost in the recent cleanup, but are handy for minimal rootfs customization. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-09-30 21:53:22 +02:00
config BR2_TARGET_GENERIC_HOSTNAME
Config.in files: whitespace cleanup This patch fixes the following whitespace problems in Config.in files: - trailing whitespace - spaces instead of tabs for indentation - help text not indented with tab + 2 spaces Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-11-11 17:23:23 +01:00
string "System hostname"
default "buildroot"
help
Select system hostname to be stored in /etc/hostname.
buildroot: reinstate /etc/{hostname,issue} kconfig when using generic target These got lost in the recent cleanup, but are handy for minimal rootfs customization. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-09-30 21:53:22 +02:00
system: clarify issue/hostname settings A custom skeleton may include /etc/issue and/or /etc/hostname, in which case we do not want to override them. But those files could also be missing from the custom skeleton, or the user may want to override their content. Update the documentation to make it clear that the user can set these to the empty string to make buildroot not create/overwrite these files. [Peter: drop the different default values depending on skeleton] Signed-off-by: Sagaert Johan <sagaert.johan@skynet.be> [yann.morin.1998@free.fr: change from hiding it behind SKELETON_DEFAULT to use conditional default values; move below the skeleton choice; improve help entries] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-01-07 23:46:07 +01:00
Leave empty to not create /etc/hostname, or to keep the
one from a custom skeleton.
buildroot: reinstate /etc/{hostname,issue} kconfig when using generic target These got lost in the recent cleanup, but are handy for minimal rootfs customization. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-09-30 21:53:22 +02:00
config BR2_TARGET_GENERIC_ISSUE
Config.in files: whitespace cleanup This patch fixes the following whitespace problems in Config.in files: - trailing whitespace - spaces instead of tabs for indentation - help text not indented with tab + 2 spaces Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-11-11 17:23:23 +01:00
string "System banner"
default "Welcome to Buildroot"
help
Select system banner (/etc/issue) to be displayed at login.
buildroot: reinstate /etc/{hostname,issue} kconfig when using generic target These got lost in the recent cleanup, but are handy for minimal rootfs customization. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-09-30 21:53:22 +02:00
system: clarify issue/hostname settings A custom skeleton may include /etc/issue and/or /etc/hostname, in which case we do not want to override them. But those files could also be missing from the custom skeleton, or the user may want to override their content. Update the documentation to make it clear that the user can set these to the empty string to make buildroot not create/overwrite these files. [Peter: drop the different default values depending on skeleton] Signed-off-by: Sagaert Johan <sagaert.johan@skynet.be> [yann.morin.1998@free.fr: change from hiding it behind SKELETON_DEFAULT to use conditional default values; move below the skeleton choice; improve help entries] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-01-07 23:46:07 +01:00
Leave empty to not create /etc/issue, or to keep the
one from a custom skeleton.
target: add different methods to encode passwords Passwords can be encoded in different ways (from the weakest to the strongest): des, md5, sha-256, sha-512 Add a choice entry to select the method, defaulting to 'md5'. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Tested-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-01-05 05:52:03 +01:00
choice
bool "Passwords encoding"
default BR2_TARGET_GENERIC_PASSWD_MD5
help
Choose the password encoding scheme to use when Buildroot
needs to encode a password (eg. the root password, below).
system: remove trailing tabs in Config.in file Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-29 12:29:33 +02:00
target: add different methods to encode passwords Passwords can be encoded in different ways (from the weakest to the strongest): des, md5, sha-256, sha-512 Add a choice entry to select the method, defaulting to 'md5'. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Tested-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-01-05 05:52:03 +01:00
Note: this is used at build-time, and *not* at runtime.
config BR2_TARGET_GENERIC_PASSWD_MD5
bool "md5"
help
Use MD5 to encode passwords.
system: remove trailing tabs in Config.in file Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-29 12:29:33 +02:00
target: add different methods to encode passwords Passwords can be encoded in different ways (from the weakest to the strongest): des, md5, sha-256, sha-512 Add a choice entry to select the method, defaulting to 'md5'. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Tested-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-01-05 05:52:03 +01:00
The default. Wildly available, and pretty good.
Although pretty strong, MD5 is now an old hash function, and
suffers from some weaknesses, which makes it susceptible to
brute-force attacks.
config BR2_TARGET_GENERIC_PASSWD_SHA256
bool "sha-256"
help
Use SHA256 to encode passwords.
system: remove trailing tabs in Config.in file Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-29 12:29:33 +02:00
target: add different methods to encode passwords Passwords can be encoded in different ways (from the weakest to the strongest): des, md5, sha-256, sha-512 Add a choice entry to select the method, defaulting to 'md5'. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Tested-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-01-05 05:52:03 +01:00
Very strong, but not ubiquitous, although available in glibc
for some time now. Choose only if you are sure your C library
understands SHA256 passwords.
config BR2_TARGET_GENERIC_PASSWD_SHA512
bool "sha-512"
help
Use SHA512 to encode passwords.
system: remove trailing tabs in Config.in file Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-29 12:29:33 +02:00
target: add different methods to encode passwords Passwords can be encoded in different ways (from the weakest to the strongest): des, md5, sha-256, sha-512 Add a choice entry to select the method, defaulting to 'md5'. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Tested-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-01-05 05:52:03 +01:00
Extremely strong, but not ubiquitous, although available in glibc
for some time now. Choose only if you are sure your C library
understands SHA512 passwords.
endchoice # Passwd encoding
config BR2_TARGET_GENERIC_PASSWD_METHOD
string
default "md5" if BR2_TARGET_GENERIC_PASSWD_MD5
default "sha-256" if BR2_TARGET_GENERIC_PASSWD_SHA256
default "sha-512" if BR2_TARGET_GENERIC_PASSWD_SHA512
Rework of the init system Since we have now two uncompatible init systems, and we want only one of them at the same time in use in the rootfs, we need to select a particular init system. This patch also adds $(PKG)_INSTALL_INIT_SYSTEMD and $(PKG)_INSTALL_INIT_SYSV hooks that are called when the matching init systems are selected to install properly the init scripts of the package. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-07-28 09:21:20 +02:00
choice
prompt "Init system"
default BR2_INIT_BUSYBOX
config BR2_INIT_BUSYBOX
replace references to Busybox with BusyBox The correct capitalised form appears to be "BusyBox" rather than "Busybox"; fix all references to the latter form. (Most such references occur in the manual and in commentary in package makefiles.) Signed-off-by: Simon Dawson <spdawson@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-31 09:55:35 +02:00
bool "BusyBox"
Rework of the init system Since we have now two uncompatible init systems, and we want only one of them at the same time in use in the rootfs, we need to select a particular init system. This patch also adds $(PKG)_INSTALL_INIT_SYSTEMD and $(PKG)_INSTALL_INIT_SYSV hooks that are called when the matching init systems are selected to install properly the init scripts of the package. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-07-28 09:21:20 +02:00
select BR2_PACKAGE_BUSYBOX
initscripts: new package 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 <maxime.hadjinlian@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-13 23:00:08 +02:00
select BR2_PACKAGE_INITSCRIPTS
Rework of the init system Since we have now two uncompatible init systems, and we want only one of them at the same time in use in the rootfs, we need to select a particular init system. This patch also adds $(PKG)_INSTALL_INIT_SYSTEMD and $(PKG)_INSTALL_INIT_SYSV hooks that are called when the matching init systems are selected to install properly the init scripts of the package. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-07-28 09:21:20 +02:00
config BR2_INIT_SYSV
bool "systemV"
system: fix kconfig warning about BR2_PACKAGE_SYSVINIT Fixes: warning: (BR2_INIT_SYSV) selects BR2_PACKAGE_SYSVINIT which has unmet direct dependencies (BR2_PACKAGE_BUSYBOX_SHOW_OTHERS && BR2_INIT_SYSV) Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-01-13 23:31:20 +01:00
select BR2_PACKAGE_BUSYBOX_SHOW_OTHERS # sysvinit
initscripts: new package 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 <maxime.hadjinlian@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-13 23:00:08 +02:00
select BR2_PACKAGE_INITSCRIPTS
Rework of the init system Since we have now two uncompatible init systems, and we want only one of them at the same time in use in the rootfs, we need to select a particular init system. This patch also adds $(PKG)_INSTALL_INIT_SYSTEMD and $(PKG)_INSTALL_INIT_SYSV hooks that are called when the matching init systems are selected to install properly the init scripts of the package. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-07-28 09:21:20 +02:00
select BR2_PACKAGE_SYSVINIT
config BR2_INIT_SYSTEMD
bool "systemd"
systemd: enable build for supported architectures. Systemd only supports the architectures defined in src/shared/architecture.h. So via a new parameter named BR2_PACKAGE_SYSTEMD_ARCH_SUPPORTS, we enable the build of this package only for those architectures. Fixes http://autobuild.buildroot.net/results/bcc/bcce95eb0748505c0d62db21a6e420aae3c3181b/ Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-03-28 17:31:06 +01:00
depends on BR2_PACKAGE_SYSTEMD_ARCH_SUPPORTS
systemd: bump to v207 This patch bumps systemd to v207 but also declares it as a provider for the udev virtual package. Starting with systemd 183, udev has been merged into systemd. The udev daemon is now installed as /lib/systemd/systemd-udevd. This means that /dev management using udev is only available if systemd is chosen as init system. When configuring systemd, the following options are available: - activation of systemd-journal-gatewayd, to access the journal via HTTP. - activation of extra features like journal compression and sealing. Support for uClibc has also been removed because: - upstream has no interest in supporting uClibc. - using a shrinked libc brings no advantage, given the size of all the programs included in Systemd. So using glibc does not matter. Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr> Reviewed-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-02-07 14:21:34 +01:00
depends on BR2_TOOLCHAIN_USES_GLIBC
Rework of the init system Since we have now two uncompatible init systems, and we want only one of them at the same time in use in the rootfs, we need to select a particular init system. This patch also adds $(PKG)_INSTALL_INIT_SYSTEMD and $(PKG)_INSTALL_INIT_SYSV hooks that are called when the matching init systems are selected to install properly the init scripts of the package. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-07-28 09:21:20 +02:00
depends on BR2_USE_WCHAR
depends on BR2_TOOLCHAIN_HAS_THREADS
systemd: bump to v207 This patch bumps systemd to v207 but also declares it as a provider for the udev virtual package. Starting with systemd 183, udev has been merged into systemd. The udev daemon is now installed as /lib/systemd/systemd-udevd. This means that /dev management using udev is only available if systemd is chosen as init system. When configuring systemd, the following options are available: - activation of systemd-journal-gatewayd, to access the journal via HTTP. - activation of extra features like journal compression and sealing. Support for uClibc has also been removed because: - upstream has no interest in supporting uClibc. - using a shrinked libc brings no advantage, given the size of all the programs included in Systemd. So using glibc does not matter. Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr> Reviewed-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-02-07 14:21:34 +01:00
depends on BR2_TOOLCHAIN_HAS_SSP
dbus: uses fork(), requires MMU In order to solve http://autobuild.buildroot.org/results/34f6843137efda20626af72714c110280ec577d7/build-end.log, this patch makes the D-Bus package as well as all the packages that select the D-Bus package 'depends on BR2_USE_MMU'. In addition, for the specific case of gvfs, the missing BR2_TOOLCHAIN_HAS_THREADS dependency is added (threads are required by D-Bus, so they are also required by gvfs which selects D-Bus). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-17 13:24:08 +01:00
depends on BR2_USE_MMU
Rename BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS Since a while, the semantic of BR2_PREFER_STATIC_LIB has been changed from "prefer static libraries when possible" to "use only static libraries". The former semantic didn't make much sense, since the user had absolutely no control/idea of which package would use static libraries, and which packages would not. Therefore, for quite some time, we have been starting to enforce that BR2_PREFER_STATIC_LIB should really build everything with static libraries. As a consequence, this patch renames BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS, and adjust the Config.in option accordingly. This also helps preparing the addition of other options to select shared, shared+static or just static. Note that we have verified that this commit can be reproduced by simply doing a global rename of BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS plus adding BR2_PREFER_STATIC_LIB to Config.in.legacy. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
2014-12-03 22:41:29 +01:00
depends on !BR2_STATIC_LIBS
systemd: needs 3.10+ kernel headers Fixes: http://autobuild.buildroot.net/results/f51/f510014600bc7d1e3cf81ff53268d186c8b417b8/ http://autobuild.buildroot.net/results/278/278a60a1569eb57773945281b102a0495ff32775/ http://autobuild.buildroot.net/results/083/083f9579893185d93c591d171b39d8e068b21412/ http://autobuild.buildroot.net/results/03a/03a96697aa72b69546d61e56d1285bb50b0633d9/ And many more. Systemd needs NDA_PORT/VNI/IFINDEX from linux/neighbour.h, which were added in 3.10 (6681712d: vxlan: generalize forwarding tables). Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-04-05 11:15:00 +02:00
depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_10
Rework of the init system Since we have now two uncompatible init systems, and we want only one of them at the same time in use in the rootfs, we need to select a particular init system. This patch also adds $(PKG)_INSTALL_INIT_SYSTEMD and $(PKG)_INSTALL_INIT_SYSV hooks that are called when the matching init systems are selected to install properly the init scripts of the package. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-07-28 09:21:20 +02:00
select BR2_PACKAGE_SYSTEMD
systemd: needs 3.10+ kernel headers Fixes: http://autobuild.buildroot.net/results/f51/f510014600bc7d1e3cf81ff53268d186c8b417b8/ http://autobuild.buildroot.net/results/278/278a60a1569eb57773945281b102a0495ff32775/ http://autobuild.buildroot.net/results/083/083f9579893185d93c591d171b39d8e068b21412/ http://autobuild.buildroot.net/results/03a/03a96697aa72b69546d61e56d1285bb50b0633d9/ And many more. Systemd needs NDA_PORT/VNI/IFINDEX from linux/neighbour.h, which were added in 3.10 (6681712d: vxlan: generalize forwarding tables). Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-04-05 11:15:00 +02:00
comment 'systemd needs an (e)glibc toolchain, headers >= 3.10'
systemd: needs kernel headers >= 3.0 Systemd requires at least Linux headers 3.0 because it uses: - setns(2) syscall, introduced in 3.0. - IFLA_GROUP from if_link.h, introduced in 2.6.39. Fixes http://autobuild.buildroot.net/results/098/09866da023d527b3c228a98f1fde104e780e1883/ Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-03-24 14:09:28 +01:00
depends on !(BR2_TOOLCHAIN_USES_GLIBC \
systemd: needs 3.10+ kernel headers Fixes: http://autobuild.buildroot.net/results/f51/f510014600bc7d1e3cf81ff53268d186c8b417b8/ http://autobuild.buildroot.net/results/278/278a60a1569eb57773945281b102a0495ff32775/ http://autobuild.buildroot.net/results/083/083f9579893185d93c591d171b39d8e068b21412/ http://autobuild.buildroot.net/results/03a/03a96697aa72b69546d61e56d1285bb50b0633d9/ And many more. Systemd needs NDA_PORT/VNI/IFINDEX from linux/neighbour.h, which were added in 3.10 (6681712d: vxlan: generalize forwarding tables). Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-04-05 11:15:00 +02:00
&& BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_10)
Rework of the init system Since we have now two uncompatible init systems, and we want only one of them at the same time in use in the rootfs, we need to select a particular init system. This patch also adds $(PKG)_INSTALL_INIT_SYSTEMD and $(PKG)_INSTALL_INIT_SYSV hooks that are called when the matching init systems are selected to install properly the init scripts of the package. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-07-28 09:21:20 +02:00
system/init: add option for no init system Can be usefull if a local package provides an init procedure. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-08-13 01:53:49 +02:00
config BR2_INIT_NONE
bool "None"
Rework of the init system Since we have now two uncompatible init systems, and we want only one of them at the same time in use in the rootfs, we need to select a particular init system. This patch also adds $(PKG)_INSTALL_INIT_SYSTEMD and $(PKG)_INSTALL_INIT_SYSV hooks that are called when the matching init systems are selected to install properly the init scripts of the package. Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2012-07-28 09:21:20 +02:00
endchoice
system: move init system option above /dev management. The option to choose init system was below the one for /dev management. As Systemd forces the use of udev, it is logical to swap them. Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-11-06 16:34:34 +01:00
choice
systemd: bump to v207 This patch bumps systemd to v207 but also declares it as a provider for the udev virtual package. Starting with systemd 183, udev has been merged into systemd. The udev daemon is now installed as /lib/systemd/systemd-udevd. This means that /dev management using udev is only available if systemd is chosen as init system. When configuring systemd, the following options are available: - activation of systemd-journal-gatewayd, to access the journal via HTTP. - activation of extra features like journal compression and sealing. Support for uClibc has also been removed because: - upstream has no interest in supporting uClibc. - using a shrinked libc brings no advantage, given the size of all the programs included in Systemd. So using glibc does not matter. Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr> Reviewed-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-02-07 14:21:34 +01:00
prompt "/dev management" if !BR2_INIT_SYSTEMD
system: move init system option above /dev management. The option to choose init system was below the one for /dev management. As Systemd forces the use of udev, it is logical to swap them. Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-11-06 16:34:34 +01:00
default BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS
config BR2_ROOTFS_DEVICE_CREATION_STATIC
bool "Static using device table"
config BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_DEVTMPFS
bool "Dynamic using devtmpfs only"
config BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV
bool "Dynamic using mdev"
select BR2_PACKAGE_BUSYBOX
eudev: new package eudev is a userspace device management daemon. It is a standalone version, independent from systemd. It is a fork maintained by Gentoo. Features: - No extra configuration options are available: Gudev is build if libglib2 is selected. - No dependency on hwdata as the package uses its own hardware database (as does systemd). eudev 1.3 is in sync with systemd v207. [Peter: add BR2_USE_MMU dependency] Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-02-07 14:21:32 +01:00
config BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV
bool "Dynamic using eudev"
depends on BR2_USE_WCHAR
Rename BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS Since a while, the semantic of BR2_PREFER_STATIC_LIB has been changed from "prefer static libraries when possible" to "use only static libraries". The former semantic didn't make much sense, since the user had absolutely no control/idea of which package would use static libraries, and which packages would not. Therefore, for quite some time, we have been starting to enforce that BR2_PREFER_STATIC_LIB should really build everything with static libraries. As a consequence, this patch renames BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS, and adjust the Config.in option accordingly. This also helps preparing the addition of other options to select shared, shared+static or just static. Note that we have verified that this commit can be reproduced by simply doing a global rename of BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS plus adding BR2_PREFER_STATIC_LIB to Config.in.legacy. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
2014-12-03 22:41:29 +01:00
depends on !BR2_STATIC_LIBS
Merge branch 'next' Conflicts: Makefile package/dmraid/Config.in package/gdb/Config.in.host package/linux-headers/linux-headers.mk package/python/python.mk package/python3/python3.mk package/rt-tests/Config.in package/sdl/sdl.mk package/systemd/systemd-01-fix-getty-unit.patch package/systemd/systemd-02-fix-page-size.patch package/systemd/systemd-03-uclibc-fix.patch package/udev/Config.in package/udisks/Config.in package/vlc/vlc.mk system/Config.in Quite some merge conflicts, hopefully I didn't screw up anything. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-02-28 14:30:23 +01:00
depends on BR2_USE_MMU # eudev
eudev: new package eudev is a userspace device management daemon. It is a standalone version, independent from systemd. It is a fork maintained by Gentoo. Features: - No extra configuration options are available: Gudev is build if libglib2 is selected. - No dependency on hwdata as the package uses its own hardware database (as does systemd). eudev 1.3 is in sync with systemd v207. [Peter: add BR2_USE_MMU dependency] Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-02-07 14:21:32 +01:00
select BR2_PACKAGE_EUDEV
system: move init system option above /dev management. The option to choose init system was below the one for /dev management. As Systemd forces the use of udev, it is logical to swap them. Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-11-06 16:34:34 +01:00
system: drop largefile depends Drop the buildroot toolchain non-largefile support option since it's being removed. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-03-30 23:07:28 +02:00
comment "eudev needs a toolchain w/ wchar, dynamic library"
Merge branch 'next' Conflicts: Makefile package/dmraid/Config.in package/gdb/Config.in.host package/linux-headers/linux-headers.mk package/python/python.mk package/python3/python3.mk package/rt-tests/Config.in package/sdl/sdl.mk package/systemd/systemd-01-fix-getty-unit.patch package/systemd/systemd-02-fix-page-size.patch package/systemd/systemd-03-uclibc-fix.patch package/udev/Config.in package/udisks/Config.in package/vlc/vlc.mk system/Config.in Quite some merge conflicts, hopefully I didn't screw up anything. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-02-28 14:30:23 +01:00
depends on BR2_USE_MMU
system: drop largefile depends Drop the buildroot toolchain non-largefile support option since it's being removed. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-03-30 23:07:28 +02:00
depends on !BR2_USE_WCHAR || BR2_STATIC_LIBS
system: move init system option above /dev management. The option to choose init system was below the one for /dev management. As Systemd forces the use of udev, it is logical to swap them. Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-11-06 16:34:34 +01:00
endchoice
systemd: bump to v207 This patch bumps systemd to v207 but also declares it as a provider for the udev virtual package. Starting with systemd 183, udev has been merged into systemd. The udev daemon is now installed as /lib/systemd/systemd-udevd. This means that /dev management using udev is only available if systemd is chosen as init system. When configuring systemd, the following options are available: - activation of systemd-journal-gatewayd, to access the journal via HTTP. - activation of extra features like journal compression and sealing. Support for uClibc has also been removed because: - upstream has no interest in supporting uClibc. - using a shrinked libc brings no advantage, given the size of all the programs included in Systemd. So using glibc does not matter. Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr> Reviewed-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-02-07 14:21:34 +01:00
comment "/dev management using udev (from systemd)"
depends on BR2_INIT_SYSTEMD
Move rootfs content options under system configuration Instead of the current mix between system config and filesystem menus. At the same time rename 'Target filesystem options' menu to 'Filesystem images' as it now only contains options about image formats. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-12 23:37:35 +02:00
config BR2_ROOTFS_DEVICE_TABLE
System config: split static-dev device table setting into seperate option As discussed here: http://lists.busybox.net/pipermail/buildroot/2011-May/043251.html Add BR2_ROOTFS_STATIC_DEVICE_TABLE for the extra device table file(s) to create device nodes in /dev, rather than complicated logic in BR2_ROOTFS_DEVICE_TABLE, making it complicated to move between static and dynamic modes. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-07-25 00:09:33 +02:00
string "Path to the permission tables"
system: fixup default device table locations after system/ got added Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-04 13:00:25 +01:00
default "system/device_table.txt"
System config: split static-dev device table setting into seperate option As discussed here: http://lists.busybox.net/pipermail/buildroot/2011-May/043251.html Add BR2_ROOTFS_STATIC_DEVICE_TABLE for the extra device table file(s) to create device nodes in /dev, rather than complicated logic in BR2_ROOTFS_DEVICE_TABLE, making it complicated to move between static and dynamic modes. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-07-25 00:09:33 +02:00
help
Specify a space-separated list of permission table locations,
that will be passed to the makedevs utility to assign
correct owners and permissions on various files in the
target filesystem.
See package/makedevs/README for details on the usage and
syntax of these files.
config BR2_ROOTFS_STATIC_DEVICE_TABLE
Move rootfs content options under system configuration Instead of the current mix between system config and filesystem menus. At the same time rename 'Target filesystem options' menu to 'Filesystem images' as it now only contains options about image formats. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-12 23:37:35 +02:00
string "Path to the device tables"
system: fixup default device table locations after system/ got added Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-04 13:00:25 +01:00
default "system/device_table_dev.txt"
System config: split static-dev device table setting into seperate option As discussed here: http://lists.busybox.net/pipermail/buildroot/2011-May/043251.html Add BR2_ROOTFS_STATIC_DEVICE_TABLE for the extra device table file(s) to create device nodes in /dev, rather than complicated logic in BR2_ROOTFS_DEVICE_TABLE, making it complicated to move between static and dynamic modes. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-07-25 00:09:33 +02:00
depends on BR2_ROOTFS_DEVICE_CREATION_STATIC
Move rootfs content options under system configuration Instead of the current mix between system config and filesystem menus. At the same time rename 'Target filesystem options' menu to 'Filesystem images' as it now only contains options about image formats. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-12 23:37:35 +02:00
help
Specify a space-separated list of device table locations,
that will be passed to the makedevs utility to create all
System config: split static-dev device table setting into seperate option As discussed here: http://lists.busybox.net/pipermail/buildroot/2011-May/043251.html Add BR2_ROOTFS_STATIC_DEVICE_TABLE for the extra device table file(s) to create device nodes in /dev, rather than complicated logic in BR2_ROOTFS_DEVICE_TABLE, making it complicated to move between static and dynamic modes. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-07-25 00:09:33 +02:00
the special device files under /dev.
Move rootfs content options under system configuration Instead of the current mix between system config and filesystem menus. At the same time rename 'Target filesystem options' menu to 'Filesystem images' as it now only contains options about image formats. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-12 23:37:35 +02:00
See package/makedevs/README for details on the usage and
syntax of these files.
choice
prompt "Root FS skeleton"
config BR2_ROOTFS_SKELETON_DEFAULT
bool "default target skeleton"
help
Use default target skeleton
config BR2_ROOTFS_SKELETON_CUSTOM
bool "custom target skeleton"
help
Use custom target skeleton.
endchoice
if BR2_ROOTFS_SKELETON_CUSTOM
config BR2_ROOTFS_SKELETON_CUSTOM_PATH
string "custom target skeleton path"
New top-level directory: system This directory groups the following elements: * the default root filesystem skeleton * the default device tables * the Config.in options for system configuration (UART port for getty, system hostname, etc.) * the make rules to apply the system configuration options Even though the skeleton and device tables could have lived in fs/, it would have been strange to have the UART, system hostname and other related options into fs/. A new system/ directory makes more sense. As a consequence, this patch also removes target/Makefile.in, which has become useless in the process. [Peter: fixup TARGET_SKELETON settings / documentation to match] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Yann E. MORIN <yann.morin.1998@free.fr> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-03 09:27:58 +01:00
default "system/skeleton"
Move rootfs content options under system configuration Instead of the current mix between system config and filesystem menus. At the same time rename 'Target filesystem options' menu to 'Filesystem images' as it now only contains options about image formats. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-12 23:37:35 +02:00
help
system/Config.in: fix custom skeleton help text Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-02 07:08:40 +02:00
Path to custom target skeleton.
Move rootfs content options under system configuration Instead of the current mix between system config and filesystem menus. At the same time rename 'Target filesystem options' menu to 'Filesystem images' as it now only contains options about image formats. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-12 23:37:35 +02:00
endif
target/generic: only show getty port option if default skeleton is used The special marker in etc/inittab might not be present with a custom skeleton. At the same time make the option always active, remove the hardcoded tty1/tty2 gettys and reword the option description slightly. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-12 17:15:36 +02:00
if BR2_ROOTFS_SKELETON_DEFAULT
target/generic: add kconfig for serial getty config (port + baudrate) These are the settings people most often want to tweak for embedded boards, so add kconfig variables to make it easy to do.
2009-03-20 22:59:43 +01:00
system: allow/disallow root login, accept encoded passwords 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 <lorenzo@sancho.ccd.uniroma2.it> [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 <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Arnout Vandecappelle <arnout@mind.be> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Tested-by: "Lorenzo M. Catucci" <lorenzo@sancho.ccd.uniroma2.it> Acked-by: "Lorenzo M. Catucci" <lorenzo@sancho.ccd.uniroma2.it> Tested-by: Gergely Imreh <imrehg@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-02 22:00:05 +02:00
config BR2_TARGET_ENABLE_ROOT_LOGIN
bool "Enable root login with password"
default y
help
Allow root to log in with a password.
If not enabled, root will not be able to log in with a password.
However, if you have an ssh server and you add an ssh key, you
can still allow root to log in. Alternatively, you can use sudo
to become root.
system: set root password only for default skeleton In case one is using a custom skeleton, the root pasword might already be set in this case, and should not be overriden. Just ask for (and set) the root password only for the default skeleton. Reported-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-01-05 05:52:02 +01:00
config BR2_TARGET_GENERIC_ROOT_PASSWD
string "Root password"
default ""
system: allow/disallow root login, accept encoded passwords 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 <lorenzo@sancho.ccd.uniroma2.it> [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 <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Arnout Vandecappelle <arnout@mind.be> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Tested-by: "Lorenzo M. Catucci" <lorenzo@sancho.ccd.uniroma2.it> Acked-by: "Lorenzo M. Catucci" <lorenzo@sancho.ccd.uniroma2.it> Tested-by: Gergely Imreh <imrehg@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-02 22:00:05 +02:00
depends on BR2_TARGET_ENABLE_ROOT_LOGIN
system: set root password only for default skeleton In case one is using a custom skeleton, the root pasword might already be set in this case, and should not be overriden. Just ask for (and set) the root password only for the default skeleton. Reported-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-01-05 05:52:02 +01:00
help
system: allow/disallow root login, accept encoded passwords 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 <lorenzo@sancho.ccd.uniroma2.it> [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 <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Arnout Vandecappelle <arnout@mind.be> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Tested-by: "Lorenzo M. Catucci" <lorenzo@sancho.ccd.uniroma2.it> Acked-by: "Lorenzo M. Catucci" <lorenzo@sancho.ccd.uniroma2.it> Tested-by: Gergely Imreh <imrehg@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-02 22:00:05 +02:00
Set the initial root password.
system: remove trailing tabs in Config.in file Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-29 12:29:33 +02:00
system: set root password only for default skeleton In case one is using a custom skeleton, the root pasword might already be set in this case, and should not be overriden. Just ask for (and set) the root password only for the default skeleton. Reported-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-01-05 05:52:02 +01:00
If set to empty (the default), then no root password will be set,
and root will need no password to log in.
system: remove trailing tabs in Config.in file Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-29 12:29:33 +02:00
system: allow/disallow root login, accept encoded passwords 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 <lorenzo@sancho.ccd.uniroma2.it> [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 <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Arnout Vandecappelle <arnout@mind.be> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Tested-by: "Lorenzo M. Catucci" <lorenzo@sancho.ccd.uniroma2.it> Acked-by: "Lorenzo M. Catucci" <lorenzo@sancho.ccd.uniroma2.it> Tested-by: Gergely Imreh <imrehg@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-02 22:00:05 +02:00
If the password starts with any of $1$, $5$ or $6$, it is considered
to be already crypt-encoded with respectively md5, sha256 or sha512.
Any other value is taken to be a clear-text value, and is crypt-encoded
as per the "Passwords encoding" scheme, above.
Note: "$" signs in the hashed password must be doubled. For example,
if the hashed password is "$1$longsalt$v35DIIeMo4yUfI23yditq0",
then you must enter it as "$$1$$longsalt$$v35DIIeMo4yUfI23yditq0"
(this is necessary otherwise make would attempt to interpret the $
as a variable expansion).
system: remove trailing tabs in Config.in file Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-29 12:29:33 +02:00
system: set root password only for default skeleton In case one is using a custom skeleton, the root pasword might already be set in this case, and should not be overriden. Just ask for (and set) the root password only for the default skeleton. Reported-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-01-05 05:52:02 +01:00
WARNING! WARNING!
system: allow/disallow root login, accept encoded passwords 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 <lorenzo@sancho.ccd.uniroma2.it> [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 <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Arnout Vandecappelle <arnout@mind.be> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Tested-by: "Lorenzo M. Catucci" <lorenzo@sancho.ccd.uniroma2.it> Acked-by: "Lorenzo M. Catucci" <lorenzo@sancho.ccd.uniroma2.it> Tested-by: Gergely Imreh <imrehg@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-02 22:00:05 +02:00
The password appears as-is in the .config file, and may appear
system: set root password only for default skeleton In case one is using a custom skeleton, the root pasword might already be set in this case, and should not be overriden. Just ask for (and set) the root password only for the default skeleton. Reported-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-01-05 05:52:02 +01:00
in the build log! Avoid using a valuable password if either the
system: allow/disallow root login, accept encoded passwords 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 <lorenzo@sancho.ccd.uniroma2.it> [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 <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Arnout Vandecappelle <arnout@mind.be> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Tested-by: "Lorenzo M. Catucci" <lorenzo@sancho.ccd.uniroma2.it> Acked-by: "Lorenzo M. Catucci" <lorenzo@sancho.ccd.uniroma2.it> Tested-by: Gergely Imreh <imrehg@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-02 22:00:05 +02:00
.config file or the build log may be distributed, or at the
very least use a strong cryptographic hash for your password!
system: set root password only for default skeleton In case one is using a custom skeleton, the root pasword might already be set in this case, and should not be overriden. Just ask for (and set) the root password only for the default skeleton. Reported-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Peter Korsgaard <jacmet@uclibc.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-01-05 05:52:02 +01:00
system: add option to choose what /bin/sh points to Not all our shells do install a pointer to /bin/sh. Besides, between those that do and multiple ones are enabled, the last one to install wins the the symlink. Add a new config choice in the system sub-menu that allows the user to explicitly select the shell to provide /bin/sh. If busybox is not enabled, default to using dash, a POSIX shell. Remove the symlink creation from bash.mk at the same time. Note: for every shell, we select them, except busybox, on which we depend, on the assumption that we do not want to force busybox in case the user decided not to enable it. [Peter: remove redundant !BR2_PACKAGE_BUSYBOX dependency] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-10-12 15:36:22 +02:00
choice
bool "/bin/sh"
default BR2_SYSTEM_BIN_SH_DASH if !BR2_PACKAGE_BUSYBOX
help
Select which shell will provide /bin/sh.
# busybox has shells that work on noMMU
config BR2_SYSTEM_BIN_SH_BUSYBOX
bool "busybox' default shell"
depends on BR2_PACKAGE_BUSYBOX
config BR2_SYSTEM_BIN_SH_BASH
bool "bash"
depends on BR2_USE_MMU # bash
depends on BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
select BR2_PACKAGE_BASH
config BR2_SYSTEM_BIN_SH_DASH
bool "dash"
depends on BR2_USE_MMU # dash
depends on BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
select BR2_PACKAGE_DASH
config BR2_SYSTEM_BIN_SH_ZSH
bool "zsh"
depends on BR2_USE_MMU # zsh
depends on BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
select BR2_PACKAGE_ZSH
comment "bash, dash, zsh need BR2_PACKAGE_BUSYBOX_SHOW_OTHERS"
depends on !BR2_PACKAGE_BUSYBOX_SHOW_OTHERS && BR2_PACKAGE_BUSYBOX
config BR2_SYSTEM_BIN_SH_NONE
bool "none"
endchoice # /bin/sh
config BR2_SYSTEM_BIN_SH
string
system: make /bin/sh symlink use relative path 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 <mstarr@hedonline.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-06-16 22:42:28 +02:00
default "busybox" if BR2_SYSTEM_BIN_SH_BUSYBOX
default "bash" if BR2_SYSTEM_BIN_SH_BASH
default "dash" if BR2_SYSTEM_BIN_SH_DASH
default "zsh" if BR2_SYSTEM_BIN_SH_ZSH
system: add option to choose what /bin/sh points to Not all our shells do install a pointer to /bin/sh. Besides, between those that do and multiple ones are enabled, the last one to install wins the the symlink. Add a new config choice in the system sub-menu that allows the user to explicitly select the shell to provide /bin/sh. If busybox is not enabled, default to using dash, a POSIX shell. Remove the symlink creation from bash.mk at the same time. Note: for every shell, we select them, except busybox, on which we depend, on the assumption that we do not want to force busybox in case the user decided not to enable it. [Peter: remove redundant !BR2_PACKAGE_BUSYBOX dependency] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-10-12 15:36:22 +02:00
getty: Create specific getty config + cleanups This commit introduces a specific BR2_TARGET_GENERIC_GETTY configuration flag. This eliminates the need for checking if BR2_TARGET_GENERIC_GETTY_PORT is an empty string or not. It also allows hiding various getty options when getty isn't enabled. Signed-off-by: Assaf Inbal <shmuelzon@gmail.com> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-09-15 08:20:48 +02:00
config BR2_TARGET_GENERIC_GETTY
Config.in files: whitespace cleanup This patch fixes the following whitespace problems in Config.in files: - trailing whitespace - spaces instead of tabs for indentation - help text not indented with tab + 2 spaces Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-11-11 17:23:23 +01:00
bool "Run a getty (login prompt) after boot"
default y
getty: Create specific getty config + cleanups This commit introduces a specific BR2_TARGET_GENERIC_GETTY configuration flag. This eliminates the need for checking if BR2_TARGET_GENERIC_GETTY_PORT is an empty string or not. It also allows hiding various getty options when getty isn't enabled. Signed-off-by: Assaf Inbal <shmuelzon@gmail.com> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-09-15 08:20:48 +02:00
if BR2_TARGET_GENERIC_GETTY
menu "getty options"
target/generic: add kconfig for serial getty config (port + baudrate) These are the settings people most often want to tweak for embedded boards, so add kconfig variables to make it easy to do.
2009-03-20 22:59:43 +01:00
config BR2_TARGET_GENERIC_GETTY_PORT
getty: Create specific getty config + cleanups This commit introduces a specific BR2_TARGET_GENERIC_GETTY configuration flag. This eliminates the need for checking if BR2_TARGET_GENERIC_GETTY_PORT is an empty string or not. It also allows hiding various getty options when getty isn't enabled. Signed-off-by: Assaf Inbal <shmuelzon@gmail.com> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-09-15 08:20:48 +02:00
string "TTY port"
system: run getty on boot console by default We used to specify explicitly serial port with all its settings for init to instantiate getty. This limits usecases when the same one rootfs could be used. For example following cases won't work well with hardcoded serial console settings: * On the same board other serial port is expected to be used * The same rootfs is intended to be used on different boards with different serial ports (like ttySx vs ttyAMAx or even ttyx) With this change by default we rely on "console" specified in kernel's boot command line. What is important getty will be set on the last console specified in bootargs. For example is a kernel comand line: --->--- bootargs="... console=tty0 console=ttyS3,115200n8..." --->--- This now will instantiate serial console on ttyS3 but not on tty0. Tested with both Busybox and SysV init. Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-12-23 13:06:13 +01:00
default "console"
Free text field for serial port configuration BR2_TARGET_GENERIC_GETTY_PORT has now a string type instead of choice. This makes port configuration flexible and compact. Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-12-05 21:53:14 +01:00
help
getty: Create specific getty config + cleanups This commit introduces a specific BR2_TARGET_GENERIC_GETTY configuration flag. This eliminates the need for checking if BR2_TARGET_GENERIC_GETTY_PORT is an empty string or not. It also allows hiding various getty options when getty isn't enabled. Signed-off-by: Assaf Inbal <shmuelzon@gmail.com> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-09-15 08:20:48 +02:00
Specify a port to run a getty on.
target/generic: add kconfig for serial getty config (port + baudrate) These are the settings people most often want to tweak for embedded boards, so add kconfig variables to make it easy to do.
2009-03-20 22:59:43 +01:00
choice
getty: Create specific getty config + cleanups This commit introduces a specific BR2_TARGET_GENERIC_GETTY configuration flag. This eliminates the need for checking if BR2_TARGET_GENERIC_GETTY_PORT is an empty string or not. It also allows hiding various getty options when getty isn't enabled. Signed-off-by: Assaf Inbal <shmuelzon@gmail.com> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-09-15 08:20:48 +02:00
prompt "Baudrate"
system: run getty on boot console by default We used to specify explicitly serial port with all its settings for init to instantiate getty. This limits usecases when the same one rootfs could be used. For example following cases won't work well with hardcoded serial console settings: * On the same board other serial port is expected to be used * The same rootfs is intended to be used on different boards with different serial ports (like ttySx vs ttyAMAx or even ttyx) With this change by default we rely on "console" specified in kernel's boot command line. What is important getty will be set on the last console specified in bootargs. For example is a kernel comand line: --->--- bootargs="... console=tty0 console=ttyS3,115200n8..." --->--- This now will instantiate serial console on ttyS3 but not on tty0. Tested with both Busybox and SysV init. Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-12-23 13:06:13 +01:00
default BR2_TARGET_GENERIC_GETTY_BAUDRATE_KEEP
target/generic: add kconfig for serial getty config (port + baudrate) These are the settings people most often want to tweak for embedded boards, so add kconfig variables to make it easy to do.
2009-03-20 22:59:43 +01:00
help
Select a baudrate to use.
target/generic: support for busybox >= 1.14.x speed=0 handling
2009-04-15 15:42:12 +02:00
config BR2_TARGET_GENERIC_GETTY_BAUDRATE_KEEP
Config.in files: whitespace cleanup This patch fixes the following whitespace problems in Config.in files: - trailing whitespace - spaces instead of tabs for indentation - help text not indented with tab + 2 spaces Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-11-11 17:23:23 +01:00
bool "keep kernel default"
target/generic: add kconfig for serial getty config (port + baudrate) These are the settings people most often want to tweak for embedded boards, so add kconfig variables to make it easy to do.
2009-03-20 22:59:43 +01:00
config BR2_TARGET_GENERIC_GETTY_BAUDRATE_9600
bool "9600"
config BR2_TARGET_GENERIC_GETTY_BAUDRATE_19200
bool "19200"
config BR2_TARGET_GENERIC_GETTY_BAUDRATE_38400
bool "38400"
config BR2_TARGET_GENERIC_GETTY_BAUDRATE_57600
bool "57600"
config BR2_TARGET_GENERIC_GETTY_BAUDRATE_115200
bool "115200"
endchoice
config BR2_TARGET_GENERIC_GETTY_BAUDRATE
string
target/generic: support for busybox >= 1.14.x speed=0 handling
2009-04-15 15:42:12 +02:00
default "0" if BR2_TARGET_GENERIC_GETTY_BAUDRATE_KEEP
target/generic: add kconfig for serial getty config (port + baudrate) These are the settings people most often want to tweak for embedded boards, so add kconfig variables to make it easy to do.
2009-03-20 22:59:43 +01:00
default "9600" if BR2_TARGET_GENERIC_GETTY_BAUDRATE_9600
default "19200" if BR2_TARGET_GENERIC_GETTY_BAUDRATE_19200
default "38400" if BR2_TARGET_GENERIC_GETTY_BAUDRATE_38400
default "57600" if BR2_TARGET_GENERIC_GETTY_BAUDRATE_57600
default "115200" if BR2_TARGET_GENERIC_GETTY_BAUDRATE_115200
system: add option to configure TERM variable This option is useful for cases where the terminal isn't a bare serial vt100, but e.g. a linux tty with more features. Signed-off-by: Richard Braun <rbraun@sceen.net> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-12-13 01:28:11 +01:00
config BR2_TARGET_GENERIC_GETTY_TERM
getty: Create specific getty config + cleanups This commit introduces a specific BR2_TARGET_GENERIC_GETTY configuration flag. This eliminates the need for checking if BR2_TARGET_GENERIC_GETTY_PORT is an empty string or not. It also allows hiding various getty options when getty isn't enabled. Signed-off-by: Assaf Inbal <shmuelzon@gmail.com> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-09-15 08:20:48 +02:00
string "TERM environment variable"
system: add option to configure TERM variable This option is useful for cases where the terminal isn't a bare serial vt100, but e.g. a linux tty with more features. Signed-off-by: Richard Braun <rbraun@sceen.net> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-12-13 01:28:11 +01:00
default "vt100"
help
Specify a TERM type.
getty: add the ability to pass options to getty Signed-off-by: Assaf Inbal <shmuelzon@gmail.com> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-09-15 08:20:49 +02:00
config BR2_TARGET_GENERIC_GETTY_OPTIONS
string "other options to pass to getty"
default ""
help
Any other flags you want to pass to getty,
Refer to getty --help for details.
getty: Create specific getty config + cleanups This commit introduces a specific BR2_TARGET_GENERIC_GETTY configuration flag. This eliminates the need for checking if BR2_TARGET_GENERIC_GETTY_PORT is an empty string or not. It also allows hiding various getty options when getty isn't enabled. Signed-off-by: Assaf Inbal <shmuelzon@gmail.com> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-09-15 08:20:48 +02:00
endmenu
endif
system: add option to configure TERM variable This option is useful for cases where the terminal isn't a bare serial vt100, but e.g. a linux tty with more features. Signed-off-by: Richard Braun <rbraun@sceen.net> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-12-13 01:28:11 +01:00
system: move tz setup outside of default skeleton clause Allow time zone setup and installation for configurations using custom skeletons as well as default skeletons. Signed-off-by: Danomi Manchego <danomimanchego123@gmail.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-07-27 19:24:11 +02:00
config BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW
bool "remount root filesystem read-write during boot"
default y
help
The root filesystem is typically mounted read-only at boot.
By default, buildroot remounts it in read-write mode early during the
boot process.
Say no here if you would rather like your root filesystem to remain
read-only.
If unsure, say Y.
endif # BR2_ROOTFS_SKELETON_DEFAULT
Allow a single DHCP configuration via the system configuration submenu This patch allows the setup of simple a single interface to be automatically brought up and configured via DHCP on system startup. The interface name can be set via a configuration option. This patch does not support systemd-networkd, any complex network configuration should be done via overlay of /etc/network/interfaces or the relevant networkd configuration file [Peter: rename to BR2_SYSTEM_DHCP, tweak help text & implementation] Signed-off-by: Jérémy Rosen <jeremy.rosen@openwide.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-01-16 14:08:39 +01:00
config BR2_SYSTEM_DHCP
string "Network interface to configure through DHCP"
default ""
depends on !BR2_PACKAGE_SYSTEMD_NETWORKD && (BR2_PACKAGE_BUSYBOX || BR2_PACKAGE_IFUPDOWN)
help
Enter here the name of the network interface (E.G. eth0) to
automatically configure through DHCP at bootup.
If left empty, no automatic DHCP requests will take place.
For more complicated network setups use an overlay to overwrite
/etc/network/interfaces or add a networkd configuration file.
comment "automatic network configuration via DHCP is not compatible with networkd"
depends on BR2_PACKAGE_SYSTEMD_NETWORKD
comment "automatic network configuration via DHCP needs ifupdown or busybox"
depends on !(BR2_PACKAGE_BUSYBOX || BR2_PACKAGE_IFUPDOWN)
system: make the zoneinfo list a system option [Peter: move legacy options under 2014.05] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-04-07 21:58:03 +02:00
config BR2_TARGET_TZ_INFO
bool "Install timezone info"
system: allow setting the local timezone for uClibc Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-04-07 21:58:08 +02:00
# No timezone for musl; only for uClibc or (e)glibc.
depends on BR2_TOOLCHAIN_USES_GLIBC || BR2_TOOLCHAIN_USES_UCLIBC
select BR2_PACKAGE_TZDATA if BR2_TOOLCHAIN_USES_GLIBC
select BR2_PACKAGE_TZ if BR2_TOOLCHAIN_USES_UCLIBC
system: make the zoneinfo list a system option [Peter: move legacy options under 2014.05] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-04-07 21:58:03 +02:00
help
Say 'y' here to install timezone info.
if BR2_TARGET_TZ_INFO
config BR2_TARGET_TZ_ZONELIST
string "timezone list"
default "default"
help
Space-separated list of time zones to compile.
The value "default" includes all commonly used time zones. Note
system: allow setting the local timezone for uClibc Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-04-07 21:58:08 +02:00
that this set consumes around 5.5M for (e)glibc and 2.1M for uClibc.
system: make the zoneinfo list a system option [Peter: move legacy options under 2014.05] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-04-07 21:58:03 +02:00
The full list is the list of files in the time zone database source,
not including the build and .tab files.
system: add selection of a default localtime [Peter: strip quotes/use local TZDATA_LOCALTIME variable] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> [alexandre.belloni: move from "tzdata" to "system configuration"] Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com> [yann.morin.1998@free.fr: move into the BR2_TARGET_TZ_INFO conditionnal block] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-04-07 21:58:04 +02:00
config BR2_TARGET_LOCALTIME
string "default local time"
system: Defaulting TZ_LOCALTIME to UTC This patch sets the default timezone to UTC if not overwritten. Some packages need a configured system timezone for properly operating like mono based software. Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-02-12 14:49:31 +01:00
default "Etc/UTC"
system: add selection of a default localtime [Peter: strip quotes/use local TZDATA_LOCALTIME variable] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> [alexandre.belloni: move from "tzdata" to "system configuration"] Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com> [yann.morin.1998@free.fr: move into the BR2_TARGET_TZ_INFO conditionnal block] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-04-07 21:58:04 +02:00
help
The time zone to install as the default local time, expressed as a
tzdata location, such as:
GMT
Europe/Paris
America/New_York
Pacific/Wallis
...
If empty, no local time will be set, and the dates will be
expressed in UTC.
system: make the zoneinfo list a system option [Peter: move legacy options under 2014.05] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-04-07 21:58:03 +02:00
endif # BR2_TARGET_TZ_INFO
system: add ability to pass additional users tables. A new entry has been added to the "System Configuration" menu to allow the user to set the location of additional user tables (besides the ones defined in packages). A user table is a text file, formatted using the mkusers syntax, which describes the users on the target system, with their UID/GID, home directory, password, etc. The target root file system will be populated according the content of these files. Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr> [yann.morin.1998@free.fr: use plural TABLES; we need to remove the intermediate users_table file, as it is no longer generated in one shot, in case a previous run failed and did not remove it] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2014-04-20 19:33:09 +02:00
config BR2_ROOTFS_USERS_TABLES
string "Path to the users tables"
help
Specify a space-separated list of users table locations,
that will be passed to the mkusers utility to create
users on the system, with home directory, password, etc.
See manual for details on the usage and syntax of these files.
target/generic: add filesystem overlay option The filesystem overlay is a tree that is copied over the target fs after building everything - which is currently usually done in the post-build script. [Peter: don't ignore missing directories] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Acked-by: Luca Ceresoli <luca@lucaceresoli.net> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-02-05 08:16:00 +01:00
config BR2_ROOTFS_OVERLAY
string "Root filesystem overlay directories"
default ""
help
Specify a list of directories that are copied over the target
root filesystem after the build has finished and before it is
packed into the selected filesystem images.
They are copied as-is into the rootfs, excluding files ending with
~ and .git, .svn and .hg directories.
Move rootfs content options under system configuration Instead of the current mix between system config and filesystem menus. At the same time rename 'Target filesystem options' menu to 'Filesystem images' as it now only contains options about image formats. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-12 23:37:35 +02:00
config BR2_ROOTFS_POST_BUILD_SCRIPT
Adjust prompt for the post-build scripts option Since the post-image config option uses the plural for "Custom scripts", do the same for the post-build config option, for consistency. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Samuel Martin <s.martin49@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-02-07 12:58:48 +01:00
string "Custom scripts to run before creating filesystem images"
Move rootfs content options under system configuration Instead of the current mix between system config and filesystem menus. At the same time rename 'Target filesystem options' menu to 'Filesystem images' as it now only contains options about image formats. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-12 23:37:35 +02:00
default ""
help
Allow to run severals post build scripts instead of only one Using severals post build scripts is usefull to share script between severals boards/projects. [Peter: fix trailing spaces in Config.in] Signed-off-by: Philippe Reynes <philippe.reynes@sagemcom.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-17 13:01:22 +01:00
Specify a space-separated list of scripts to be run after the build
has finished and before Buildroot starts packing the files into
selected filesystem images.
Move rootfs content options under system configuration Instead of the current mix between system config and filesystem menus. At the same time rename 'Target filesystem options' menu to 'Filesystem images' as it now only contains options about image formats. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-12 23:37:35 +02:00
system: fix spelling errors Fix minor spelling errors that exists in system/Config.in Signed-off-by: Ryan Barnett <rjbarnet@rockwellcollins.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-02 00:26:36 +02:00
This gives users the opportunity to do board-specific cleanups,
Move rootfs content options under system configuration Instead of the current mix between system config and filesystem menus. At the same time rename 'Target filesystem options' menu to 'Filesystem images' as it now only contains options about image formats. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-12 23:37:35 +02:00
add-ons and the like, so the generated files can be used directly
without further processing.
system: add option to pass extra args to post-build and post-image scripts It can be useful to have different configuration use the same post-build and/or post-image scripts as they share a common infrastructure, but yet have minor differentiation. This option allows passing zero or more additional arguments to each post-build or post-image script. The same set of extra arguments are passed to all scripts, it is not possible to pass different arguments to each script. [Peter: fix help text, post-image gets called with the images dir] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-10 00:00:31 +02:00
These scripts are called with the target directory name as first
argument. Make sure the exit code of those scripts are 0, otherwise
make will stop after calling them.
Move rootfs content options under system configuration Instead of the current mix between system config and filesystem menus. At the same time rename 'Target filesystem options' menu to 'Filesystem images' as it now only contains options about image formats. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-05-12 23:37:35 +02:00
Add a post-image script mechanism Just like we have a post-build script mechanism that gets executed after the build of all packages but before the creation of the filesystem images, let's introduce a post-image script mechanism, that gets executed once all filesystem images have been generated. This can for example be used to call a tool building a firmware image from different images generated by Buildroot, or automatically extract the tarball root filesystem image into some location exported by NFS, or any other custom action. [Peter: fix image script check] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Acked-by: Luca Ceresoli <luca@lucaceresoli.net> Acked-by: Samuel Martin <s.martin49@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-02-07 12:58:43 +01:00
config BR2_ROOTFS_POST_IMAGE_SCRIPT
string "Custom scripts to run after creating filesystem images"
default ""
help
Specify a space-separated list of scripts to be run after
the build has finished and after Buildroot has packed the
files into selected filesystem images.
This can for example be used to call a tool building a
firmware image from different images generated by Buildroot,
or automatically extract the tarball root filesystem image
into some location exported by NFS, or any other custom
action.
These scripts are called with the images directory name as
system: add option to pass extra args to post-build and post-image scripts It can be useful to have different configuration use the same post-build and/or post-image scripts as they share a common infrastructure, but yet have minor differentiation. This option allows passing zero or more additional arguments to each post-build or post-image script. The same set of extra arguments are passed to all scripts, it is not possible to pass different arguments to each script. [Peter: fix help text, post-image gets called with the images dir] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-10 00:00:31 +02:00
first argument. The script is executed from the main Buildroot
source directory as the current directory.
config BR2_ROOTFS_POST_SCRIPT_ARGS
string "Extra post-{build,image} arguments"
depends on BR2_ROOTFS_POST_BUILD_SCRIPT != "" || BR2_ROOTFS_POST_IMAGE_SCRIPT != ""
help
system: fix spelling errors Fix minor spelling errors that exists in system/Config.in Signed-off-by: Ryan Barnett <rjbarnet@rockwellcollins.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-05-02 00:26:36 +02:00
Pass these additional arguments to each post-build or post-image
system: add option to pass extra args to post-build and post-image scripts It can be useful to have different configuration use the same post-build and/or post-image scripts as they share a common infrastructure, but yet have minor differentiation. This option allows passing zero or more additional arguments to each post-build or post-image script. The same set of extra arguments are passed to all scripts, it is not possible to pass different arguments to each script. [Peter: fix help text, post-image gets called with the images dir] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-07-10 00:00:31 +02:00
scripts.
Note that all the post-build and post-image scripts will be passed
the same set of arguments, you can not pass different arguments to
each script.
Note also, as stated in their respective help text, that the first
argument to each post-build or post-image script is the target
directory / images directory. The arguments in this option will be
passed *after* those.
Add a post-image script mechanism Just like we have a post-build script mechanism that gets executed after the build of all packages but before the creation of the filesystem images, let's introduce a post-image script mechanism, that gets executed once all filesystem images have been generated. This can for example be used to call a tool building a firmware image from different images generated by Buildroot, or automatically extract the tarball root filesystem image into some location exported by NFS, or any other custom action. [Peter: fix image script check] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Acked-by: Luca Ceresoli <luca@lucaceresoli.net> Acked-by: Samuel Martin <s.martin49@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-02-07 12:58:43 +01:00
Re-add target/generic/Config.in options to menuconfig The options to customize the hostname, the banner and the serial port configuration are now inside a menu named 'System configuration'. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-12-05 21:52:44 +01:00
endmenu
Reference in New Issue Copy Permalink