From: Mark Hatle <mark.hatle@windriver.com>
To: Colin Walters <walters@verbum.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base-files: Add /run/lock as a standard directory
Date: Fri, 9 May 2014 15:35:27 -0500 [thread overview]
Message-ID: <536D3C0F.1040605@windriver.com> (raw)
In-Reply-To: <1399664736.22845.0@mail.messagingengine.com>
On 5/9/14, 2:41 PM, Colin Walters wrote:
> On Fri, May 9, 2014 at 11:14 AM, Mark Hatle <mark.hatle@windriver.com>
> wrote:
>>
>> /run is not always a tmpfs... We've got configurations where it's
>> persistent.
>
> What? Why?
>
Certain system configurations may require parts of the /run filesystem to not
always be on tmpfs. (Some situations where you have a lot of disk, but limited
ram for instance.. using tmpfs will potentially put your system into a low
memory state, or you might not have enough tmpfs to run the system properly.)
As part of the future work to allow for persistent storage on certain things
that the volatiles are doing right now, /run is one of the directories that
needs to be investigated. Is there actually anything there that may be
desirable to persist from one boot to the next?
--Mark
next prev parent reply other threads:[~2014-05-09 20:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 23:24 [PATCH] base-files: Add /run/lock as a standard directory Mark Hatle
2014-05-09 9:16 ` Burton, Ross
2014-05-09 15:14 ` Mark Hatle
2014-05-09 15:31 ` Saul Wold
2014-05-09 15:50 ` Mark Hatle
2014-05-09 19:41 ` Colin Walters
2014-05-09 20:35 ` Mark Hatle [this message]
2014-05-09 20:50 ` Colin Walters
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=536D3C0F.1040605@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=walters@verbum.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