From: john slee <indigoid@higherplane.net>
To: Daniel Phillips <phillips@arcor.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bzip2 support against 2.4.18
Date: Sat, 13 Jul 2002 23:56:02 +1000 [thread overview]
Message-ID: <20020713135602.GK7579@higherplane.net> (raw)
In-Reply-To: <E17Suso-0002dn-00@starship>
On Fri, Jul 12, 2002 at 09:30:29AM +0200, Daniel Phillips wrote:
> Actually, what is the use of even including 'bz2' in the name? Nobody
> besides we geeks needs to know the thing is compressed with bzip2. It
> would be nice to see the word 'linux' in there. How about bzlinux?
> Just think of the hundreds of cases of carpal tunnel syndrome you'd
> prevent by eliminating the shifted character.
why not just call it 'linux'? file(1) exists for a reason, and the 'vm'
prefix is a bit redundant these days
also i've never really understood why the binary format of the kernel is
selected via make. why not just make it a regular kernel option with a
sane default? surely your average kernel compiling person picks
something that works (zImage? bzImage? Image?) and sticks to it...
j.
--
toyota power: http://indigoid.net/
next prev parent reply other threads:[~2002-07-13 13:50 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
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 [this message]
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=20020713135602.GK7579@higherplane.net \
--to=indigoid@higherplane.net \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
/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