All of lore.kernel.org
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] systemd-compat-units: make run-postinsts.service work correctly on target
Date: Tue, 14 Jan 2014 09:50:34 +0800	[thread overview]
Message-ID: <52D497EA.20301@windriver.com> (raw)
In-Reply-To: <CAJTo0Lb3ysqtjm-fN5vCqpOONEAUH-N+eeC3a=t+PqG8bOWe1g@mail.gmail.com>

On 01/14/2014 01:01 AM, Burton, Ross wrote:
> On 13 January 2014 07:38, Chen Qi <Qi.Chen@windriver.com> wrote:
>> +ExecStart=-/etc/rcS.d/S98run-postinsts ; -/etc/rcS.d/S99run-postinsts
> Can we just make opkg and run-postinsts write that file using the same number?
>
> Also, that service file needs to move directly into run-postinsts.
> There's a start in poky-contrib:ross/postinsts if you want to finish
> it off. :)
>
> Ross
>
>

Hi Ross,

As you have started working on this problem, I think I'll just drop this 
patch.

After looking at your branch, I think there's only one thing to look out 
for. When we're using ipk/dpkg as the package back-end, and 
'package-management' is in IMAGE_FEATURES, there would be no 
/etc/*-postinsts.

Best Regards,
Chen Qi



  reply	other threads:[~2014-01-14  1:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13  7:38 [PATCH 0/2] Fixes for run-postinsts in sysvinit and systemd Chen Qi
2014-01-13  7:38 ` [PATCH 1/2] run-postinsts: remove the init script after a clean start-up Chen Qi
2014-01-13  7:38 ` [PATCH 2/2] systemd-compat-units: make run-postinsts.service work correctly on target Chen Qi
2014-01-13 17:01   ` Burton, Ross
2014-01-14  1:50     ` ChenQi [this message]
2014-01-22 17:08       ` Burton, Ross
2014-01-23  1:28         ` ChenQi

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=52D497EA.20301@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@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.