Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Matthias Hentges <oe@hentges.net>
To: Using the OpenEmbedded metadata to build Distributions
	<openembedded-devel@lists.openembedded.org>
Subject: Re: Making /var/lib persistent
Date: Fri, 20 Apr 2007 01:32:33 +0200	[thread overview]
Message-ID: <1177025553.5022.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20070418090235.GA21841@twibble.org>

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

Am Mittwoch, den 18.04.2007, 19:02 +1000 schrieb Jamie Lenehan:
> On Tue, Apr 17, 2007 at 12:02:03AM +0200, Koen Kooi wrote:
> > Hi,
> > 
> > Marcel Holtmann just pointed me to the fact that OE mount /var as tmpfs for
> > almost all machines, which wipes /var/lib at boot, which will break bluez and
> > dpkg.
> > 
> > What would be the best way to preserve /var/lib (and maybe others) across boots?
> 
> This has been brought up a few times and no one has really had a good
> answer for it. I think /var/lib at a minimum needs to be made
> persistent.
> 
> After thinking about it a bit I've got the following proposal:
> 
>  - make /var a standard directory (no tmpfs)
> 
>  - make /var/volatile a tmpfs filesystems (or /var/tmpfs)
> 
>  - symlink things that are to be made volatile from /var into
>    /var/volatile
> 

Sounds fine to me.

-- 
Matthias 'CoreDump' Hentges 
Cologne / Germany

Webmaster of Hentges.net & Embedded Linux Developer
GPG ->  gpg --keyserver gpg-keyserver.de --recv-keys 0xAF3030D9

My OS: Debian SID: Geek by Nature, Linux by Choice



[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 196 bytes --]

  parent reply	other threads:[~2007-04-19 23:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-16 22:02 Making /var/lib persistent Koen Kooi
2007-04-16 22:13 ` Patrick Steiner
2007-04-16 22:40 ` Erik Hovland
2007-04-16 22:43 ` cyril Romain
2007-04-18  9:02 ` Jamie Lenehan
2007-04-18 14:24   ` Koen Kooi
2007-04-19  1:49     ` Jamie Lenehan
2007-04-19 17:37       ` Justin Patrin
2007-04-23 11:53       ` Paul Sokolovsky
2007-05-10 15:00       ` Paul Sokolovsky
2007-05-10 19:23         ` Koen Kooi
2007-05-10 23:06         ` Richard Purdie
2007-05-14 12:06         ` Koen Kooi
2007-05-14 12:21           ` Koen Kooi
2007-04-19 23:32   ` Matthias Hentges [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-05-14 17:15 [cc]smart

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=1177025553.5022.13.camel@localhost.localdomain \
    --to=oe@hentges.net \
    --cc=openembedded-devel@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