2010-12-05 21:52:44 +01:00
|
|
|
menu "System configuration"
|
2009-09-30 21:53:22 +02:00
|
|
|
|
2016-07-17 10:44:26 +02:00
|
|
|
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"
|
|
|
|
|
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
|
|
|
|
|
|
2016-07-17 10:44:28 +02:00
|
|
|
if BR2_ROOTFS_SKELETON_DEFAULT
|
|
|
|
|
|
2009-09-30 21:53:22 +02:00
|
|
|
config BR2_TARGET_GENERIC_HOSTNAME
|
2013-11-11 17:23:23 +01:00
|
|
|
string "System hostname"
|
|
|
|
|
default "buildroot"
|
|
|
|
|
help
|
|
|
|
|
Select system hostname to be stored in /etc/hostname.
|
2009-09-30 21:53:22 +02:00
|
|
|
|
2014-01-07 23:46:07 +01:00
|
|
|
Leave empty to not create /etc/hostname, or to keep the
|
|
|
|
|
one from a custom skeleton.
|
|
|
|
|
|
2009-09-30 21:53:22 +02:00
|
|
|
config BR2_TARGET_GENERIC_ISSUE
|
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.
|
2009-09-30 21:53:22 +02:00
|
|
|
|
2014-01-07 23:46:07 +01:00
|
|
|
Leave empty to not create /etc/issue, or to keep the
|
|
|
|
|
one from a custom skeleton.
|
|
|
|
|
|
2016-07-17 10:44:28 +02:00
|
|
|
endif
|
|
|
|
|
|
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).
|
2013-04-29 12:29:33 +02:00
|
|
|
|
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.
|
2013-04-29 12:29:33 +02:00
|
|
|
|
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.
|
2013-04-29 12:29:33 +02:00
|
|
|
|
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.
|
2013-04-29 12:29:33 +02:00
|
|
|
|
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
|
|
|
|
|
|
2012-07-28 09:21:20 +02:00
|
|
|
choice
|
|
|
|
|
prompt "Init system"
|
|
|
|
|
default BR2_INIT_BUSYBOX
|
|
|
|
|
|
|
|
|
|
config BR2_INIT_BUSYBOX
|
2014-05-31 09:55:35 +02:00
|
|
|
bool "BusyBox"
|
2012-07-28 09:21:20 +02:00
|
|
|
select BR2_PACKAGE_BUSYBOX
|
2015-07-13 23:00:08 +02:00
|
|
|
select BR2_PACKAGE_INITSCRIPTS
|
2012-07-28 09:21:20 +02:00
|
|
|
|
|
|
|
|
config BR2_INIT_SYSV
|
|
|
|
|
bool "systemV"
|
2016-08-13 18:57:21 +02:00
|
|
|
depends on BR2_USE_MMU # sysvinit
|
2014-01-13 23:31:20 +01:00
|
|
|
select BR2_PACKAGE_BUSYBOX_SHOW_OTHERS # sysvinit
|
2015-07-13 23:00:08 +02:00
|
|
|
select BR2_PACKAGE_INITSCRIPTS
|
2012-07-28 09:21:20 +02:00
|
|
|
select BR2_PACKAGE_SYSVINIT
|
|
|
|
|
|
system: add options for /bin /sbin and /lib to be symlinks into /usr
systemd is increasingly expecting things to live in /usr/bin, /usr/sbin
or /usr/lib nad not in /bin, /sbin or /lib. It has inherited those
expectations from a Fedora change:
https://fedoraproject.org/wiki/Features/UsrMove
Note however, that systemd does support /usr being on a separate
filesystem; it just expects an initramfs to mount it before the final
switchroot over to the actual rootfs.
But the traditional use-case for Buildroot is not to boot with an
initramfs; although that is totally feasible, that's probably not what
is commonly done in the vast majority of cases.
However, a lot of packages still install stuff directly into /bin,
/sbin or /lib, which systemd may need early-on in the boot process,
even before it may have a chance to mount /usr. Even though we can
tell systemd, at configure-time, where it should expect programs to
be at runtime, it does not make sense to go head-first against an
upstream wa^Hill.
Add an option so that /bin, /sbin and /lib be symlinks to /usr/bin
and /usr/sbin. That option is forcibly enabled when the init system
is systemd.
Note: we need not handle /lib32 or /lib64, as they already are symlinks
to /lib, which means they will automatically be redirected to /usr/lib,
as /usr/lib32 and /usr/lib64 already are.
Furthermore, this means we're no longer supporting a split-usr setup, so
the corresponding configure options have been removed as well for
systemd and, when using a merged /usr, for eudev as well.
In Buildroot, we decided (with this patch) not to support a split-usr
when systemd is used as an init system. This is a design decision, not
a systemd issue. Thus the select is with BR2_INIT_SYSTEMD rather than
with BR2_PACKAGE_SYSTEMD.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Mike Williams <mike@mikebwilliams.com>
Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Cc: Baruch Siach <baruch@tkos.co.il>
Tested-by: Mike Williams <mike@mikebwilliams.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-09-04 22:17:32 +02:00
|
|
|
# In Buildroot, we decided not to support a split-usr when systemd is
|
|
|
|
|
# used as an init system. This is a design decision, not a systemd
|
|
|
|
|
# issue. Thus the select is with BR2_INIT_SYSTEMD (below) rather than
|
|
|
|
|
# with BR2_PACKAGE_SYSTEMD.
|
2012-07-28 09:21:20 +02:00
|
|
|
config BR2_INIT_SYSTEMD
|
|
|
|
|
bool "systemd"
|
2014-03-28 17:31:06 +01:00
|
|
|
depends on BR2_PACKAGE_SYSTEMD_ARCH_SUPPORTS
|
2014-02-07 14:21:34 +01:00
|
|
|
depends on BR2_TOOLCHAIN_USES_GLIBC
|
2012-07-28 09:21:20 +02:00
|
|
|
depends on BR2_USE_WCHAR
|
|
|
|
|
depends on BR2_TOOLCHAIN_HAS_THREADS
|
2014-02-07 14:21:34 +01:00
|
|
|
depends on BR2_TOOLCHAIN_HAS_SSP
|
2012-11-17 13:24:08 +01:00
|
|
|
depends on BR2_USE_MMU
|
2014-12-03 22:41:29 +01:00
|
|
|
depends on !BR2_STATIC_LIBS
|
2015-04-05 11:15:00 +02:00
|
|
|
depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_10
|
2015-11-09 21:40:32 +01:00
|
|
|
select BR2_ROOTFS_MERGED_USR
|
2012-07-28 09:21:20 +02:00
|
|
|
select BR2_PACKAGE_SYSTEMD
|
2016-09-11 14:38:55 +02:00
|
|
|
select BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW if BR2_ROOTFS_SKELETON_DEFAULT
|
2012-07-28 09:21:20 +02:00
|
|
|
|
2016-06-08 23:40:54 +02:00
|
|
|
comment "systemd needs a glibc toolchain, headers >= 3.10"
|
2014-03-24 14:09:28 +01:00
|
|
|
depends on !(BR2_TOOLCHAIN_USES_GLIBC \
|
2015-04-05 11:15:00 +02:00
|
|
|
&& BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_10)
|
2012-07-28 09:21:20 +02:00
|
|
|
|
2012-08-13 01:53:49 +02:00
|
|
|
config BR2_INIT_NONE
|
|
|
|
|
bool "None"
|
2016-05-27 22:53:53 +02:00
|
|
|
help
|
|
|
|
|
Buildroot will not install any init system. You will
|
|
|
|
|
have to provide your own, either with a new package
|
|
|
|
|
or with a rootfs-overlay.
|
2012-08-13 01:53:49 +02:00
|
|
|
|
2012-07-28 09:21:20 +02:00
|
|
|
endchoice
|
|
|
|
|
|
2013-11-06 16:34:34 +01:00
|
|
|
choice
|
2014-02-07 14:21:34 +01:00
|
|
|
prompt "/dev management" if !BR2_INIT_SYSTEMD
|
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
|
2015-10-04 11:43:35 +02:00
|
|
|
bool "Dynamic using devtmpfs + mdev"
|
2013-11-06 16:34:34 +01:00
|
|
|
select BR2_PACKAGE_BUSYBOX
|
|
|
|
|
|
2014-02-07 14:21:32 +01:00
|
|
|
config BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV
|
2015-10-04 11:43:35 +02:00
|
|
|
bool "Dynamic using devtmpfs + eudev"
|
2016-12-26 16:22:35 +01:00
|
|
|
depends on BR2_USE_WCHAR # eudev
|
2014-12-03 22:41:29 +01:00
|
|
|
depends on !BR2_STATIC_LIBS
|
2014-02-28 14:30:23 +01:00
|
|
|
depends on BR2_USE_MMU # eudev
|
2014-02-07 14:21:32 +01:00
|
|
|
select BR2_PACKAGE_EUDEV
|
2013-11-06 16:34:34 +01:00
|
|
|
|
2015-03-30 23:07:28 +02:00
|
|
|
comment "eudev needs a toolchain w/ wchar, dynamic library"
|
2014-02-28 14:30:23 +01:00
|
|
|
depends on BR2_USE_MMU
|
2015-03-30 23:07:28 +02:00
|
|
|
depends on !BR2_USE_WCHAR || BR2_STATIC_LIBS
|
2013-11-06 16:34:34 +01:00
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2014-02-07 14:21:34 +01:00
|
|
|
comment "/dev management using udev (from systemd)"
|
|
|
|
|
depends on BR2_INIT_SYSTEMD
|
|
|
|
|
|
2011-05-12 23:37:35 +02:00
|
|
|
config BR2_ROOTFS_DEVICE_TABLE
|
2011-07-25 00:09:33 +02:00
|
|
|
string "Path to the permission tables"
|
2012-11-04 13:00:25 +01:00
|
|
|
default "system/device_table.txt"
|
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
|
2011-05-12 23:37:35 +02:00
|
|
|
string "Path to the device tables"
|
2012-11-04 13:00:25 +01:00
|
|
|
default "system/device_table_dev.txt"
|
2011-07-25 00:09:33 +02:00
|
|
|
depends on BR2_ROOTFS_DEVICE_CREATION_STATIC
|
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
|
2011-07-25 00:09:33 +02:00
|
|
|
the special device files under /dev.
|
2011-05-12 23:37:35 +02:00
|
|
|
|
|
|
|
|
See package/makedevs/README for details on the usage and
|
|
|
|
|
syntax of these files.
|
|
|
|
|
|
2016-06-29 17:19:44 +02:00
|
|
|
config BR2_ROOTFS_DEVICE_TABLE_SUPPORTS_EXTENDED_ATTRIBUTES
|
|
|
|
|
bool "support extended attributes in device tables"
|
|
|
|
|
help
|
|
|
|
|
Support extended attributes handling in device tables
|
|
|
|
|
|
2011-05-12 17:15:36 +02:00
|
|
|
if BR2_ROOTFS_SKELETON_DEFAULT
|
2009-03-20 22:59:43 +01:00
|
|
|
|
system: add options for /bin /sbin and /lib to be symlinks into /usr
systemd is increasingly expecting things to live in /usr/bin, /usr/sbin
or /usr/lib nad not in /bin, /sbin or /lib. It has inherited those
expectations from a Fedora change:
https://fedoraproject.org/wiki/Features/UsrMove
Note however, that systemd does support /usr being on a separate
filesystem; it just expects an initramfs to mount it before the final
switchroot over to the actual rootfs.
But the traditional use-case for Buildroot is not to boot with an
initramfs; although that is totally feasible, that's probably not what
is commonly done in the vast majority of cases.
However, a lot of packages still install stuff directly into /bin,
/sbin or /lib, which systemd may need early-on in the boot process,
even before it may have a chance to mount /usr. Even though we can
tell systemd, at configure-time, where it should expect programs to
be at runtime, it does not make sense to go head-first against an
upstream wa^Hill.
Add an option so that /bin, /sbin and /lib be symlinks to /usr/bin
and /usr/sbin. That option is forcibly enabled when the init system
is systemd.
Note: we need not handle /lib32 or /lib64, as they already are symlinks
to /lib, which means they will automatically be redirected to /usr/lib,
as /usr/lib32 and /usr/lib64 already are.
Furthermore, this means we're no longer supporting a split-usr setup, so
the corresponding configure options have been removed as well for
systemd and, when using a merged /usr, for eudev as well.
In Buildroot, we decided (with this patch) not to support a split-usr
when systemd is used as an init system. This is a design decision, not
a systemd issue. Thus the select is with BR2_INIT_SYSTEMD rather than
with BR2_PACKAGE_SYSTEMD.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
Cc: Mike Williams <mike@mikebwilliams.com>
Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Cc: Baruch Siach <baruch@tkos.co.il>
Tested-by: Mike Williams <mike@mikebwilliams.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-09-04 22:17:32 +02:00
|
|
|
config BR2_ROOTFS_MERGED_USR
|
|
|
|
|
bool "Use symlinks to /usr for /bin, /sbin and /lib"
|
|
|
|
|
help
|
|
|
|
|
If you say 'n' here, then /bin, /sbin and /lib and their
|
|
|
|
|
counterparts in /usr will be separate directories. This
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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
|
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.
|
2013-04-29 12:29:33 +02:00
|
|
|
|
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.
|
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).
|
2013-04-29 12:29:33 +02:00
|
|
|
|
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
|
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!
|
2013-01-05 05:52:02 +01:00
|
|
|
|
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
|
|
|
|
|
|
2016-09-28 15:58:51 +02:00
|
|
|
config BR2_SYSTEM_BIN_SH_MKSH
|
|
|
|
|
bool "mksh"
|
|
|
|
|
depends on BR2_USE_MMU # mksh
|
|
|
|
|
depends on BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
|
|
|
|
|
select BR2_PACKAGE_MKSH
|
|
|
|
|
|
2014-10-12 15:36:22 +02:00
|
|
|
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
|
|
|
|
|
|
2016-09-28 15:58:51 +02:00
|
|
|
comment "bash, dash, mksh, zsh need BR2_PACKAGE_BUSYBOX_SHOW_OTHERS"
|
2014-10-12 15:36:22 +02:00
|
|
|
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
|
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
|
2016-09-28 15:58:51 +02:00
|
|
|
default "mksh" if BR2_SYSTEM_BIN_SH_MKSH
|
2015-06-16 22:42:28 +02:00
|
|
|
default "zsh" if BR2_SYSTEM_BIN_SH_ZSH
|
2014-10-12 15:36:22 +02:00
|
|
|
|
2015-09-02 01:10:34 +02:00
|
|
|
menuconfig BR2_TARGET_GENERIC_GETTY
|
2013-11-11 17:23:23 +01:00
|
|
|
bool "Run a getty (login prompt) after boot"
|
|
|
|
|
default y
|
2013-09-15 08:20:48 +02:00
|
|
|
|
|
|
|
|
if BR2_TARGET_GENERIC_GETTY
|
2009-03-20 22:59:43 +01:00
|
|
|
config BR2_TARGET_GENERIC_GETTY_PORT
|
2013-09-15 08:20:48 +02:00
|
|
|
string "TTY port"
|
2014-12-23 13:06:13 +01:00
|
|
|
default "console"
|
2010-12-05 21:53:14 +01:00
|
|
|
help
|
2013-09-15 08:20:48 +02:00
|
|
|
Specify a port to run a getty on.
|
2009-03-20 22:59:43 +01:00
|
|
|
|
|
|
|
|
choice
|
2013-09-15 08:20:48 +02:00
|
|
|
prompt "Baudrate"
|
2014-12-23 13:06:13 +01:00
|
|
|
default BR2_TARGET_GENERIC_GETTY_BAUDRATE_KEEP
|
2009-03-20 22:59:43 +01:00
|
|
|
help
|
|
|
|
|
Select a baudrate to use.
|
|
|
|
|
|
2009-04-15 15:42:12 +02:00
|
|
|
config BR2_TARGET_GENERIC_GETTY_BAUDRATE_KEEP
|
2013-11-11 17:23:23 +01:00
|
|
|
bool "keep kernel default"
|
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
|
2009-04-15 15:42:12 +02:00
|
|
|
default "0" if BR2_TARGET_GENERIC_GETTY_BAUDRATE_KEEP
|
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
|
|
|
|
|
|
2012-12-13 01:28:11 +01:00
|
|
|
config BR2_TARGET_GENERIC_GETTY_TERM
|
2013-09-15 08:20:48 +02:00
|
|
|
string "TERM environment variable"
|
2012-12-13 01:28:11 +01:00
|
|
|
default "vt100"
|
|
|
|
|
help
|
|
|
|
|
Specify a TERM type.
|
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.
|
2013-09-15 08:20:48 +02:00
|
|
|
endif
|
2012-12-13 01:28:11 +01:00
|
|
|
|
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.
|
|
|
|
|
|
2015-01-16 14:08:39 +01:00
|
|
|
config BR2_SYSTEM_DHCP
|
|
|
|
|
string "Network interface to configure through DHCP"
|
|
|
|
|
default ""
|
2016-09-17 13:58:37 +02:00
|
|
|
depends on BR2_PACKAGE_BUSYBOX || BR2_PACKAGE_IFUPDOWN || BR2_PACKAGE_SYSTEMD_NETWORKD
|
2015-01-16 14:08:39 +01:00
|
|
|
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.
|
|
|
|
|
|
2016-09-17 13:58:37 +02:00
|
|
|
comment "automatic network configuration via DHCP needs ifupdown or busybox or networkd"
|
|
|
|
|
depends on !(BR2_PACKAGE_BUSYBOX || BR2_PACKAGE_IFUPDOWN || BR2_PACKAGE_SYSTEMD_NETWORKD)
|
2015-01-16 14:08:39 +01:00
|
|
|
|
2016-07-17 10:44:27 +02:00
|
|
|
endif # BR2_ROOTFS_SKELETON_DEFAULT
|
|
|
|
|
|
2016-08-03 00:19:40 +02:00
|
|
|
config BR2_ENABLE_LOCALE_PURGE
|
|
|
|
|
bool "Purge unwanted locales"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Explicitly specify what locales to install on target. If N
|
|
|
|
|
then all locales supported by packages are installed.
|
|
|
|
|
|
|
|
|
|
config BR2_ENABLE_LOCALE_WHITELIST
|
|
|
|
|
string "Locales to keep"
|
|
|
|
|
default "C en_US"
|
|
|
|
|
depends on BR2_ENABLE_LOCALE_PURGE
|
|
|
|
|
help
|
|
|
|
|
Whitespace seperated list of locales to allow on target.
|
|
|
|
|
Locales not listed here will be removed from the target.
|
|
|
|
|
See 'locale -a' on your host for a list of locales available
|
|
|
|
|
on your build host, or have a look in /usr/share/locale in
|
|
|
|
|
the target file system for available locales.
|
|
|
|
|
|
|
|
|
|
Notice that listing a locale here doesn't guarantee that it
|
|
|
|
|
will be available on the target - That purely depends on the
|
|
|
|
|
support for that locale in the selected packages.
|
|
|
|
|
|
|
|
|
|
config BR2_GENERATE_LOCALE
|
|
|
|
|
string "Generate locale data"
|
|
|
|
|
default ""
|
|
|
|
|
depends on \
|
|
|
|
|
(BR2_TOOLCHAIN_BUILDROOT_UCLIBC && BR2_ENABLE_LOCALE) || \
|
|
|
|
|
BR2_TOOLCHAIN_USES_GLIBC
|
|
|
|
|
help
|
|
|
|
|
Generate support for a list of locales. Locales can be
|
|
|
|
|
specified with or without encoding, when no encoding is
|
|
|
|
|
specified, UTF-8 is assumed. Examples of locales: en_US,
|
|
|
|
|
fr_FR.UTF-8.
|
|
|
|
|
|
2014-04-07 21:58:03 +02:00
|
|
|
config BR2_TARGET_TZ_INFO
|
|
|
|
|
bool "Install timezone info"
|
2014-04-07 21:58:08 +02:00
|
|
|
select BR2_PACKAGE_TZDATA if BR2_TOOLCHAIN_USES_GLIBC
|
2016-08-09 22:25:55 +02:00
|
|
|
select BR2_PACKAGE_TZDATA if BR2_TOOLCHAIN_USES_MUSL
|
2014-04-07 21:58:08 +02:00
|
|
|
select BR2_PACKAGE_TZ if BR2_TOOLCHAIN_USES_UCLIBC
|
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
|
2016-06-08 23:40:54 +02:00
|
|
|
that this set consumes around 5.5M for glibc and 2.1M for uClibc.
|
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.
|
|
|
|
|
|
2014-04-07 21:58:04 +02:00
|
|
|
config BR2_TARGET_LOCALTIME
|
|
|
|
|
string "default local time"
|
2015-02-12 14:49:31 +01:00
|
|
|
default "Etc/UTC"
|
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.
|
|
|
|
|
|
2014-04-07 21:58:03 +02:00
|
|
|
endif # BR2_TARGET_TZ_INFO
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
2011-05-12 23:37:35 +02:00
|
|
|
config BR2_ROOTFS_POST_BUILD_SCRIPT
|
2013-02-07 12:58:48 +01:00
|
|
|
string "Custom scripts to run before creating filesystem images"
|
2011-05-12 23:37:35 +02:00
|
|
|
default ""
|
|
|
|
|
help
|
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.
|
2011-05-12 23:37:35 +02:00
|
|
|
|
2014-05-02 00:26:36 +02:00
|
|
|
This gives users the opportunity to do board-specific cleanups,
|
2011-05-12 23:37:35 +02:00
|
|
|
add-ons and the like, so the generated files can be used directly
|
|
|
|
|
without further processing.
|
|
|
|
|
|
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.
|
2011-05-12 23:37:35 +02:00
|
|
|
|
2016-07-03 17:08:19 +02:00
|
|
|
config BR2_ROOTFS_POST_FAKEROOT_SCRIPT
|
|
|
|
|
string "Custom scripts to run inside the fakeroot environment"
|
|
|
|
|
default ""
|
|
|
|
|
help
|
|
|
|
|
Specify a space-separated list of scripts to be run at the end
|
|
|
|
|
of the fakeroot script right before the image(s) are actually
|
|
|
|
|
generated.
|
|
|
|
|
|
|
|
|
|
This gives users the opportunity to do customisations of the
|
|
|
|
|
content of the rootfs, which would otherwise require root
|
2016-10-10 15:45:59 +02:00
|
|
|
rights.
|
2016-07-03 17:08:19 +02:00
|
|
|
|
|
|
|
|
These scripts are called with the target directory name as
|
|
|
|
|
first argument. The build will fail on the first scripts that
|
|
|
|
|
exits with a non-zero exit code.
|
|
|
|
|
|
|
|
|
|
Note that Buildroot already provides mechanisms to customise
|
|
|
|
|
the content of the rootfs:
|
|
|
|
|
|
|
|
|
|
- BR2_ROOTFS_STATIC_DEVICE_TABLE
|
|
|
|
|
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,
|
|
|
|
|
|
|
|
|
|
- BR2_ROOTFS_USERS_TABLES:
|
|
|
|
|
to create arbitrary users and their home directories
|
|
|
|
|
|
|
|
|
|
It is highly recommended to use those mechanisms if possible,
|
|
|
|
|
rather than using custom fakeroot scripts.
|
|
|
|
|
|
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
|
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
|
2016-07-03 17:08:19 +02:00
|
|
|
string "Extra arguments passed to custom scripts"
|
|
|
|
|
depends on BR2_ROOTFS_POST_BUILD_SCRIPT != "" \
|
|
|
|
|
|| BR2_ROOTFS_POST_FAKEROOT_SCRIPT != "" \
|
|
|
|
|
|| BR2_ROOTFS_POST_IMAGE_SCRIPT != ""
|
2013-07-10 00:00:31 +02:00
|
|
|
help
|
2014-05-02 00:26:36 +02:00
|
|
|
Pass these additional arguments to each post-build or post-image
|
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.
|
2013-02-07 12:58:43 +01:00
|
|
|
|
2010-12-05 21:52:44 +01:00
|
|
|
endmenu
|
