All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-oe][PATCH 1/1] busybox: remove bbappend
Date: Mon, 26 Aug 2013 22:03:37 -0700	[thread overview]
Message-ID: <99DB6787-504F-4C7F-BB26-0A1062E9E60A@gmail.com> (raw)
In-Reply-To: <21550950.hdvkljmBJI@helios>


On Aug 26, 2013, at 2:53 PM, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:

> On Monday 26 August 2013 14:39:10 Khem Raj wrote:
>> On Aug 24, 2013, at 2:47 AM, Paul Eggleton <paul.eggleton@linux.intel.com>
>> wrote:
>>> On Friday 23 August 2013 10:36:15 Khem Raj wrote:
>>>> On Aug 23, 2013, at 4:33 AM, Paul Eggleton
>>>> <paul.eggleton@linux.intel.com> wrote:
>>>>> This bbappend has effectively been merged into OE-Core, although the
>>>>> log buffer size is the busybox default rather than 64K - layers may
>>>>> change this either by providing their own /etc/default/busybox-syslog
>>>>> file (when using systemd) or modifying the
>>>>> CONFIG_FEATURE_IPC_SYSLOG_BUFFER_SIZE option in busybox's build time
>>>>> config
>>>> 
>>>> I think it would be better if we added this option via a kconfig fragment
>>>> in OE-Core if DISTRO_FEATURES contained systemd and then remove this from
>>>> here. I say this because otherwise size of circular buffer goes back to
>>>> 16k from 64k and may not be enough to hold valuable info.
>>> 
>>> Why is this specific to systemd?
>> 
>> It probably is not. Otavio added it, so I am CCing him
>> however this is default used in many distros, just to keep enough
>> messages around while you can affort 64K buffer which is not a huge ask
>> these days.
> 
> If it's generally useful and not specific to systemd (and it seems it isn't the 
> latter) I'd have to say I agree, let's set the default in our busybox 
> defconfig.
> 

I have no issues with changed the defconfig.

> Cheers,
> Paul
> 
> -- 
> 
> Paul Eggleton
> Intel Open Source Technology Centre



  reply	other threads:[~2013-08-27  5:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23 11:33 [meta-oe][PATCH 0/1] Remove busybox bbappend Paul Eggleton
2013-08-23 11:33 ` [meta-oe][PATCH 1/1] busybox: remove bbappend Paul Eggleton
2013-08-23 17:36   ` Khem Raj
2013-08-24  9:47     ` Paul Eggleton
2013-08-26 21:39       ` Khem Raj
2013-08-26 21:53         ` Paul Eggleton
2013-08-27  5:03           ` Khem Raj [this message]
2013-08-29 22:04           ` Otavio Salvador
2013-09-03 17:59   ` Martin Jansa

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=99DB6787-504F-4C7F-BB26-0A1062E9E60A@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=paul.eggleton@linux.intel.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.