From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] var/volatile: Mount it if doing ro-rfs
Date: Wed, 11 Mar 2015 10:19:20 +0000 [thread overview]
Message-ID: <1426069160.9114.41.camel@linuxfoundation.org> (raw)
In-Reply-To: <1426062809-1844-1-git-send-email-raj.khem@gmail.com>
On Wed, 2015-03-11 at 08:33 +0000, Khem Raj wrote:
> - Do not mount /var/volatile to be tmpfs always only when generating
> readonly rootfs
> - Generate var-volatile.mount unit when using system in readonly-rootfs
> to mount /var/volatile as tmpfs
> - for sysvinit, mount /var/volatile to be tmpfs if its not already
> mounted so
> - Use RequiresMountsFor instead of After=, so systemd figures out the
> needed dependencies for making /var/volatile accessible for journald
> and not us.
>
> Change-Id: I0b176b3e1c1e88e84d2c93154aac04cef565d8ea
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/classes/image.bbclass | 1 +
> meta/recipes-core/base-files/base-files/fstab | 1 -
> meta/recipes-core/initscripts/initscripts-1.0/read-only-rootfs-hook.sh | 2 +-
> meta/recipes-core/systemd/systemd/journald-volatile.conf | 2 +-
> 4 files changed, 3 insertions(+), 3 deletions(-)
Which combinations has this been tested with? Given the time the patch
has existed for, I'm sceptical all the combinations we need have been
tested, I'd love to be wrong.
This is a pretty major change of behaviour and given the problems
previous changes have caused, I'm very very very nervous about what
issues this is going to cause :(.
Cheers,
Richard
next prev parent reply other threads:[~2015-03-11 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 8:33 [PATCH] var/volatile: Mount it if doing ro-rfs Khem Raj
2015-03-11 10:19 ` Richard Purdie [this message]
2015-03-11 14:53 ` Khem Raj
2015-03-11 16:05 ` Khem Raj
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=1426069160.9114.41.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.