public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: hno@marasystems.com (Henrik Nordstrom)
To: linux-mtd@lists.infradead.org
Subject: "Hot" updating root-mounted mtd partitions
Date: Wed, 26 Feb 2003 01:31:11 +0100	[thread overview]
Message-ID: <200302260131.11190@henrik.marasystems.com> (raw)
In-Reply-To: <3E5C016C.4070700@elitedvb.net>

On Wednesday 26 February 2003 00.51, Felix Domke wrote:

> Of course updating it (be it from internet, from satellite or
> whatever) includes erasing and rewriting the root. This naturally
> causes troubles. How can i avoid this?

Have the system load the filesystem into ram at startup, and run from 
there.. can very easily by done by loading the root as an initrd.. 
this obviously assumes your root is relatively small.

or have two partitions, and only update the one not currently running 
and then update the boot loader nvram to load the "other" image after 
a successful upgrade.

> Possibilities are:
>   - remount rootfs using an in-memory-copy (ramfs), but i don't
> think this is possible, since there are many open files in the old
> fs. - including ugly hacks in the flash driver, mainly by copying
> the partition to RAM and redirect accesses to that backup while
> flashing the rootfs
>
> both possibilities suck.

Of these, a devise layer hack sounds most appealing, but you should 
also consider what happens on partial upgrades etc..

You might actually be able to pivot_root into a ram based rootfs while 
upgrading, but almost certainly involves a near complete shutdown to 
terminate all applications before the actual upgrade starts..

Regards
Henrik

  reply	other threads:[~2003-02-26  0:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25 23:51 "Hot" updating root-mounted mtd partitions Felix Domke
2003-02-26  0:31 ` Henrik Nordstrom [this message]
2003-02-26  1:41   ` Jasmine Strong

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=200302260131.11190@henrik.marasystems.com \
    --to=hno@marasystems.com \
    --cc=linux-mtd@lists.infradead.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