linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Huber <huber@alum.wpi.edu>
To: Grant Erickson <erick205@umn.edu>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Solutions for Fast Software Upgrade in Linux/PPC
Date: Wed, 26 Sep 2001 11:51:17 -0400	[thread overview]
Message-ID: <87n13idk7e.fsf@mclinux.com> (raw)
In-Reply-To: <Pine.SOL.4.20.0109251001370.4999-100000@garnet.tc.umn.edu> (Grant Erickson's message of "Tue, 25 Sep 2001 10:38:15 -0500 (CDT)")


Grant Erickson <erick205@umn.edu> writes:

[snip]

I'd also recommend the fast-reboot option, but since no one mentioned
yet I'll suggest Werner Almsberger's bootimg utility.

Take a look at:
<URL:ftp://icaftp.epfl.ch/pub/people/almesber/misc/>

specifically, bootimg-current.tar.gz

Also, in ../booting/ there is a paper describing the
method. (bootinglinux-current.ps.gz)

I've tested this many times (we use it at Mission Critical for our
kernel crash dump system), and if you're looking for fast reboots this
is the way to go.

Unfortunately, it doesn't solve the upgrading of the ROM issue.

For the lazy who don't want to look at the references, what this
allows you to do is boot a linux kernel, using an already loaded Linux
kernel.

ttyl,
--
Josh Huber

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-09-26 15:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-25 15:38 Solutions for Fast Software Upgrade in Linux/PPC Grant Erickson
2001-09-25 15:42 ` Mark Hatle
2001-09-25 15:48   ` Jim Thompson
2001-09-25 16:22 ` Peter Desnoyers
2001-09-26 15:51 ` Josh Huber [this message]
2001-09-26 22:53   ` Magnus Damm
2001-09-26 15:52 ` Josh Huber

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=87n13idk7e.fsf@mclinux.com \
    --to=huber@alum.wpi.edu \
    --cc=erick205@umn.edu \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).