All of lore.kernel.org
 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 16:05:36 +0200	[thread overview]
Message-ID: <50F56230.7000605@intel.com> (raw)
In-Reply-To: <50F51BE9.6080302@intel.com>



On 01/15/2013 02:24 PM, Martin Jansa wrote:
>> 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?
> That's why we're using u-a for init script, isn't it?
>
I guess you're right. I'll have to find another solution. Most likely,
change update-rc.d script so that it gets the file the link points to,
append the rootfs path to it and then check for the actual file's
existence before reporting an error.

> Imho the problem is only order of postinst where update-rc.d is executed
> before u-a postinst.
No, the problem is not on target. The problem is when the postinst is
run on host. Basically, update-rc.d will run on a file that points to a
path on target:

/path/to/target/rootfs/syslog -> /etc/init.d/syslog.busybox

On host, this link is invalid and update-rc.d will exit with error.
Hence, the postinst will be postponed.

Thanks,
Laurentiu

>
> Cheers,
>



      reply	other threads:[~2013-01-15 14:20 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
2013-01-15 14:05     ` Laurentiu Palcu [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=50F56230.7000605@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 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.