Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] busybox.inc: have the busybox-syslog postinstall run on host
Date: Tue, 15 Jan 2013 11:05:45 +0200	[thread overview]
Message-ID: <50F51BE9.6080302@intel.com> (raw)
In-Reply-To: <20130114164905.GF2992@jama>



On 01/14/2013 06:49 PM, Martin Jansa wrote:
> On Mon, Jan 14, 2013 at 06:39:29PM +0200, Laurentiu Palcu wrote:
>> update-rc.d fails when executing the postinstall on host. That's because
>> 'syslog' is renamed to 'syslog.busybox' and a 'syslog' link to it is made
>> instead. However, on host, the link is not valid and update-rc.d will
>> complain that the file does not exist. On target, this does not happen.
>>
>> So, this patch will have update-rc.d create the necessary links to
>> syslog.busybox instead. Technically, the behavior is unchanged and
>> syslogd will be started as usual. The only change will be the links in
>> rcX.d directories:
>>
>> Instead of: S20syslog -> ../init.d/syslog
>> we will have: S20syslog.busybox -> ../init.d/syslog.busybox
>>
>> Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
>> ---
>>  meta/recipes-core/busybox/busybox.inc |    2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-core/busybox/busybox.inc b/meta/recipes-core/busybox/busybox.inc
>> index 972e7d0..c70ba62 100644
>> --- a/meta/recipes-core/busybox/busybox.inc
>> +++ b/meta/recipes-core/busybox/busybox.inc
>> @@ -25,7 +25,7 @@ FILES_${PN}-hwclock = "${sysconfdir}/init.d/hwclock.sh"
>>  INITSCRIPT_PACKAGES = "${PN}-httpd ${PN}-syslog ${PN}-udhcpd ${PN}-mdev ${PN}-hwclock"
>>  
>>  INITSCRIPT_NAME_${PN}-httpd = "busybox-httpd"
>> -INITSCRIPT_NAME_${PN}-syslog = "syslog"
>> +INITSCRIPT_NAME_${PN}-syslog = "syslog.${BPN}"
> 
> What if syslog-ng is installed? won't it run both syslog implementations?
This is a valid concern. It would certainly start them both or, at
least, try. But, is it normal for one to have two different syslog
implementations installed? Is this a valid use case?

Thanks,
Laurentiu

> 
>>  INITSCRIPT_NAME_${PN}-mdev = "mdev"
>>  INITSCRIPT_NAME_${PN}-hwclock = "hwclock.sh"
>>  INITSCRIPT_PARAMS_${PN}-mdev = "start 06 S ."
>> -- 
>> 1.7.9.5
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> 



  reply	other threads:[~2013-01-15  9:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 16:39 [PATCH] busybox.inc: have the busybox-syslog postinstall run on host Laurentiu Palcu
2013-01-14 16:49 ` Martin Jansa
2013-01-15  9:05   ` Laurentiu Palcu [this message]
2013-01-15 14:05     ` Laurentiu Palcu

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=50F51BE9.6080302@intel.com \
    --to=laurentiu.palcu@intel.com \
    --cc=martin.jansa@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