From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Unable to boot a raw kernel image :??
Date: 6 Mar 2003 12:28:05 -0800 [thread overview]
Message-ID: <b48b0l$5rl$1@cesium.transmeta.com> (raw)
In-Reply-To: 15975.8192.437452.801287@gargle.gargle.HOWL
Followup to: <15975.8192.437452.801287@gargle.gargle.HOWL>
By author: Mikael Pettersson <mikpe@user.it.uu.se>
In newsgroup: linux.dev.kernel
>
> Indeed. The SYSLINUX 2.02 + mtools combination works like a charm
> for 'make bzdisk'. I'm happy with your nobootsect patch.
>
Well, Linus keeps dropping it on the floor, so I don't know if we'll
see a working "make bzdisk" in the kernel any time soon :(
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-03-06 20:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 13:21 Unable to boot a raw kernel image :?? DervishD
2002-12-03 11:29 ` Denis Vlasenko
2002-12-08 10:33 ` DervishD
2002-12-06 11:45 ` Edgar Toernig
2002-12-08 10:36 ` DervishD
2003-03-05 15:00 ` H. Peter Anvin
2003-03-05 15:33 ` Mikael Pettersson
2003-03-05 15:47 ` H. Peter Anvin
2003-03-05 15:58 ` Mikael Pettersson
2003-03-05 16:02 ` H. Peter Anvin
2003-03-05 16:05 ` Mikael Pettersson
2003-03-06 10:16 ` Mikael Pettersson
2003-03-06 20:28 ` H. Peter Anvin [this message]
2003-03-09 10:31 ` DervishD
2003-03-10 19:38 ` H. Peter Anvin
2003-03-11 9:23 ` DervishD
2003-03-05 16:12 ` DervishD
2003-03-05 16:33 ` John Bradford
2003-03-05 16:48 ` H. Peter Anvin
2003-03-05 16:55 ` John Bradford
2003-03-05 17:01 ` DervishD
2003-03-05 18:04 ` John Bradford
2003-03-05 16:51 ` H. Peter Anvin
2003-03-05 17:04 ` DervishD
2003-03-05 17:51 ` H. Peter Anvin
2003-03-06 1:08 ` Alan Cox
2003-03-06 0:30 ` H. Peter Anvin
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='b48b0l$5rl$1@cesium.transmeta.com' \
--to=hpa@zytor.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;
as well as URLs for NNTP newsgroup(s).