From: Anton Blanchard <anton@samba.org>
To: Tom Gall <tom_gall@vnet.ibm.com>
Cc: Samium Gromoff <_deepfire@mail.ru>, linux-kernel@vger.kernel.org
Subject: Re: is bzImage container large enough?
Date: Sun, 2 Sep 2001 09:49:11 +1000 [thread overview]
Message-ID: <20010902094911.A6041@krispykreme> (raw)
In-Reply-To: <22500.999376181@ocs3.ocs-net> <3B914805.F9883E5E@vnet.ibm.com>
In-Reply-To: <3B914805.F9883E5E@vnet.ibm.com>
> The bug we fixed was that an uncompressed
> kernel could only be up to 4 meg in size, if it was larger, at
> uncompression time you'd just lose everything past the 4M mark.
> Todd Inglett raised the limit to 8 meg for us, and that's a mighty
> large penguin....
Computing the size at link time is neater and this is what he actually
does.
Anton
next prev parent reply other threads:[~2001-09-01 23:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-01 16:28 is bzImage container large enough? Samium Gromoff
2001-09-01 20:29 ` Keith Owens
2001-09-01 20:41 ` Tom Gall
2001-09-01 23:49 ` Anton Blanchard [this message]
2001-09-01 20:42 ` Mike Castle
2001-09-01 20:49 ` Keith Owens
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=20010902094911.A6041@krispykreme \
--to=anton@samba.org \
--cc=_deepfire@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=tom_gall@vnet.ibm.com \
/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