From: ebiederm@xmission.com (Eric W. Biederman)
To: Mike Galbraith <efault@gmx.de>
Cc: robert w hall <bobh@n-cantrell.demon.co.uk>,
Thomas Molina <tmolina@cox.net>,
linux-kernel@vger.kernel.org
Subject: Re: loadlin with 2.5.?? kernels
Date: 26 Oct 2002 03:24:16 -0600 [thread overview]
Message-ID: <m1vg3plfi7.fsf@frodo.biederman.org> (raw)
In-Reply-To: <5.1.0.14.2.20021026073915.00b55008@pop.gmx.net>
Mike Galbraith <efault@gmx.de> writes:
> At 11:20 PM 10/25/2002 -0600, Eric W. Biederman wrote:
> >Mike Galbraith <efault@gmx.de> writes:
> >
> > > I went back and double-checked my loadlin version, and it turned out I was
> > > actually using 1.6a due to a fat finger. Version 1.6c booted fine (only one
>
> > > kernel tested) without Eric's help. 1.6a definitely needs Eric's help to
> > boot.
> >
> >Darn. I guess the arguments for my patch may not be quite as good,
> >but I still think it may be worth while.
>
> Well, cleanup is always a pretty fine argument. Since there only seem to be two
>
> of us loadlin users, you probably didn't loose much argument wise ;-) The other
>
> loadlin user reported failure at .38, so maybe your patch is needed sometimes
> even with loadlin-1.6c. (other loadlin user listening?)
Robert thanks for your reply.
I just looked at what the loadlin 1.6c code does, and it's heuristic
is just slightly more reliable. It assumes %ds is %cs+8.... That
happens to work but there is nothing in the kernel keeping that from
being broken. So in practice it looks to be worthwhile to stabilize
this interface. So loadlin, and other bootloaders can work by design
and not by chance.
Eric
next prev parent reply other threads:[~2002-10-26 9:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-20 12:51 loadlin with 2.5.?? kernels Mike Galbraith
2002-10-20 13:17 ` Thomas Molina
2002-10-20 17:34 ` Mike Galbraith
2002-10-20 18:58 ` Thomas Molina
2002-10-21 11:28 ` Denis Vlasenko
2002-10-21 17:36 ` Mike Galbraith
2002-10-24 8:07 ` Eric W. Biederman
2002-10-24 8:26 ` Mike Galbraith
2002-10-25 12:21 ` Eric W. Biederman
2002-10-25 13:30 ` Mike Galbraith
2002-10-25 22:00 ` robert w hall
2002-10-26 4:56 ` Eric W. Biederman
2002-10-26 5:02 ` Mike Galbraith
2002-10-26 5:20 ` Eric W. Biederman
2002-10-26 5:49 ` Mike Galbraith
2002-10-26 6:32 ` Rene Blokland
2002-10-26 7:34 ` Mike Galbraith
2002-10-26 9:24 ` Eric W. Biederman [this message]
2002-10-26 10:37 ` robert w hall
2002-10-30 1:29 ` Eric W. Biederman
2002-10-31 21:24 ` robert w hall
2002-10-26 8:22 ` robert w hall
[not found] <1a9.a96af34.2ae43a18@aol.com>
2002-10-20 17:40 ` Mike Galbraith
[not found] <002f01c27c2a$d4c758a0$6400a8c0@mikeg>
2002-10-25 18:42 ` Mike Galbraith
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=m1vg3plfi7.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=bobh@n-cantrell.demon.co.uk \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@cox.net \
/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