From: Dmitry <golubovsky@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] PAM support in Busybox if linux-pam is built
Date: Sat, 11 Aug 2012 23:03:43 -0400 [thread overview]
Message-ID: <1344740623-29446-1-git-send-email-golubovsky@gmail.com> (raw)
Signed-off-by: Dmitry <golubovsky@gmail.com>
---
package/busybox/Config.in | 11 +++++++++++
package/busybox/busybox.mk | 12 ++++++++++++
2 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/package/busybox/Config.in b/package/busybox/Config.in
index dedcf18..3e9f56d 100644
--- a/package/busybox/Config.in
+++ b/package/busybox/Config.in
@@ -62,6 +62,17 @@ config BR2_PACKAGE_BUSYBOX_WATCHDOG
Install the watchdog daemon startup script,
that just start at the boot the busybox watchdog daemon.
+config BR2_PACKAGE_BUSYBOX_PAM
+ bool "Enable PAM support in Busybox"
+ default y
+ depends on BR2_PACKAGE_LINUX_PAM
+ help
+ PAM support in Busybox is enabled by default if package
+ linux-pam is selected. Make sure that files /etc/pam.d/default
+ and/or /etc/pam.d/login exist and contain valid authentication
+ stack. Otherwise you will not be able to log into the booted
+ system. If unsure unselect this item.
+
if BR2_PACKAGE_BUSYBOX_WATCHDOG
config BR2_PACKAGE_BUSYBOX_WATCHDOG_PERIOD
diff --git a/package/busybox/busybox.mk b/package/busybox/busybox.mk
index 17ee50a..c97ce77 100644
--- a/package/busybox/busybox.mk
+++ b/package/busybox/busybox.mk
@@ -161,6 +161,17 @@ define BUSYBOX_INSTALL_WATCHDOG_SCRIPT
endef
endif
+ifeq ($(BR2_PACKAGE_BUSYBOX_PAM),y)
+BUSYBOX_DEPENDENCIES += linux-pam
+define BUSYBOX_ENABLE_PAM
+ $(call KCONFIG_ENABLE_OPT,CONFIG_PAM,$(BUSYBOX_BUILD_CONFIG))
+endef
+else
+define BUSYBOX_ENABLE_PAM
+ $(call KCONFIG_DISABLE_OPT,CONFIG_PAM,$(BUSYBOX_BUILD_CONFIG))
+endef
+endif
+
# We do this here to avoid busting a modified .config in configure
BUSYBOX_POST_EXTRACT_HOOKS += BUSYBOX_COPY_CONFIG
@@ -176,6 +187,7 @@ define BUSYBOX_CONFIGURE_CMDS
$(BUSYBOX_DISABLE_MMU_APPLETS)
$(BUSYBOX_SET_INIT)
$(BUSYBOX_SET_WATCHDOG)
+ $(BUSYBOX_ENABLE_PAM)
@yes "" | $(MAKE) ARCH=$(KERNEL_ARCH) CROSS_COMPILE="$(TARGET_CROSS)" \
-C $(@D) oldconfig
endef
--
1.7.2.5
next reply other threads:[~2012-08-12 3:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 3:03 Dmitry [this message]
2012-08-12 14:17 ` [Buildroot] [PATCH] PAM support in Busybox if linux-pam is built Baruch Siach
2012-08-12 14:25 ` Dmitry Golubovsky
2012-08-12 15:18 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1344740623-29446-1-git-send-email-golubovsky@gmail.com \
--to=golubovsky@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox