rpi/domo
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Bump buildroot to 2019.02

Browse Source
This commit is contained in:
NADAL Jean-Baptiste
2019-03-28 22:49:48 +01:00
parent 5598b1b762
commit 920d307141
5121 changed files with 78550 additions and 46132 deletions
Download Patch File Download Diff File Expand all files Collapse all files

169
bsp/buildroot/system/Config.in
View File

@@ -31,10 +31,6 @@ config BR2_ROOTFS_SKELETON_CUSTOM_PATH
help
Path to custom target skeleton.
# dummy config so merged /usr workarounds can also be activated for
# custom rootfs skeleton
config BR2_ROOTFS_MERGED_USR
endif
if BR2_ROOTFS_SKELETON_DEFAULT
@@ -61,40 +57,22 @@ endif
choice
bool "Passwords encoding"
default BR2_TARGET_GENERIC_PASSWD_MD5
default BR2_TARGET_GENERIC_PASSWD_SHA256
help
Choose the password encoding scheme to use when Buildroot
needs to encode a password (eg. the root password, below).
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.
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.
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.
Use SHA256 to encode passwords which is stronger than MD5.
config BR2_TARGET_GENERIC_PASSWD_SHA512
bool "sha-512"
help
Use SHA512 to encode passwords.
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.
Use SHA512 to encode passwords which is stronger than SHA256
endchoice # Passwd encoding
@@ -128,8 +106,6 @@ config BR2_INIT_SYSTEMD
bool "systemd"
depends on BR2_PACKAGE_SYSTEMD_ARCH_SUPPORTS
depends on BR2_TOOLCHAIN_USES_GLIBC
depends on BR2_USE_WCHAR
depends on BR2_TOOLCHAIN_HAS_THREADS
depends on BR2_TOOLCHAIN_HAS_SSP
depends on BR2_USE_MMU
depends on !BR2_STATIC_LIBS
@@ -137,9 +113,12 @@ config BR2_INIT_SYSTEMD
select BR2_ROOTFS_MERGED_USR
select BR2_PACKAGE_SYSTEMD
comment "systemd needs a glibc toolchain, headers >= 3.10"
depends on !(BR2_TOOLCHAIN_USES_GLIBC \
&& BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_10)
comment "systemd needs a glibc toolchain w/ SSP, headers >= 3.10"
depends on BR2_PACKAGE_SYSTEMD_ARCH_SUPPORTS
depends on BR2_USE_MMU
depends on !BR2_TOOLCHAIN_USES_GLIBC || \
!BR2_TOOLCHAIN_HAS_SSP || \
!BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_10
config BR2_INIT_NONE
bool "None"
@@ -209,8 +188,6 @@ config BR2_ROOTFS_DEVICE_TABLE_SUPPORTS_EXTENDED_ATTRIBUTES
help
Support extended attributes handling in device tables
if BR2_ROOTFS_SKELETON_DEFAULT
config BR2_ROOTFS_MERGED_USR
bool "Use symlinks to /usr for /bin, /sbin and /lib"
help
@@ -219,9 +196,11 @@ config BR2_ROOTFS_MERGED_USR
is the historical UNIX way. In this case, /usr can be a
filesystem on a partition separate from / .
If you say 'y' here, then /bin, /sbin and /lib will be symlinks
to their counterparts in /usr. In this case, /usr can not be a
separate filesystem.
If you say 'y' here, then /bin, /sbin and /lib will be
symlinks to their counterparts in /usr. In this case, /usr can
not be a separate filesystem.
if BR2_ROOTFS_SKELETON_DEFAULT
config BR2_TARGET_ENABLE_ROOT_LOGIN
bool "Enable root login with password"
@@ -230,10 +209,10 @@ config BR2_TARGET_ENABLE_ROOT_LOGIN
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.
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.
config BR2_TARGET_GENERIC_ROOT_PASSWD
string "Root password"
@@ -242,25 +221,28 @@ config BR2_TARGET_GENERIC_ROOT_PASSWD
help
Set the initial root password.
If set to empty (the default), then no root password will be set,
and root will need no password to log in.
If set to empty (the default), then no root password will be
set, and root will need no password to log in.
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.
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).
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).
WARNING! WARNING!
The password appears as-is in the .config file, and may appear
in the build log! Avoid using a valuable password if either the
.config file or the build log may be distributed, or at the
very least use a strong cryptographic hash for your password!
in the build log! Avoid using a valuable password if either
the .config file or the build log may be distributed, or at
the very least use a strong cryptographic hash for your
password!
choice
bool "/bin/sh"
@@ -375,10 +357,10 @@ config BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW
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.
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.
config BR2_SYSTEM_DHCP
@@ -391,14 +373,25 @@ config BR2_SYSTEM_DHCP
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.
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 needs ifupdown or busybox or networkd"
depends on !(BR2_PACKAGE_BUSYBOX || BR2_PACKAGE_IFUPDOWN || BR2_PACKAGE_SYSTEMD_NETWORKD)
endif # BR2_ROOTFS_SKELETON_DEFAULT
config BR2_SYSTEM_DEFAULT_PATH
string "Set the system's default PATH"
default "/bin:/sbin:/usr/bin:/usr/sbin"
help
Sets the system's default PATH. It is being used in
/etc/profile in the skeleton-init-common package and by some
daemons.
The default should work in most cases.
config BR2_ENABLE_LOCALE_PURGE
bool "Purge unwanted locales"
default y
@@ -468,18 +461,19 @@ config BR2_TARGET_TZ_ZONELIST
help
Space-separated list of time zones to compile.
The value "default" includes all commonly used time zones. Note
that this set consumes around 5.5M for glibc and 2.1M for uClibc.
The value "default" includes all commonly used time zones.
Note that this set consumes around 5.5M for glibc and 2.1M for
uClibc.
The full list is the list of files in the time zone database source,
not including the build and .tab files.
The full list is the list of files in the time zone database
source, not including the build and .tab files.
config BR2_TARGET_LOCALTIME
string "default local time"
default "Etc/UTC"
help
The time zone to install as the default local time, expressed as a
tzdata location, such as:
The time zone to install as the default local time, expressed
as a tzdata location, such as:
Etc/UTC (the default)
GMT
Europe/Paris
@@ -506,24 +500,24 @@ config BR2_ROOTFS_OVERLAY
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.
They are copied as-is into the rootfs, excluding files ending
with ~ and .git, .svn and .hg directories.
config BR2_ROOTFS_POST_BUILD_SCRIPT
string "Custom scripts to run before creating filesystem images"
default ""
help
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.
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.
This gives users the opportunity to do board-specific cleanups,
add-ons and the like, so the generated files can be used directly
without further processing.
This gives users the opportunity to do board-specific
cleanups, add-ons and the like, so the generated files can be
used directly without further processing.
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.
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.
config BR2_ROOTFS_POST_FAKEROOT_SCRIPT
string "Custom scripts to run inside the fakeroot environment"
@@ -548,8 +542,9 @@ config BR2_ROOTFS_POST_FAKEROOT_SCRIPT
to create arbitrary entries statically in /dev
- BR2_ROOTFS_DEVICE_TABLE
to set arbitrary permissions as well as extended attributes
(such as capabilities) on files and directories,
to set arbitrary permissions as well as extended
attributes (such as capabilities) on files and
directories,
- BR2_ROOTFS_USERS_TABLES:
to create arbitrary users and their home directories
@@ -581,16 +576,16 @@ config BR2_ROOTFS_POST_SCRIPT_ARGS
|| BR2_ROOTFS_POST_FAKEROOT_SCRIPT != "" \
|| BR2_ROOTFS_POST_IMAGE_SCRIPT != ""
help
Pass these additional arguments to each post-build or post-image
scripts.
Pass these additional arguments to each post-build or
post-image 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 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.
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.
endmenu

