public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Werner Almesberger <wa@almesberger.net>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andrew Morton <akpm@osdl.org>,
	fastboot@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] Re: [PATCH 0/29] overview
Date: Thu, 20 Jan 2005 18:34:35 -0300	[thread overview]
Message-ID: <20050120183435.C21510@almesberger.net> (raw)
In-Reply-To: <m1is5r502d.fsf@ebiederm.dsl.xmission.com>; from ebiederm@xmission.com on Thu, Jan 20, 2005 at 01:15:38PM -0700

Eric W. Biederman wrote:
> The hard one there is support of arbitrary OS's.

Bah, couldn't care less :-) If all else fails, you can fall back
to the "old-style" boot loader, and let this one boot the legacy
OS. (Well, for GRUB, you'd need the fallback extension, if this
isn't a standard feature yet.)

> Most people want to implement simple boot policies,
> and really don't care for the full complexity that some firmware
> solutions allow.  So what I have seen is people will take kexec
> and implement their custom policy instead of doing something complex.

I think many of them would just be as happy with a more complex
solution, as long as it comes in a nice bundle. Of course, if
there is no nice package to start from, they'll only implement
the bare minimum.

Also, in most cases, we can probably ignore space issues for now,
leave some room for experiments, and optimize later.

> The goal
> now is to build enough confidence so that we can move from the
> development to the stable kernel.

Yes, that's what I mean with it being in "mainline". For user
space to begin making use of kexec, it really should be part of
a kernel most people can accept for regular use.

> Want to help?

Trying to, by explaining why it should move on :-) Anything else
you need ?

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

      reply	other threads:[~2005-01-20 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050120102223.B14297@almesberger.net>
2005-01-20 19:00 ` [Fastboot] Re: [PATCH 0/29] overview Eric W. Biederman
2005-01-20 19:51   ` Werner Almesberger
2005-01-20 20:15     ` Eric W. Biederman
2005-01-20 21:34       ` Werner Almesberger [this message]

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=20050120183435.C21510@almesberger.net \
    --to=wa@almesberger.net \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --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