Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe PATCH] busybox: Follow OE-Core update to 1.12.1 version
Date: Wed, 24 Jul 2013 10:08:41 +0800	[thread overview]
Message-ID: <51EF3729.8010903@windriver.com> (raw)
In-Reply-To: <2813811.F5BqiUbT83@helios>

On 07/23/2013 08:54 PM, Paul Eggleton wrote:
> On Tuesday 23 July 2013 09:46:36 Otavio Salvador wrote:
>> On Tue, Jul 23, 2013 at 9:41 AM, Paul Eggleton
>>
>> <paul.eggleton@linux.intel.com> wrote:
>>> On Tuesday 23 July 2013 09:09:37 Otavio Salvador wrote:
>>>> On Tue, Jul 23, 2013 at 6:44 AM, Paul Eggleton
>>>>
>>>> <paul.eggleton@linux.intel.com> wrote:
>>>>> On Monday 08 July 2013 13:35:21 Paul Eggleton wrote:
>>>>>> On Friday 05 July 2013 19:45:25 Eric Bénard wrote:
>>>>>>> Le Fri, 05 Jul 2013 18:29:04 +0100,
>>>>>>>
>>>>>>> Paul Eggleton <paul.eggleton@linux.intel.com> a écrit :
>>>>>>>> Could someone *please* figure out what this bbappend is needed for
>>>>>>>> and
>>>>>>>> get
>>>>>>>> it into OE-Core if it is still needed so we can drop it here?
>>>>>>> it's only here to install /etc/default/busybox-syslog which contains
>>>>>>> only one line : OPTIONS="-C64" which sets the size of the logbuffer.
>>>>>>> So obviously this could go into OE-Core.
>>>>>> Yes but why is this needed? If we are to merge this into OE-Core we'll
>>>>>> need
>>>>>> to say why this change is needed in the commit message.
>>>>> ping...
>>>> I am working in something else so I cannot work on busybox now. Feel
>>>> free to handle this.
>>>>
>>>> The syslog support would be good to be kept.
>>> The problem is it's not clear to me what we should do here. Surely having
>>> this bbappend or not isn't the determining factor in whether we have
>>> syslog support with systemd...?
>> With systemd we shouldn't provide it but for sysv we should provide it.
> I still need to know what this is needed for. Surely it doesn't actually
> enable syslog functionality, just adds one configuration value to it? If that's
> the case, why is this configuration change needed?
>
> Cheers,
> Paul
>
Hi All,

FWIW, there are two bugs which might be related to this.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4837
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4860

My opinion is to respect the same configuration file in both sysv and 
systemd systems.
The configuration file is /etc/syslog-startup.conf.

Best Regards,
Chen Qi


      reply	other threads:[~2013-07-24  2:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05 17:01 [meta-oe PATCH] busybox: Follow OE-Core update to 1.12.1 version Otavio Salvador
2013-07-05 17:29 ` Paul Eggleton
2013-07-05 17:34   ` Otavio Salvador
2013-07-05 17:45   ` Eric Bénard
2013-07-08 12:35     ` Paul Eggleton
2013-07-23  9:44       ` Paul Eggleton
2013-07-23 12:09         ` Otavio Salvador
2013-07-23 12:41           ` Paul Eggleton
2013-07-23 12:46             ` Otavio Salvador
2013-07-23 12:54               ` Paul Eggleton
2013-07-24  2:08                 ` ChenQi [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=51EF3729.8010903@windriver.com \
    --to=qi.chen@windriver.com \
    --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