From: Jack Mitchell <ml@communistcode.co.uk>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: systemd post-install failure
Date: Mon, 22 Apr 2013 15:44:20 +0100 [thread overview]
Message-ID: <51754CC4.9010604@communistcode.co.uk> (raw)
In-Reply-To: <CAJTo0LYMc0F=OG-xUQztpveQdYAPKnj0W_8Vb-wRZRL7F5+bSQ@mail.gmail.com>
On 22/04/13 15:40, Burton, Ross wrote:
> On 22 April 2013 15:13, Jack Mitchell <ml@communistcode.co.uk> wrote:
>> Booting master today I had a systemd fault. Enabling debugging I captured
>> the (attached) output. The gist of which is:
>>
>> So, looking into systemd-system-update-generator, it seems this is what
>> takes card of the post install scripts, which I know we're having problems
>> with.
> Not quite - the system update generator would be used if we were using
> systemd's native systemd update protocol, which we're not. This
> generator shouldn't do anything unless you've got a symlink
> /system-update (see
> http://freedesktop.org/wiki/Software/systemd/SystemUpdates for the
> details).
>
> Ross
Ah, ok then, I don't have a /system-update. So square one, any ideas why
this would have suddenly flagged up? I was building and booting fine on
Wed/Thurs. That was the only useful bit of the debug log I could
determine...
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next prev parent reply other threads:[~2013-04-22 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 14:13 systemd post-install failure Jack Mitchell
2013-04-22 14:40 ` Burton, Ross
2013-04-22 14:44 ` Jack Mitchell [this message]
2013-04-22 14:56 ` Burton, Ross
2013-04-22 15:03 ` Jack Mitchell
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=51754CC4.9010604@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--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.