All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian Ludwig" <cl81@gmx.net>
To: "Daniel Phillips" <phillips@arcor.de>,
	"Ville Herva" <vherva@niksula.hut.fi>
Cc: "Linux Kernel Mailinglist" <linux-kernel@vger.kernel.org>
Subject: Re: bzip2 support against 2.4.18
Date: Fri, 12 Jul 2002 08:36:41 +0200	[thread overview]
Message-ID: <000901c2296e$7cab2ed0$1c6fa8c0@hyper> (raw)
In-Reply-To: E17SheA-0002Uh-00@starship

On 11.07.2001 - 19:21 Daniel Phillips wrote:
> How about bz2Image, or, more natural in my mind, bz2linux.

bzImage stands for "big zipped Image". Zipped, in this case, means that it
is gzipped. Perhaps Linus never wants to support other compression formats
for the kernel.
Sure "bz2bzImage" is a bit ugly. I personally would prefer bzImage.bz2,
although it is some kind of self-extracting executable, thus *.bz2 is also
not correct. But it would imply better which sort of compression you are
using. But that also means that the standard kernel has to be called
"bzImage.gz". I did not want to mess up the standard names...

But the question is: who is responsible for all those naming conventions?
Does anyone has an idea?

Have fun,

    - Christian



  reply	other threads:[~2002-07-12  6:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10 13:57 bzip2 support against 2.4.18 Christian Ludwig
2002-07-10 15:54 ` bzip2 patent status query jbradford
2002-07-10 16:48   ` Albert D. Cahalan
2002-07-10 17:37     ` jbradford
2002-07-10 17:08   ` Alan Cox
2002-07-10 17:26   ` Mark Mielke
2002-07-10 21:11   ` Rik van Riel
2002-07-12  7:04     ` Christian Ludwig
     [not found] ` <20020711062832.GU1548@niksula.cs.hut.fi>
2002-07-11  7:21   ` bzip2 support against 2.4.18 Christian Ludwig
2002-07-11 17:22     ` Daniel Phillips
2002-07-12  6:36       ` Christian Ludwig [this message]
2002-07-12  7:30         ` Daniel Phillips
2002-07-12  8:32           ` Christian Ludwig
2002-07-12  8:52             ` Daniel Phillips
2002-07-12 10:12               ` Christian Ludwig
2002-07-12 12:01                 ` jw schultz
2002-07-12 14:25               ` Tom Oehser
2002-07-12 14:49                 ` Mark Mielke
2002-07-15 21:31             ` Horst von Brand
2002-07-16 12:01               ` Tom Oehser
2002-07-12 12:37           ` Thunder from the hill
2002-07-13 13:56           ` john slee
2002-07-13 14:04             ` Daniel Phillips
2002-07-13 15:02               ` Tomas Szepe
2002-07-13 14:44             ` Thunder from the hill
2002-07-12 12:33         ` Thunder from the hill
2002-07-12 13:05         ` jbradford
2002-07-12 13:24         ` Mark Mielke
2002-07-12 13:49           ` Christian Ludwig
2002-07-12 14:21         ` Tom Oehser
2002-07-15  6:28           ` Christian Ludwig
2002-07-15 12:17             ` Tom Oehser
2002-07-16  8:28               ` [PATCH] bzip2 compression for kernel 2.4 and ramdisk Christian Ludwig
2002-07-13  5:16       ` bzip2 support against 2.4.18 Mike Touloumtzis

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='000901c2296e$7cab2ed0$1c6fa8c0@hyper' \
    --to=cl81@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@arcor.de \
    --cc=vherva@niksula.hut.fi \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.