From: <Mikko.Rapeli@bmw.de>
To: <jupiter.hce@gmail.com>
Cc: openembedded-core@lists.openembedded.org, yocto@yoctoproject.org
Subject: Re: [yocto] Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts
Date: Tue, 18 Feb 2020 10:11:22 +0000 [thread overview]
Message-ID: <20200218101122.GE104502@korppu> (raw)
In-Reply-To: <CAA=hcWREdVeYqnOs-3aSFOhobaQWvLoaEU8Rdku_RM=Q5q2Ruw@mail.gmail.com>
On Tue, Feb 18, 2020 at 08:43:01PM +1100, JH wrote:
> Hi Mikko,
>
> On 2/18/20, Mikko.Rapeli@bmw.de <Mikko.Rapeli@bmw.de> wrote:
> > I think you may be missing volatile-binds package and service from your
> > image.
> > See poky/meta/recipes-core/volatile-binds/volatile-binds.bb
>
> I got the source in my build system, it is zeus:
>
> oe-core/meta/recipes-core/volatile-binds/volatile-binds.bb
>
> ./all-oe-linux/volatile-binds
> ./all-oe-linux/volatile-binds/1.0-r0/packages-split/volatile-binds
> ./all-oe-linux/volatile-binds/1.0-r0/sysroot-destdir/sysroot-providers/volatile-binds
> ./all-oe-linux/volatile-binds/1.0-r0/pkgdata-pdata-input/runtime/volatile-binds
> ./all-oe-linux/volatile-binds/1.0-r0/pkgdata-pdata-input/runtime-reverse/volatile-binds
> ./all-oe-linux/volatile-binds/1.0-r0/pkgdata-pdata-input/volatile-binds
> ./all-oe-linux/volatile-binds/1.0-r0/pkgdata/runtime/volatile-binds
> ./all-oe-linux/volatile-binds/1.0-r0/pkgdata/runtime-reverse/volatile-binds
> ./all-oe-linux/volatile-binds/1.0-r0/pkgdata/volatile-binds
> ./all-oe-linux/volatile-binds/1.0-r0/license-destdir/volatile-binds
>
> Are there correct?
>
> > It may be missing /var/log but with systemd there should not be needs to
> > write
> > to that location after image builds...
>
> The volatile did not have the log, so /var/log -> volatile/log was an
> invalid link, should I manually create it?
>
> Thanks Mikko,
Well I have zeus and am using read-only rootfs with volatile binds and
I did not need anything extra. I would dig into this /var/log thing
and patch it away. I use systemd journal so no need for syslogs.
Cheers,
-Mikko
next prev parent reply other threads:[~2020-02-18 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 1:00 Change RO rootfs failed RF Kill Switch Status and Failed to start Run pending postinsts JH
2020-02-18 4:35 ` JH
2020-02-18 6:37 ` [yocto] " Belisko Marek
2020-02-18 7:20 ` JH
2020-02-18 8:58 ` Mikko.Rapeli
2020-02-18 9:43 ` JH
2020-02-18 10:11 ` Mikko.Rapeli [this message]
2020-02-18 11:30 ` JH
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=20200218101122.GE104502@korppu \
--to=mikko.rapeli@bmw.de \
--cc=jupiter.hce@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@yoctoproject.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