public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: robert w hall <bobh@n-cantrell.demon.co.uk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Mike Galbraith <EFAULT@gmx.de>, Thomas Molina <tmolina@cox.net>,
	linux-kernel@vger.kernel.org
Subject: Re: loadlin with 2.5.?? kernels
Date: Fri, 25 Oct 2002 23:00:43 +0100	[thread overview]
Message-ID: <ApOnXDAL8bu9EwOR@n-cantrell.demon.co.uk> (raw)
In-Reply-To: <m1bs5in1zh.fsf@frodo.biederman.org>

which version of loadlin does this patch?
Hans Lermen changed the gdt structure in version 1.6b to enable it to
boot a win4lin-enabled kernel - he also changed things recently (1.6c)
to boot kernels of between 0.5 &1.5Mb compressed.

(IF I sat down for half an hour I could comment better.. but you
probably know the answer straight-off anyway :-))
Bob Hall


In article <m1bs5in1zh.fsf@frodo.biederman.org>, Eric W. Biederman
<ebiederm@xmission.com> writes
>"Mike Galbraith" <EFAULT@gmx.de> writes:
>
>> (sorry, I have to use this pos at work)
>> 
>> Yes.  .31 exploded on me after boot, but did not do the violent reboot
>> during boot.
>
>Earlier you had said it was .38 or so where the failures kicked in,
>so I figured it was some other problem.
> 
>> > If it is really the gdt I have some old patches that roughly do the
>> > right thing, and I just need to dust them off.
>> 
>> You dust them off, and I'll be more than happy to test them.  I keep
>> entirely too many kernels resident to want to use lilo.
>
>Here you are.
>The following patch cleans up and removes unnecessary dependencies from
>the x86 boot path.
> 
>> (kexec/bootimg wonderfulness solves my problem too.  boot into a stable
>> kernel, instant reboot into any one I want.  gimme gimme gimme:)
>
>It is getting there...
>I just need to find a formula that makes the linux kernel boot reliably.
>
>
>[ A MIME text / plain part was included here. ]
>
>
>Eric

-- 
robert w hall

  parent reply	other threads:[~2002-10-25 21:56 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 [this message]
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
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=ApOnXDAL8bu9EwOR@n-cantrell.demon.co.uk \
    --to=bobh@n-cantrell.demon.co.uk \
    --cc=EFAULT@gmx.de \
    --cc=ebiederm@xmission.com \
    --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