1
bsp/buildroot/system/skeleton/dev/fd Symbolic link
View File

@@ -0,0 +1 @@
../proc/self/fd

1
bsp/buildroot/system/skeleton/dev/stderr Symbolic link
View File

@@ -0,0 +1 @@
../proc/self/fd/2

1
bsp/buildroot/system/skeleton/dev/stdin Symbolic link
View File

@@ -0,0 +1 @@
../proc/self/fd/0

1
bsp/buildroot/system/skeleton/dev/stdout Symbolic link
View File

@@ -0,0 +1 @@
../proc/self/fd/1

2
bsp/buildroot/system/skeleton/etc/profile
View File

@@ -1,4 +1,4 @@
export PATH=/bin:/sbin:/usr/bin:/usr/sbin
export PATH=@PATH@
if [ "$PS1" ]; then
if [ "`id -u`" -eq 0 ]; then

4
bsp/buildroot/system/system.mk
View File

@@ -86,3 +86,7 @@ define SYSTEM_REMOUNT_ROOT_INITTAB
$(SED) '/^[^#].*-o remount,rw \/$$/s~^~#~' $(TARGET_DIR)/etc/inittab
endef
endif
ifeq ($(BR_BUILDING)$(BR2_SYSTEM_DEFAULT_PATH),y"")
$(error BR2_SYSTEM_DEFAULT_PATH can't be empty)
endif