Re: [OE-core] Issue: /var/tmp does not persist due to /var/volatile being tmpfs in fstab #scarthgap

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Tue, 2025-03-18 at 09:11 -0700, Vish via lists.openembedded.org wrote:
> Thank you for the reply. 
>  
> In Scarthgap LTS implementation is different, but I got the idea. 
> https://git.yoctoproject.org/poky/tree/meta/conf/bitbake.conf?h=scarthgap#n387
>  
> I believe default behavior should be same as before to persist
> /var/temp over reboot and these changes should only be required for
> any customization. Also somewhat difficult for us to upgrade CI/CD
> with this config. 
>  
> Can we know the reasons for original changes here?
> https://git.yoctoproject.org/poky/commit/meta/recipes-core/systemd/systemd/00-create-volatile.conf?h=scarthgap&id=3cc8c3520cedb66500757f843f757646da69ab30
>  
> I reviewed commit message but not giving much details. Considering
> default base-files and as persistence is required, this newer
> approach seems be an issue. 
>  
> We recently migrated to Scarthgap and noticed the issues with our
> system. This can be issue for other developers as well whoever is
> planning to migrate to Scarthgap and embedded devices in the field.
> This commit requires all build systems to adopt changes bitbake.conf
> which is not preferable .  
>  
> What is the usecases targeted with the changes? I believe the commit
> should be reviewed again and potentially reverted considering default
> behavior with base-files and 00-create-volatile.conf.

scarthgap has been released for a while now so making a change like
this well into the stable release cycle would be a problem in its own
right. I therefore don't think this can be reverted now regardless of
whether it should have happened or not.

Cheers,

Richard