From: jbradford@dial.pipex.com
To: linux-kernel@vger.kernel.org
Subject: Re: Recoverable RAM Disk
Date: Wed, 10 Jul 2002 12:16:12 +0100 (BST) [thread overview]
Message-ID: <200207101116.MAA02504@darkstar.example.net> (raw)
In-Reply-To: <p04320407b950a89e4fc4@[192.168.3.11]> from "Christian Jaeger" at Jul 09, 2002 09:07:18 PM
Looks interesting for saving debug info between re-boots, but I was thinking more of reserving an area at the top of system memory, (say 4 megs), and putting a root filesystem, and some kernel images there.
The theory being that if you haven't got a hard disk, (e.g. nodes of a beowulf cluster), doing a warm boot to change kernels is 'expensive', because you're either booting from a floppy over the LAN.
Alternatively, you could preserve the in-memory filesystem cache between re-boots, (although why anyone should be re-booting that much, I don't know).
> I've recently stumbled about this:
> http://oss.missioncriticallinux.com/projects/mcore/
>
> Maybe that's about what you're looking for.
next parent reply other threads:[~2002-07-10 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <p04320407b950a89e4fc4@[192.168.3.11]>
2002-07-10 11:16 ` jbradford [this message]
2002-09-02 23:48 Recoverable RAM disk jbradford
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 16:19 Recoverable RAM Disk jbradford
2002-07-09 16:40 ` Chris Friesen
2002-07-09 17:24 ` Roy Sigurd Karlsbakk
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=200207101116.MAA02504@darkstar.example.net \
--to=jbradford@dial.pipex.com \
--cc=linux-kernel@vger.kernel.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