From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: dora: systemd + package_deb = broken run-postinsts
Date: Fri, 13 Dec 2013 09:58:02 -0600 [thread overview]
Message-ID: <52AB2E8A.6060201@windriver.com> (raw)
In-Reply-To: <CAGDS+nmbUGR6r72_xGzMyouAyGiCpPL115eD8=keaouwrHshBA@mail.gmail.com>
On 12/13/13, 9:38 AM, Steve Sakoman wrote:
> A client has requested help setting up a build using debian packaging
> and systemd as the init system.
>
> When testing the initial image build I noticed that package postinsts
> didn't seem to run properly.
>
> It turns out that dpkg installs an S98run-postinsts file in /etc/rcS.d
> in addition to the normal S99run-postinsts link to
> /etc/init.d/run-postinsts.
>
> Systemd-compat-units installs a run-postinsts.service file that calls
> /etc/rcS.d/S99run-postinsts.
>
> I haven't investigated why the standard /etc/rcS.d/S99run-postinsts
> doesn't work properly for the debian case, but I have verified that
> changing the service file to use the dpkg provided
> /etc/rcS.d/S98run-postinsts works, as does changing dpkg to write
> S99run-postinsts instead of S98run-postinsts.
>
> I'm not sure what the "proper" fix is for this issue. Any
> debian/systemd experts care to weigh in with advice?
Last time I looked into this problem, what appeared to be happening was the
files run out of order. I never did figure out why.
--Mark
> Regards,
>
> Steve
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
prev parent reply other threads:[~2013-12-13 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 15:38 dora: systemd + package_deb = broken run-postinsts Steve Sakoman
2013-12-13 15:58 ` Mark Hatle [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=52AB2E8A.6060201@windriver.com \
--to=mark.hatle@windriver.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