From: Michael Meissner <meissner@spectacle-pond.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Universal debug macros.
Date: Mon, 27 Nov 2000 00:19:23 -0500 [thread overview]
Message-ID: <20001127001923.B16176@munchkin.spectacle-pond.org> (raw)
In-Reply-To: <200011270045.BAA13121@cave.bitwizard.nl> <Pine.LNX.4.10.10011270302570.24716-100000@yle-server.ylenurme.sise> <8vsno2$pc6$1@cesium.transmeta.com>
In-Reply-To: <8vsno2$pc6$1@cesium.transmeta.com>; from hpa@zytor.com on Sun, Nov 26, 2000 at 08:25:38PM -0800
On Sun, Nov 26, 2000 at 08:25:38PM -0800, H. Peter Anvin wrote:
> Followup to: <Pine.LNX.4.10.10011270302570.24716-100000@yle-server.ylenurme.sise>
> By author: Elmer Joandi <elmer@ylenurme.ee>
> In newsgroup: linux.dev.kernel
> >
> > Red Hat will ship two kernels. Well, they actually ship now about 4 ones
> > or something. So they will ship 8.
> >
>
> Something RedHat & co may want to consider doing is providing a basic
> kernel and have, as part of the install procedure or later, an
> automatic recompile and install kernel procedure. It could be
> automated very easily, and on all but the very slowest of machines, it
> really doesn't take that long.
(Note, I work in the GCC group, not the Linux group, so the following is MHO,
and not Red Hat gospel).
Assuming you've installed the compiler/other relevant tools, installed the
kernel source, and have enough disk space to build the kernel. This would
screw people wanting to install Linux on their old 386/486/pentium for use as a
firewall or web server. For example, the machine I'm planning on moving a web
server to only has 2 gig of disk. Right now, I have barely enough space to
hold the compiler tools plus web pages I want to serve. If I was serving much
more content, I would probably chuck the compiler tools/kernel source.
--
Michael Meissner, Red Hat, Inc.
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: meissner@redhat.com phone: +1 978-486-9304
Non-work: meissner@spectacle-pond.org fax: +1 978-692-4482
-
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/
next prev parent reply other threads:[~2000-11-27 5:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-26 17:53 [PATCH] removal of "static foo = 0" Elmer Joandi
2000-11-26 18:36 ` Alexander Viro
2000-11-26 19:11 ` Elmer Joandi
2000-11-26 22:49 ` Rogier Wolff
2000-11-26 23:30 ` Universal debug macros Elmer Joandi
2000-11-27 0:45 ` Rogier Wolff
2000-11-27 1:11 ` Elmer Joandi
2000-11-27 4:25 ` H. Peter Anvin
2000-11-27 5:19 ` Michael Meissner [this message]
2000-11-27 16:56 ` Chmouel Boudjnah
2000-11-27 17:47 ` H. Peter Anvin
2000-11-27 17:56 ` Chmouel Boudjnah
2000-11-27 17:58 ` H. Peter Anvin
2000-11-27 18:10 ` Chmouel Boudjnah
2000-11-27 18:28 ` H. Peter Anvin
2000-11-27 18:39 ` Chmouel Boudjnah
2000-11-27 18:41 ` H. Peter Anvin
2000-11-27 21:09 ` Gerhard Mack
2000-11-27 8:35 ` Rogier Wolff
2000-11-27 14:42 ` Elmer Joandi
2000-11-27 14:59 ` Rogier Wolff
2000-11-27 15:58 ` Elmer Joandi
2000-11-28 1:34 ` Peter Samuelson
2000-11-27 16:37 ` Andrew E. Mileski
2000-11-27 17:01 ` Richard B. Johnson
2000-11-27 17:19 ` Andrew E. Mileski
2000-11-27 18:01 ` Richard B. Johnson
2000-11-27 19:55 ` Andrew E. Mileski
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=20001127001923.B16176@munchkin.spectacle-pond.org \
--to=meissner@spectacle-pond.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®