All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lukas Böhm" <lukas.boehm@iseg-hv.de>
To: yocto@yoctoproject.org
Subject: Re: Read-only file system with persistent storage
Date: Thu, 23 Jul 2015 15:24:10 +0200	[thread overview]
Message-ID: <55B0EAFA.40502@iseg-hv.de> (raw)
In-Reply-To: <4B07ADD556F70043925DA2E9C5D4346D2FE9BBF806@MSXBEBVT12.planar.net>



Am 21.07.2015 um 18:01 schrieb Matt Schuckmann:
> If you are using systemd you can simply create a separate writeable partition and then use the volatile_binds.bb recipe to map files or directories from the read only rootfs to the writable partition via bind mounts.

How should one use the volatile-binds.bb recipe? How can I configure which 
files, directories shall be bind mounted?
Thanks

> If you are not using systemd you can do the same thing with sysVinit you'll just have to write your own recipe equivalent to volatile_binds.bb
>
> This method works and the way volatile_binds is written it takes the default settings from the read only rootfs which is nice.
>
> The only problem I've found is if you have a bind mount to a file you have to be careful not to delete the file or it will break the mount link.You'd be surprised how often you want to delete the file when you go to update it. Therefore I tend to use directories with volatile_binds.bb instead of individual files.
>
> Matt S.
>
>> -----Original Message-----
>> From: yocto-bounces@yoctoproject.org [mailto:yocto-
>> bounces@yoctoproject.org] On Behalf Of Gary Thomas
>> Sent: Thursday, July 16, 2015 4:37 AM
>> To: Yocto Project
>> Subject: [yocto] Read-only file system with persistent storage
>>
>> I'd like to set up a system with a read-only root file system along with some
>> persistent read-write storage.  What are the [best] options in Poky/Yocto for
>> this?  Is there any support for some type of overlay file system?
>>
>> Thanks for any ideas/pointers
>>
>> --
>> ------------------------------------------------------------
>> Gary Thomas                 |  Consulting for the
>> MLB Associates              |    Embedded world
>> ------------------------------------------------------------
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>

-- 
Lukas Böhm                       fon:  ++49 351 26996-0
iseg Spezialelektronik GmbH      fax:  ++49 351 26996-21
Bautzner Landstr. 23             mail: lukas.boehm@iseg-hv.de
D-01454 Radeberg OT Rossendorf   web:  www.iseg-hv.de

Geschäftsführer/Managing Director:
     Dr. Frank Gleisberg, Dr. Joachim Pöthig
Registergericht/Lower District Court:
     Amtsgericht Dresden HRB 16250
Umsatzsteuer-Identnummer / VAT Id:
     DE 812 50 89 42



      reply	other threads:[~2015-07-23 13:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 11:36 Read-only file system with persistent storage Gary Thomas
2015-07-16 13:05 ` Daniel.
2015-07-17 13:03 ` Nikolay Dimitrov
2015-07-20  6:07 ` Mike Looijmans
2015-07-21 15:01   ` Thomas Petazzoni
2015-07-21 16:01 ` Matt Schuckmann
2015-07-23 13:24   ` Lukas Böhm [this message]

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=55B0EAFA.40502@iseg-hv.de \
    --to=lukas.boehm@iseg-hv.de \
    --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.