From: "RaúlNúñez de Arenas Coronado" <dervishd@jazzfree.com>
To: ebiederm@xmission.com, lm@bitmover.com
Cc: dervishd@jazzfree.com, linux-kernel@vger.kernel.org
Subject: Re: LOBOS (kexec)
Date: Tue, 20 Nov 2001 13:22:28 +0100 [thread overview]
Message-ID: <E1669v2-0000Cv-00@DervishD> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
Hello Larry (or Eric) :)
>> I've been wanting Linux which can boot Linux for a long time.
>I am maintaining a version of this functionality against 2.4.x
>called kexec. And I plan to work on integration into linux with 2.5.x.
>After the details are worked out I will look at a backport to 2.4.x
I think that this is a very important point, since will ease the
making of installation disks, etc... Moreover, it will ease the
creation of 'live' linux systems that can do a pretty work detecting
the hardware and the like.
>The hard part is not linux booting linux but the passing of the
>firmware/BIOS tables from one kernel to the next.
Why?. I mean, I haven't read on this issue in the LOBOS project.
I'm afraid I thought that this was easier than it really is...
>I am doing this a part of the linuxBIOS effort and as such it is just
I want to take a look at LinuxBIOS.
Raúl
next reply other threads:[~2001-11-20 12:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 12:22 RaúlNúñez de Arenas Coronado [this message]
2001-11-20 13:40 ` LOBOS (kexec) Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2001-11-20 0:04 LOBOS RaúlNúñez de Arenas Coronado
2001-11-20 2:17 ` LOBOS Larry McVoy
2001-11-20 3:11 ` LOBOS (kexec) Eric W. Biederman
2001-11-20 5:41 ` Tim Hockin
2001-11-20 6:52 ` Eric W. Biederman
2001-11-20 23:56 ` Werner Almesberger
2001-11-21 2:53 ` Eric W. Biederman
2001-11-21 17:11 ` Randy.Dunlap
2001-11-22 6:37 ` Eric W. Biederman
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=E1669v2-0000Cv-00@DervishD \
--to=dervishd@jazzfree.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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