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

On Wed, 2002-06-19 at 16:56, Christopher Fowler wrote:
> In a way.  On my system you have to restart to run on the new software. 
> I have implemented a pseudo single user mode in init that will umount
> the rootfs and then dump the new software into memory.  Ths keeps you
> from having to do a restart.  However, this is not possible from remote
> locations.  You must be on serial console to do this.  That is why
> single user mode is not acceptable.

I think you are a little confused on what is going on here, so I'll
explain in detail.

on my system, when it is normally up and running, an ftpd daemon is
running

when the ftpd daemon receives an upload, it verifies the integrity, and
saves it in /var

The ftpd daemon then sends a HUP signal to init

because inittab contains the line: ::restart:/linuxex, init kills all
running processes and exec's /linuxex

linuxex now runs, and is the only running process on the system, linuxex
is a shell script:

/bin/umount /tmp 
/bin/umount /etc
/bin/umount /proc
/bin/cp /usr/sbin/flash /var
/bin/cp -a /dev/nftla /var/out
/bin/cp -a /dev/ttyS0 /var
cd /var
/bin/ln -s flash chroot
/bin/mkdir old
echo pivot root to var... 
pivot_root . old 
exec ./chroot . ./flash

so now flash is the only program running, and its statiacally linked, so
there are no more references to the cramfs root, and it can be umounted
by flash. flash ten proceeds to flash the image, and reset the machine.

------

so as you can see, there is no pseudo single user mode required, and the
flash image is received while the system is up and fully operational. As
soon as the image is received and verified, the system basically goes
down for a reboot, during which the new image is flashed.

  reply	other threads:[~2002-06-20  1:48 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
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 [this message]
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=1024537429.1088.17.camel@timmy \
    --to=russ.dill@asu.edu \
    --cc=catlee@canada.com \
    --cc=cfowler@outpostsentinel.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