Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] Both cramfs + jffs2 in buildroot?
Date: Thu, 9 Oct 2008 11:42:28 +1100	[thread overview]
Message-ID: <20081009004228.GA12878@cloud.net.au> (raw)
In-Reply-To: <48ECAD04.6070209@timeterminal.se>

On Wed, Oct 08, 2008 at 02:52:20PM +0200, Daniel Nystr?m wrote:
> (Sorry if this has been a topic earlier, but it's really hard to search
> the mailing archive)
> 
> Is it possible in Buildroot to make both a read-only rootfs and a second
> writable filesystem?
> 
> A common setup is using cramfs for / and mounting a jffs2 on /mnt/flash,
> and then make a symlink of /etc to point at /mnt/flash/etc where all
> config files are writable.
> 
> Is this possible to achive with Buildroot?

No, there's no support for building two file systems with different
contents.

There might be better ways to handle this anyway, like copying /etc from
the cramfs to the rw jffs2 on the first bootup?

With regard to mounting /mnt/flash/etc onto /etc, I don't think a
symlink will work - you need to use/run stuff from /etc before the
second file system can be mounted. I suggest a minimal /etc in the root,
enough to get the other file system mounted, and then "mount --bind" the 
new /etc over the top.


Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  reply	other threads:[~2008-10-09  0:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 12:52 [Buildroot] Both cramfs + jffs2 in buildroot? Daniel Nyström
2008-10-09  0:42 ` Hamish Moffatt [this message]
2008-10-09  6:49   ` Daniel Nyström
2008-10-09  8:16 ` Hinko Kocevar
2008-10-10  3:29   ` Hamish Moffatt

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=20081009004228.GA12878@cloud.net.au \
    --to=hamish@cloud.net.au \
    --cc=buildroot@busybox.net \
    /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