public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Max Inux <maxinux@bigfoot.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: bzImage ~ 900K with i386 test11-pre2
Date: Sat, 11 Nov 2000 12:08:00 -0800	[thread overview]
Message-ID: <3A0DA720.990C4927@transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0011110323020.10847-100000@shambat>

Max Inux wrote:
> 
> >gzip, actually.  I can verify here "make bzImage" does the expected thing
> >and it looks normal-sized to me.
> 
> I believe there is zImage (gzip) and bzImage (bzip2). (Or is it compress
> vs gzip, but then why bzImage vs gzImage?)
> 

b is "big".  They are both gzip compressed.  zImage has a size limit
which bzImage doesn't.  zImage is pretty much obsolete.

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
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/

  parent reply	other threads:[~2000-11-11 20:08 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-10 23:37 bzImage ~ 900K with i386 test11-pre2 Robert Lynch
2000-11-10 23:47 ` H. Peter Anvin
2000-11-11  2:25   ` Max Inux
2000-11-11  3:03     ` H. Peter Anvin
2000-11-11  5:28       ` Chmouel Boudjnah
2000-11-11 11:27       ` Max Inux
2000-11-11 11:28         ` Jan Niehusmann
2000-11-11 11:38         ` bzImage ~ 900K with i386 test11-pre2, I stand corrected Max Inux
2000-11-11 13:49         ` bzImage ~ 900K with i386 test11-pre2 James A. Sutherland
2000-11-11 20:08         ` H. Peter Anvin [this message]
2000-11-11 11:36       ` Tigran Aivazian
2000-11-11 11:38         ` Tigran Aivazian
2000-11-11 11:52         ` Max Inux
2000-11-11 14:42         ` Andrea Arcangeli
2000-11-11 14:51           ` Tigran Aivazian
2000-11-11 16:26             ` Andrea Arcangeli
2000-11-11 16:46               ` Tigran Aivazian
2000-11-11 18:47                 ` Andrea Arcangeli
2000-11-11 19:35                 ` Eric W. Biederman
2000-11-12 11:29                   ` Andrea Arcangeli
2000-11-12 13:14                     ` Eric W. Biederman
2000-11-12 15:37                       ` Andrea Arcangeli
2000-11-12 15:44                         ` Andi Kleen
2000-11-12 16:33                           ` Andrea Arcangeli
2000-11-12 18:57                         ` Eric W. Biederman
2000-11-12 19:33                           ` Andi Kleen
2000-11-16 17:43                             ` Eric W. Biederman
2000-11-12 22:30                           ` Andrea Arcangeli
2000-11-12 19:20                         ` Eric W. Biederman
2000-11-12 23:03                           ` Andrea Arcangeli
2000-11-11 20:09         ` H. Peter Anvin
2000-11-12 16:22           ` Andrea Arcangeli
2000-11-11 16:05       ` Andrzej Krzysztofowicz
2000-11-11 17:27         ` Jeff Garzik
2000-11-14 14:02         ` Werner Almesberger
2000-11-11  5:47 ` Peter Samuelson
2000-11-11 14:30   ` Andi Kleen
2000-11-11 15:43     ` Thomas Köhler
2000-11-11 18:03     ` Robert Lynch
2000-11-11 18:30       ` Andi Kleen
2000-11-11 18:57         ` Robert Lynch
2000-11-11 20:35           ` Andi Kleen

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=3A0DA720.990C4927@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxinux@bigfoot.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