Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Vish" <vs.yocto@outlook.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Issue: /var/tmp does not persist due to /var/volatile being tmpfs in fstab #scarthgap
Date: Tue, 18 Mar 2025 16:24:07 -0700	[thread overview]
Message-ID: <29973.1742340247475380282@lists.openembedded.org> (raw)
In-Reply-To: <83c9c92162d9c0bc1387c633f1464e67f57c70bc.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 848 bytes --]

Thanks for the reply.

Do maintainers recognize this as an issue with having this as default option? There are chances that similar to us other devs/orgs are planning migration in phases to Scarthgap considering Kirkstone getting updates, so this could potentially become issue for others as well. We do have sizable amount of edge systems in production with various CI, and this change broke an important feature and took some time for us to find root cause.

I believe correcting is still a proper thing to do and can be planned during any releases.
Additional reference -
https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s15.html ( https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s15.html )

Also, it would be good to know what scenarios were considered with this change, probably we are missing some context.

Regards,
VS.

[-- Attachment #2: Type: text/html, Size: 1220 bytes --]

  reply	other threads:[~2025-03-18 23:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18  3:17 Issue: /var/tmp does not persist due to /var/volatile being tmpfs in fstab #scarthgap Vish
2025-03-18  4:48 ` [OE-core] " Chen, Qi
2025-03-18 16:11   ` Vish
2025-03-18 22:22     ` [OE-core] " Richard Purdie
2025-03-18 23:24       ` Vish [this message]
2025-03-19  6:57         ` Alexander Kanavin
2025-03-19  9:11         ` Richard Purdie
2025-03-19 18:28           ` Vish
2025-03-19  4:55     ` [OE-core] " Niko Mauno

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=29973.1742340247475380282@lists.openembedded.org \
    --to=vs.yocto@outlook.com \
    --cc=openembedded-core@lists.openembedded.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