Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	OpenEmbedded Devel List
	<openembedded-devel@lists.openembedded.org>
Subject: Re: Busybox drop systemd support
Date: Wed, 27 Jul 2016 16:14:26 -0500	[thread overview]
Message-ID: <57992432.4000200@linux.intel.com> (raw)
In-Reply-To: <69a74e8b-5c4f-27d2-6563-0307f9c74dae@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 2335 bytes --]



On 07/27/2016 12:58 PM, Mark Hatle wrote:
> On 7/27/16 12:17 PM, Aníbal Limón wrote:
>> Hi folks,
>>
>> I was working debugging an issue for missing /var/log/messages in
>> systemd/busybox images [1] and then i found that busybox drop support
>> for systemd from 1.25 version [2].
>>
>> This ends in a set of questions of what we need to do in systemd/busybox
>> images since the next version of busybox will not support systemd,
>>
>> I have a couple of ideas,
>>
>> - Remove the support of busybox in systemd images?, this is the hard
>> one, we need an sw alternative here may be toybox...
>> - Maintain the systemd support in busybox?, the patch [2] is small atm
>> but in the future may be this will cause problems for maintain it.
> 
> I know we've had customers who want a 'busybox free' system.  In YP 2.0 there
> were still a few items provided by busybox, so just disabling it (blacklist)
> wasn't easy.
> 
> This sounds like a good opportunity to make sure that you can make a system that
> works with and without busybox.
> 

I agree, currently we have the option to use core-image-{full-cmdline,
lsb} that don't come with busybox but comes with standard linux
utilities may me not targeted for embedded systems. Will be good if we
could provide support for toybox or another busybox like implementation
of shell, tools.

> With that said, looking at [2] below.  I don't see that busybox ever really
> supported or not systemd (contrary to what it says.)

The support was very basic for enable busybox-syslog start/stop with
systemd.

> 
> It just means if systemd is selected, and the user is using busybox -- you
> should not use syslogd out of busybox.  I think this is a reasonable requirement
> -- and something that should be fairly easy to implement.  (With systemd, I'm
> not sure why you would want to use the busybox syslogd anyway.. it's too limited
> IMHO.)

Yes that's an option to mantain to get rid of busybox-syslog and only
use systemd journald.

> 
> --Mark
> 
>> Best regards,
>> 	alimon
>>
>> [1]
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=alimon/debug_times2&id=aa143dbe3cb233ee50944ebb62c541c823179a04
>> [2]
>> https://git.busybox.net/busybox/commit/?id=accd9eeb719916da974584b33b1aeced5f3bb346
>>
>>
>>
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2016-07-27 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 17:17 Busybox drop systemd support Aníbal Limón
2016-07-27 17:58 ` Mark Hatle
2016-07-27 21:14   ` Aníbal Limón [this message]

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=57992432.4000200@linux.intel.com \
    --to=anibal.limon@linux.intel.com \
    --cc=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@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