system: do not set hostname and issue for custom skeleton

We expect the custom skeleton to be fully filled with the necessary
files, now. There is definitely no reason we should handle setting the
hostname and the issue file in there. A user using a custom skeleton
should be fully responsible for providing a functional skeleton.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Reviewed-by: Romain Naour <romain.naour@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
Yann E. MORIN
2016-07-17 10:44:28 +02:00
committed by Thomas Petazzoni
parent 65329a1024
commit 8c8b9b6ad7
2 changed files with 8 additions and 4 deletions

View File

@@ -28,6 +28,8 @@ config BR2_ROOTFS_MERGED_USR
endif
if BR2_ROOTFS_SKELETON_DEFAULT
config BR2_TARGET_GENERIC_HOSTNAME
string "System hostname"
default "buildroot"
@@ -46,6 +48,8 @@ config BR2_TARGET_GENERIC_ISSUE
Leave empty to not create /etc/issue, or to keep the
one from a custom skeleton.
endif
choice
bool "Passwords encoding"
default BR2_TARGET_GENERIC_PASSWD_MD5