From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Best way to update deployed systems created with BuildRoot?
Date: Sun, 26 Jul 2015 18:45:53 +0200 [thread overview]
Message-ID: <20150726164553.GF3770@free.fr> (raw)
In-Reply-To: <CAE-zcqW_rRQVr8T+wevTdboyyk3qtf88YpX_be5M-A7_=B89uA@mail.gmail.com>
Fred, All,
On 2015-07-26 09:30 -0700, Fred Basset spake thusly:
> Does anyone have any experience on the best way to update the root
> filesystem of systems in the field once they're deployed?
Basically, you BR2_PACKAGE_XSERVER_XORG_SERVER_MODULARhave two options:
1) duplication
- you split your storage in two halves, each with a version of the
firmware: N and N-1.
- when you update to N+1, you overwrite the N-1 with N+1 and reboot
- your bootloader has a way to find the latest version, check its
integrity, and boot it.
2) rescue/update
- you split your storage in two, one large partition with the
nominal system, a smal one with a minimalist system that only
knows how to update the nominal
- your bootloader is smart enough to detect which it should boot.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-07-26 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 16:30 [Buildroot] Best way to update deployed systems created with BuildRoot? Fred Basset
2015-07-26 16:43 ` Brendan Heading
2015-07-26 16:45 ` Yann E. MORIN [this message]
2015-07-26 17:03 ` Yann E. MORIN
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=20150726164553.GF3770@free.fr \
--to=yann.morin.1998@free.fr \
--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