From: Brian Gerst <bgerst@didntduck.org>
To: Wakko Warner <wakko@animx.eu.org>
Cc: Rick Warner <rick@microway.com>, linux-kernel@vger.kernel.org
Subject: Re: zImage on 2.6?
Date: Tue, 03 May 2005 14:44:52 -0400 [thread overview]
Message-ID: <4277C6A4.3070409@didntduck.org> (raw)
In-Reply-To: <20050503164012.GE11937@animx.eu.org>
Wakko Warner wrote:
> Please keep me CCd
>
> Rick Warner wrote:
>
>>On Monday 02 May 2005 09:29 pm, Wakko Warner wrote:
>>
>>>Is it possible to use zImage on 2.6 kernels or is bzImage required?
>>
>>Why do you need the zImage anyway? Maybe there is another way around the
>>problem you are having. Can you post what you are trying to do (end goal) ?
>
>
> This is a little project I'm doing to beable to load a system onto a hard
> drive. The linux system is short lived by design and will run out of a
> tmpfs root populated by various tgz files found either on CDs or a USB
> stick.
>
> My goal (which I realize may not be achivable nor is it important in the
> long run) is to get the kernel and the initrd onto a single floppy disk
> (Currently, I'm ~80kb too large for this).
>
> I decided (remembering 2.2 days and prior when zImage was normally used) to
> try zImage to see what happened. I was going to compare the size of the
> resulting images. That's when I hit the problem.
>
> I understand that upx can compress the kernel better and I also remember
> hearing about utilizing bzip2 as the compressor for the kernel and initrd
> images.
>
> As far as my question, it still stands. Is bzImage required (i386/x86) for
> a 2.6 kernel?
>
More or less yes. As you're finding out, it's very difficult to build a
functioning 2.6 kernel that fits the size requirements of the zImage
format. Really, the zImage format is not needed anymore. It was only
kept around because a small number of ancient BIOSes failed to load the
bzImage format with the now defunct floppy boot block. There is no size
difference in the resulting zImage or bzImage, only the load address is
different.
--
Brian Gerst
next prev parent reply other threads:[~2005-05-03 18:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 1:29 zImage on 2.6? Wakko Warner
2005-05-03 2:35 ` Randy.Dunlap
2005-05-03 10:45 ` Wakko Warner
2005-05-03 14:26 ` Randy.Dunlap
2005-05-03 16:33 ` Wakko Warner
2005-05-03 16:59 ` Randy.Dunlap
2005-05-03 22:19 ` Wakko Warner
2005-05-03 22:27 ` segin
2005-05-03 22:31 ` Wakko Warner
2005-05-03 23:15 ` segin
2005-05-04 0:28 ` shogunx
2005-05-04 1:29 ` Wakko Warner
2005-07-12 4:55 ` H. Peter Anvin
2005-05-03 22:37 ` Randy.Dunlap
2005-05-03 23:05 ` Wakko Warner
2005-05-03 23:16 ` Randy.Dunlap
2005-07-12 4:54 ` H. Peter Anvin
2005-05-03 18:28 ` Krzysztof Halasa
2005-07-12 4:58 ` H. Peter Anvin
2005-05-03 16:06 ` Rick Warner
2005-05-03 16:40 ` Wakko Warner
2005-05-03 18:01 ` Lennart Sorensen
2005-05-03 18:44 ` Brian Gerst [this message]
2005-05-03 22:20 ` Wakko Warner
2005-05-03 21:42 ` Rick Warner
2005-05-03 22:23 ` Wakko Warner
2005-07-12 5:00 ` H. Peter Anvin
2005-05-04 13:50 ` Wakko Warner
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=4277C6A4.3070409@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rick@microway.com \
--cc=wakko@animx.eu.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