From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patrick Ohly <patrick.ohly@intel.com>, Khem Raj <raj.khem@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] busybox: Add support for busybox-init
Date: Tue, 02 Feb 2016 15:29:43 +0000 [thread overview]
Message-ID: <1454426983.27087.81.camel@linuxfoundation.org> (raw)
In-Reply-To: <1454425253.22914.5.camel@intel.com>
On Tue, 2016-02-02 at 16:00 +0100, Patrick Ohly wrote:
> On Mon, 2016-02-01 at 08:57 -0800, Khem Raj wrote:
> > On Mon, Feb 1, 2016 at 12:14 AM, Patrick Ohly <
> > patrick.ohly@intel.com> wrote:
> > > On Mon, 2016-01-25 at 11:39 -0800, Andre McCurdy wrote:
> > > > > + if grep "CONFIG_INIT=y" ${B}/.config; then
> > > > > + install -D -m 0777 ${WORKDIR}/rcS
> > > > ${D}${sysconfdir}/init.d/rcS
> > > > > + install -D -m 0777 ${WORKDIR}/rcK
> > > > ${D}${sysconfdir}/init.d/rcK
> > > > > + install -D -m 0755 ${WORKDIR}/runlevel
> > > > ${D}${base_sbindir}/runlevel
> > > > > + if grep "CONFIG_FEATURE_USE_INITTAB=y"
> > > > ${B}/.config; then
> > > > > + install -D -m 0777
> > > > > ${WORKDIR}/inittab
> > > > ${D}${sysconfdir}/inittab
> > > > > + tmp="${SERIAL_CONSOLES}"
> > > > > + for i in $tmp
> > > > > + do
> > > > > + j=`echo ${i} | sed s/\;/\
> > > > > /g`
> > > > > + label=`echo ${i} | sed -e
> > > > > 's/tty//'
> > > > -e 's/^.*;//' -e 's/;.*//'`
> > > > > + echo "tty$label::respawn:
> > > > ${base_sbindir}/getty ${j}" >> ${D}${sysconfdir}/inittab
> > > > > + done
> > > > > + fi
> > > > > + fi
> > >
> > > SERIAL_CONSOLES is typically set differently for different
> > > machines. But
> > > busybox is not machine-specific, therefore using SERIAL_CONSOLE
> > > like
> > > this prevents sstate/package reuse or worse, causes package
> > > versioning
> > > problems.
> >
> > when busybox is used as init system then it becomes machine
> > specific and we have
> > a choice to do so which is disabled by default.
>
> In my case, busybox is not the init system and the recipe is
> therefore
> not machine specific. But the code above is active and thus
> introduces a
> sstate dependency on the machine-specific SERIAL_CONSOLES anyway,
> even
> though the code is dead (if check never reaches it).
>
> The code would have to be added conditionally, and only when it is
> okay
> to reference ${SERIAL_CONSOLES}.
I think we should split this init piece out into a separate recipe,
which busybox can depend on if/as/when needed.
Cheers,
Richard
next prev parent reply other threads:[~2016-02-02 15:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 20:49 [PATCH 1/2] busybox: Add support for busybox-init Khem Raj
2016-01-22 20:49 ` [PATCH 2/2] local.conf.sample: Document HOW-TO enable systemd or busbox to replace sysvinit Khem Raj
2016-01-22 20:57 ` Tanu Kaskinen
2016-01-22 21:06 ` Khem Raj
2016-01-24 19:21 ` Paul Eggleton
2016-01-24 20:20 ` Khem Raj
2016-01-25 19:39 ` [PATCH 1/2] busybox: Add support for busybox-init Andre McCurdy
2016-01-25 20:11 ` Khem Raj
2016-02-01 8:14 ` Patrick Ohly
2016-02-01 16:57 ` Khem Raj
2016-02-02 15:00 ` Patrick Ohly
2016-02-02 15:29 ` Richard Purdie [this message]
2016-05-02 16:43 ` Denys Dmytriyenko
2018-03-02 21:19 ` Denys Dmytriyenko
2018-03-03 1:48 ` Denys Dmytriyenko
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=1454426983.27087.81.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@intel.com \
--cc=raj.khem@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.