From: John Stile <john@stilen.com>
To: buildroot@busybox.net
Subject: [Buildroot] making a second small failsafe file system
Date: Tue, 29 Jan 2013 17:33:06 -0800 [thread overview]
Message-ID: <1359509586.7974.207.camel@genx> (raw)
I have a board with 8Mb of NOR and 256Mb of NAND.
I plan to normally use NAND, divided into redundant halves, but if
neither half can boot, I would like a failsafe minimal file system on
NOR in order to re-image NAND over the network.
What are my options?
Do I maintain a separate buildroot just for that failsafe?
Should I create a post-build script that assembles a tiny file system
image?
Has anyone tired this?
next reply other threads:[~2013-01-30 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 1:33 John Stile [this message]
2013-01-30 2:21 ` [Buildroot] making a second small failsafe file system Willy Lambert
2013-01-30 4:58 ` Baruch Siach
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=1359509586.7974.207.camel@genx \
--to=john@stilen.com \
--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 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.