On Tue, Feb 18, 2020 at 08:43:01PM +1100, JH wrote: > Hi Mikko, > > On 2/18/20, [email protected] <[email protected]> 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 -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
