Re: [yocto] /var/volatile not mounted as tmpfs on read-only rootfs when migrating to Warrior

on, as tmpfs. It doesn't explain what's changed, however. Either way, the fault appears to be in my environment, and Sumo possibly worked with luck. Regards, Ryan. > Kind regards, > Ryan. > > >> >> Best regards, >> >> >> >> Carsten >> >> &g

Re: [yocto] /var/volatile not mounted as tmpfs on read-only rootfs when migrating to Warrior

n:* yocto-boun...@yoctoproject.org [mailto: > yocto-boun...@yoctoproject.org] *Im Auftrag von *Ryan Harkin > *Gesendet:* Freitag, 2. August 2019 13:09 > *An:* yocto@yoctoproject.org > *Cc:* openembedded > *Betreff:* [yocto] /var/volatile not mounted as tmpfs on read-only rootfs >

Re: [yocto] /var/volatile not mounted as tmpfs on read-only rootfs when migrating to Warrior

as tmpfs on read-only rootfs when migrating to Warrior Hi, I have a working system based on Sumo. The system boots with a read-only rootfs, then applies are read-write overlay for /etc. When I migrate to Warrior, systemd-resolved fails to start. If I mount the same rootfs via NFS, it starts and

[yocto] /var/volatile not mounted as tmpfs on read-only rootfs when migrating to Warrior

Hi, I have a working system based on Sumo. The system boots with a read-only rootfs, then applies are read-write overlay for /etc. When I migrate to Warrior, systemd-resolved fails to start. If I mount the same rootfs via NFS, it starts and works fine. systemd-timesyncd is also failing, but I ha