From: "James A. Sutherland" <jas88@cam.ac.uk>
To: George Anzinger <george@mvista.com>
Cc: Horst von Brand <vonbrand@inf.utfsm.cl>,
"Jeff V. Merkey" <jmerkey@vger.timpanogas.org>,
linux-kernel@vger.kernel.org
Subject: Re: Installing kernel 2.4
Date: Wed, 8 Nov 2000 22:01:41 +0000 [thread overview]
Message-ID: <00110822033500.04252@dax.joh.cam.ac.uk> (raw)
In-Reply-To: <200011081205.eA8C5ui27838@pincoya.inf.utfsm.cl> <00110819463200.01915@dax.joh.cam.ac.uk> <3A09B856.EC897A92@mvista.com>
In-Reply-To: <3A09B856.EC897A92@mvista.com>
On Wed, 08 Nov 2000, George Anzinger wrote:
> "James A. Sutherland" wrote:
> >
> > On Wed, 08 Nov 2000, George Anzinger wrote:
> > > But, here the customer did run the configure code (he said he did not
> > > change anything). Isn't this where the machine should be diagnosed and
> > > the right options chosen? Need a way to say it is a cross build, but
> > > that shouldn't be too hard.
> >
> > Why default to incompatibility?! If the user explicitly says "I really do want
> > a kernel which only works on this specific machine as it is now, and I want it
> > to break otherwise", fine. Don't make it a default!
>
> I could go along with this. The user, however, had the default break,
> and, to my knowledge, there are no tools to diagnose the current (or any
> other) machine anywhere in the kernel. Maybe it is time to do such a
> tool with exports that the configure programs could use as defaults. My
> thought is that the tool could run independently on the target system
> (be it local or otherwise) with the results fed back to configure.
I think a default whereby the kernel built will run on any Linux-capable
machine of that architecture would be sensible - so if I grab the 2.4.0t10
tarball and build it now, with no changes, I'll be able to boot the kernel on
any x86 machine.
> (Oops, corollary to the rule that "The squeaking wheel gets the grease."
> is "S/he who complains most about the squeaking gets to do the
> greasing." I better keep quiet :)
I'm still not convinced the wheel IS squeaking - anyone got those benchmarks??
James.
-
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-08 22:05 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 23:24 davej
2000-11-07 23:37 ` Jeff V. Merkey
2000-11-07 23:47 ` Jeff V. Merkey
2000-11-07 23:59 ` Jeff V. Merkey
2000-11-08 0:51 ` David Lang
2000-11-08 0:10 ` Jeff V. Merkey
2000-11-08 3:39 ` davej
2000-11-08 4:41 ` Jeff V. Merkey
2000-11-08 3:57 ` davej
2000-11-08 12:05 ` Horst von Brand
2000-11-08 15:29 ` Eric W. Biederman
2000-11-08 16:51 ` James A. Sutherland
2000-11-08 17:36 ` George Anzinger
2000-11-08 19:43 ` James A. Sutherland
2000-11-08 20:32 ` George Anzinger
2000-11-08 22:01 ` James A. Sutherland [this message]
2000-11-09 13:25 ` David Woodhouse
2000-11-09 18:24 ` James A. Sutherland
2000-11-08 3:30 ` davej
2000-11-08 0:03 ` Jeff Garzik
2000-11-08 0:06 ` Jeff V. Merkey
2000-11-08 3:25 ` davej
2000-11-08 4:36 ` Jeff V. Merkey
2000-11-08 3:50 ` davej
-- strict thread matches above, loose matches on Subject: below --
2000-11-08 19:19 David Feuer
2000-11-08 13:49 Bruce_Holzrichter
2000-11-08 15:10 ` davej
2000-11-08 19:16 ` Jeff V. Merkey
2000-11-08 13:43 Jesse Pollard
2000-11-08 18:52 ` Jeff V. Merkey
2000-11-08 2:25 Marty Fouts
2000-11-08 3:43 ` davej
2000-11-08 2:19 Marty Fouts
2000-11-07 22:49 Bruce_Holzrichter
2000-11-07 20:52 Anil kumar
2000-11-07 20:59 ` Jeff V. Merkey
2000-11-07 21:39 ` Tigran Aivazian
2000-11-07 22:28 ` Martin Josefsson
2000-11-07 22:32 ` Jeff V. Merkey
2000-11-07 22:51 ` kernel
2000-11-07 23:10 ` Jeff V. Merkey
2000-11-07 23:57 ` Jeff Garzik
2000-11-08 0:01 ` Jeff V. Merkey
2000-11-08 0:10 ` Jeff Garzik
2000-11-08 0:12 ` Jeff V. Merkey
2000-12-10 8:22 ` Mark W. McClelland
2000-11-09 13:40 ` Alan Cox
2000-11-08 2:18 ` H. Peter Anvin
2000-11-08 7:35 ` Jeff V. Merkey
2000-11-08 0:54 ` Alan Cox
2000-11-08 3:31 ` Matthew Kirkwood
2000-11-08 0:11 ` David Lang
2000-11-07 23:39 ` Jeff V. Merkey
2000-11-07 23:51 ` Sven Koch
2000-11-07 23:59 ` Jeff Garzik
2000-11-08 0:18 ` David Relson
2000-11-08 0:23 ` Jeff V. Merkey
2000-11-08 0:50 ` Jeff Garzik
2000-11-08 0:52 ` Jeff V. Merkey
2000-11-08 0:49 ` Alan Cox
2000-11-08 0:47 ` Jeff V. Merkey
2000-11-08 0:57 ` Alan Cox
2000-11-08 0:54 ` Jeff V. Merkey
2000-11-07 22:52 ` J . A . Magallon
2000-11-07 22:54 ` J Sloan
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=00110822033500.04252@dax.joh.cam.ac.uk \
--to=jas88@cam.ac.uk \
--cc=george@mvista.com \
--cc=jmerkey@vger.timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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®