From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] busybox: Add setsid and cttyhack for tiny DISTRO_FEATURE
Date: Thu, 14 Jun 2012 00:05:31 -0700 [thread overview]
Message-ID: <4FD98D3B.7060200@gmail.com> (raw)
In-Reply-To: <3b44305edae36265295087fb5f31d22d660599b8.1339650859.git.dvhart@linux.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 6/13/2012 10:19 PM, Darren Hart wrote:
> When building very small systems, it can be useful to spawn a shell
> from a simple init script, rather than a full System V Init
> process. This requires the shell be the session leader and be able
> to open the controlling terminal if it is to have job control.
>
> Enable CONFIG_CTTYHACK and CONFIG_SETSID to enable this for
> distros defining the "tiny" DISTRO_FEATURE.
>
> Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: OE Core
> <openembedded-core@lists.openembedded.org> ---
> meta/recipes-core/busybox/busybox.inc | 2 ++ 1 files changed, 2
> insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-core/busybox/busybox.inc
> b/meta/recipes-core/busybox/busybox.inc index 5b83d32..d07ba7e
> 100644 --- a/meta/recipes-core/busybox/busybox.inc +++
> b/meta/recipes-core/busybox/busybox.inc @@ -57,6 +57,8 @@ def
> features_to_busybox_settings(d): busybox_cfg('nls',
> distro_features, 'CONFIG_LOCALE_SUPPORT', cnf, rem)
> busybox_cfg('ipv4', distro_features,
> 'CONFIG_FEATURE_IFUPDOWN_IPV4', cnf, rem) busybox_cfg('ipv6',
> distro_features, 'CONFIG_FEATURE_IFUPDOWN_IPV6', cnf, rem) +
> busybox_cfg('tiny', distro_features, 'CONFIG_SETSID', cnf, rem) +
> busybox_cfg('tiny', distro_features, 'CONFIG_CTTYHACK', cnf, rem)
> return "\n".join(cnf), "\n".join(rem)
>
> # X, Y = ${@features_to_uclibc_settings(d)}
Enabling cttyhack and setsid could be a good thing in general
(thinking of initramfs kind of images) so I would propose to enable it
by default
and not introduce another distro knob here. How much does busybox code
size grow which these two features turned on.?
otherwise second best thing is to keep it in poky-tiny distro layer
which wants to set the policy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/ZjTsACgkQuwUzVZGdMxSXwACfX44Ffs5G4hhW9q9toubwxZYn
Ag4AnijTe1TbzrGZfHaHw+qZY/IQAzlA
=mTVi
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-06-14 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1339650859.git.dvhart@linux.intel.com>
2012-06-14 5:19 ` [PATCH 2/3] busybox: Add setsid and cttyhack for tiny DISTRO_FEATURE Darren Hart
2012-06-14 5:21 ` Darren Hart
2012-06-14 7:05 ` Khem Raj [this message]
2012-06-15 22:22 ` Darren Hart
2012-06-15 22:57 ` Darren Hart
2012-06-14 9:41 ` Phil Blundell
2012-06-14 13:55 ` Darren Hart
2012-06-14 14:26 ` Phil Blundell
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=4FD98D3B.7060200@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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