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 16:51:50 -0300 [thread overview]
Message-ID: <20050120165150.A21510@almesberger.net> (raw)
In-Reply-To: <m1vf9s3ozr.fsf@ebiederm.dsl.xmission.com>; from ebiederm@xmission.com on Thu, Jan 20, 2005 at 12:00:08PM -0700
Eric W. Biederman wrote:
> To some extent. It is worth noting that the first 13 of my patches
> are not core functionality they are bug fixes or feature enhancements
> of code that simply have come to be associated with the work on kexec.
Good point. I didn't even think of the low-level parts of the boot
process. I'm more worried about the high-level side. Since GRUB,
not much seems to have happened. I think we should have a much
richer boot environment by now.
We're still not even at the level of functionality typically found
in the boot PROMs of classical Unix workstations, whereas I think
we should have been running circles around them for years already.
So if there was a vote to be cast for getting kexec into mainline
as quickly as possible, you'd certainly have mine :-)
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2005-01-20 19:53 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 [this message]
2005-01-20 20:15 ` Eric W. Biederman
2005-01-20 21:34 ` Werner Almesberger
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=20050120165150.A21510@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