From: "H. Peter Anvin" <hpa@transmeta.com>
To: Chmouel Boudjnah <chmouel@mandrakesoft.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org,
Mandrake Install <install@linux-mandrake.com>
Subject: Re: Universal debug macros.
Date: Mon, 27 Nov 2000 09:58:33 -0800 [thread overview]
Message-ID: <3A22A0C9.6888B08@transmeta.com> (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> <m3vgt9nykk.fsf@matrix.mandrakesoft.com> <3A229E41.B3C278E2@transmeta.com> <m3aealnvt6.fsf@matrix.mandrakesoft.com>
Chmouel Boudjnah wrote:
>
> "H. Peter Anvin" <hpa@transmeta.com> writes:
>
> > > > 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.
> > >
> > > this completely not possible to do in regard of the end-users eyes.
> > >
> >
> > Why not?
>
> slow !! end-user want to install a distribution fast !!!
>
> it need a lot to be friendly the compilation (ie: we cannot do only
> launch of make xconfig, not everyone now which options to select),
> what we can do is a detection of the module and recompile a kernel
> with the detected module for recompilation but there is too much error
> case that could not be handle.
>
It's not that slow compared to a whole distro install, although you would
of course want to do it *optionally*. You wouldn't want to get into
every single option, of course, but I thought that was obvious
(apparently not.) The drivers and stuff is the least of the problem --
there, you can use modules anyway.
-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/
next prev parent reply other threads:[~2000-11-27 18:30 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
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 [this message]
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=3A22A0C9.6888B08@transmeta.com \
--to=hpa@transmeta.com \
--cc=chmouel@mandrakesoft.com \
--cc=hpa@zytor.com \
--cc=install@linux-mandrake.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