All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Darander <anders@chargestorm.se>
To: Ulf Samuelsson <yocto@emagii.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: How handle files needing updates in read-only filesystem
Date: Wed, 13 Jun 2018 15:20:09 +0200	[thread overview]
Message-ID: <20180613132009.GA11193@ad.chargestorm.se> (raw)
In-Reply-To: <9EEEF203-2371-4CCE-8E70-947330CDB462@emagii.com>

* Ulf Samuelsson <yocto@emagii.com> [180612 22:01]:

> We want most of /etc to be read-only for security reasons,
> and the overlayfs will make the whole of /etc writeable.

> I tried mount —bind /etc/timezone /persistent/etc/timezone, and it
> complained that they were not directories. Bind mounting /etc again
> will make all of /etc writeable.

Try to use: mount —o bind /etc/timezone /persistent/etc/timezone

I'm using that heavily, either manually or by the volatile-binds recipe.
It works perfectly fine with files.

> Symlinking to /persistent is fine, so the question is what an
> acceptable method is to have a simple way of ensuring that a certain
> file is converted to that symlink.

This is normally done by a manual inspection / addition of bbappend
file.

Cheers,
Anders
-- 
Anders Darander, Senior System Architect
ChargeStorm AB / eStorm AB


  reply	other threads:[~2018-06-13 13:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-09  9:50 How handle files needing updates in read-only filesystem Ulf Samuelsson
2018-06-09 23:36 ` Peter Kjellerstedt
2018-06-10  3:30   ` Ulf Samuelsson
2018-06-13 13:20     ` Anders Darander [this message]
2018-06-13 16:28       ` Ulf Samuelsson
2018-06-13 23:02         ` Andre McCurdy
2018-06-14 21:02           ` Ulf Samuelsson

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=20180613132009.GA11193@ad.chargestorm.se \
    --to=anders@chargestorm.se \
    --cc=yocto@emagii.com \
    --cc=yocto@yoctoproject.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 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.