public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Todd Goodman <tsg@bonedaddy.net>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] quickpkg and PKG_INSTALL_MASK
Date: Tue, 24 Jan 2012 09:06:29 -0500	[thread overview]
Message-ID: <20120124140629.GR26939@ns1.bonedaddy.net> (raw)
In-Reply-To: <OFEBDA1FC0.30EED2E1-ONC125798F.002A27B5-C125798F.002B3E16@transmode.se>

* Joakim Tjernlund <joakim.tjernlund@transmode.se> [120124 02:18]:
> Ed W <lists@wildgooses.com> wrote on 2012/01/23 19:43:49:
[ .. ]
> > I'm doing something like this using aufs.  The performance seems "not
> > bad", but you get a couple MB or so memory hit.  (I'm using squashfs as
> > well, so unsure which causes the main memory increase).
> 
> hmm, not sure how aufs would work out. One would like to permanently delete the

aufs is A Union FileSystem.  You can have a RO "branch" (say SquashFS)
and a r/w "branch" (say JFFS2 or UBIFS.)  When you write it will write
to the r/w branch and when you read it will read from the r/w branch if
it exists, else the r/o.

So, if you want to permanently delete the old software.  Write it to the
filesystem r/w filesystem (initially or after you have the aufs mounts
mounted.)  Then you can delete from the r/w filesystem and it's gone for
good.

> old sw at some point and I don't see how, perhaps I misunderstand something?
> 
> How does aufs do w.r.t power cuts? We need a reliable FS w.r.t power cuts. In the
> past we have used JFFS2 on NOR flash and that has worked really well. Now
> we need to switch to NAND due to size requirements.

You still want to pick a r/w branch with a filesystem that handles power
cuts well.  You can continue to use JFFS2.

[..]

Todd



  reply	other threads:[~2012-01-24 15:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23 13:23 [gentoo-embedded] quickpkg and PKG_INSTALL_MASK Joakim Tjernlund
2011-12-25  9:34 ` Kfir Lavi
2011-12-25 17:52   ` solar
2011-12-26 18:03     ` Joakim Tjernlund
2011-12-26 20:38       ` solar
2011-12-27  9:40         ` Joakim Tjernlund
2011-12-27 11:44           ` Kfir Lavi
2011-12-29  9:48         ` Joakim Tjernlund
2012-01-23 18:43       ` Ed W
2012-01-24  7:52         ` Joakim Tjernlund
2012-01-24 14:06           ` Todd Goodman [this message]
2012-01-25 13:21             ` Ed W
2012-01-26 11:11               ` Joakim Tjernlund
2012-01-26 13:30                 ` Todd Goodman
2012-01-27 18:15                   ` Ed W
2012-01-26 14:59                 ` Peter Stuge
2012-01-27 18:27                   ` Ed W

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=20120124140629.GR26939@ns1.bonedaddy.net \
    --to=tsg@bonedaddy.net \
    --cc=gentoo-embedded@lists.gentoo.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