public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Russ Dill <Russ.Dill@asu.edu>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Chris AtLee <catlee@canada.com>,
	Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: Updating the root partition
Date: 19 Jun 2002 15:44:15 -0700	[thread overview]
Message-ID: <1024526655.441.5.camel@timmy> (raw)
In-Reply-To: <20020620002303.A21586@wohnheim.fh-wedel.de>

On Wed, 2002-06-19 at 15:23, Jörn Engel wrote:
> On Wed, 19 June 2002 11:18:12 -0400, Chris AtLee wrote:
> > I've got linux booting off of a cramfs partition sitting on mtdblock1. 
> > Is it possible to overwrite the mtdblock1 partition while linux is
> > running?  The kernel itself isn't located on the root partition.  I've
> > tried just copying a new cramfs image to /dev/mtd1 but I get errors on
> > decompressing next time I try and boot.
> 
> - Use /dev/mtdblock1. The char device does not erase any blocks, so
>   you end up ||ing the old and new data.
> - Do the flashing soon after reboot and make sure, all necessary
>   binaries are in RAM. Power-cycle afterwards, as you sure don't want
>   to load good-as-random code and execute it, albeit it is only the
>   userspace.

if you are using busybox init, you can signal it to kill everything, and
exec run the respawn entry in inittab. Your respawn entry can copy a
statiacly linked copy of whatever you are using to flash to a ramfs,
chroot/piviot_root to the ramfs and exec the program. once there, umount
the cramfs, and you can safely do whatever you want.

  reply	other threads:[~2002-06-19 22:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19 15:18 Updating the root partition Chris AtLee
2002-06-19 22:23 ` Jörn Engel
2002-06-19 22:44   ` Russ Dill [this message]
2002-06-19 23:22     ` Christopher Fowler
2002-06-19 23:29       ` Russ Dill
2002-06-19 23:56         ` Christopher Fowler
2002-06-20  1:43           ` Russ Dill
2002-06-20 10:13             ` Stefan Thomasson
2002-06-20 11:47               ` cfowler

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=1024526655.441.5.camel@timmy \
    --to=russ.dill@asu.edu \
    --cc=catlee@canada.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --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