public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: RaXl NXXez de Arenas Coronado <dervishd@jazzfree.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: LOBOS (kexec)
Date: 20 Nov 2001 06:40:19 -0700	[thread overview]
Message-ID: <m1bshx5zng.fsf@frodo.biederman.org> (raw)
In-Reply-To: <E1669v2-0000Cv-00@DervishD>
In-Reply-To: <E1669v2-0000Cv-00@DervishD>

RaXl NXXez de Arenas Coronado <dervishd@jazzfree.com> writes:

>     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.

Yep it allows linux to sever a lot of very interesting roles.  Linux
doesn't act especially well as firmware (it is fairly big).  But otherwise
it does a good job.
 
> >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...

The difficulty isn't in implementation but in freezing the API.  Which
is needed if you want a solid long term approach.

> 
> >I am doing this a part of the linuxBIOS effort and as such it is just
> 
>     I want to take a look at LinuxBIOS.

The documentation is sketchy but you can look at:
http://www.linuxbios.org  and ask questions on the mailing list.

Eric

  reply	other threads:[~2001-11-20 13:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-20 12:22 LOBOS (kexec) RaúlNúñez de Arenas Coronado
2001-11-20 13:40 ` Eric W. Biederman [this message]
  -- 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=m1bshx5zng.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=dervishd@jazzfree.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