From: Peter Samuelson <peter@cadcamlab.org>
To: infernix <infernix@infernix.nl>
Cc: Niels Kristian Bech Jensen <nkbj@image.dk>,
"Linux kernel developer's mailing list"
<linux-kernel@vger.kernel.org>
Subject: Re: Unable to boot 2.4.0-test12 (0224 AX:0212 BX:BC00 CX:5101 DX:000.)
Date: Sat, 16 Dec 2000 17:25:18 -0600 [thread overview]
Message-ID: <20001216172518.M3199@cadcamlab.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0012160521580.2805-100000@hafnium.nkbj.dk> <Pine.LNX.4.21.0012161651390.5677-100000@server.ggmc.nl>
In-Reply-To: <Pine.LNX.4.21.0012161651390.5677-100000@server.ggmc.nl>; from infernix@infernix.nl on Sat, Dec 16, 2000 at 04:56:07PM +0100
[infernix]
> I found the cause. I read somewhere in a debian bugreport that
> bootsect.S can't handle really big (b)vmlinuz images (over 500kb
> orso). However, I am wondering why 'make bzdisk' doesn't give me an
> error or a warning.
As someone (Jeff Garzik?) was saying a week or two ago, can we please
kill the x86 boot sector already? With today's kernels, 'over 500k or
so' is probably the common case. Is there *anything* the builtin code
can do better than syslinux?
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-16 23:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 1:01 infernix
2000-12-16 4:22 ` Niels Kristian Bech Jensen
2000-12-16 10:06 ` Jens Müller
2000-12-16 15:56 ` infernix
2000-12-16 23:25 ` Peter Samuelson [this message]
2000-12-17 0:19 ` Alan Cox
2000-12-17 1:20 ` Peter Samuelson
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=20001216172518.M3199@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=infernix@infernix.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=nkbj@image.dk \
/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
all inboxes | Powered by JetHome®