From: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
To: Dave Jones <davej@codemonkey.org.uk>,
Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: lkml, bugme.osdl.org?
Date: Wed, 4 Dec 2002 11:58:19 +0000 [thread overview]
Message-ID: <20021204115819.GB1137@gallifrey> (raw)
In-Reply-To: <20021203121521.GB30431@suse.de>
* Dave Jones (davej@codemonkey.org.uk) wrote:
> - architecture xxx doesn't compile
> there's a few of these now in bugzilla, and personally I don't think
> they belong there. Any arch other than i386 is always going to be
> playing catchup, and is nearly always out of date in mainline.
Quite a few of those are from me. It is a real pity that we keep the
view of everything other than i386 is playing catch up - that really
deminishes the usefulness of Linux in a lot of fields.
Don't forget that ia64, x86-64 and s390 are all potentially growing
users of Linux. Linux on ARM, MIPS and PPC also has a healthy band of
productive (commercial and home) users.
The problem for a lot of the users of some of these architectures is that they
have to have a long hard fight to get a kernel to work on their system;
and every one of the systems has to have a different kernel version with
different oddities. The stability of these systems isn't just harmed by
the fact that less people are testing the architecture specific code but
also that they tend to be based on older original kernel trees.
In addition porting to another architecture is a great way to shake out
pointer bugs and random bugs in any code - so being able to run the main
kernel on a few architectures should help make life more stable for
everyone.
I don't expect that all the other architectures will be as well tested
as x86; but at least we should know the state of each architecture and
preferably have 2.6.x (or whatever it gets called) to basically work on
as many architectures as possible.
When Linux does work accross lots of architectures it is very, very
useful - how many other OS's can give you the same operating environment
on totally different pieces of hardware? It makes porting code very
simple and pleasent when you only have to worry about the architectural
differences and not battling between different OS.
Dave
---------------- Have a happy GNU millennium! ----------------------
/ Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2002-12-04 11:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 7:24 Valdis.Kletnieks
2002-12-03 12:15 ` Dave Jones
2002-12-03 14:13 ` bill davidsen
2002-12-03 18:09 ` Tupshin Harper
2002-12-04 11:58 ` Dr. David Alan Gilbert [this message]
2002-12-04 12:35 ` Russell King
2002-12-04 12:42 ` Dave Jones
2002-12-04 18:32 ` Dr. David Alan Gilbert
2002-12-04 22:20 ` Russell King
2002-12-05 9:15 ` David Woodhouse
2002-12-05 9:25 ` William Lee Irwin III
2002-12-05 9:34 ` David Woodhouse
2002-12-05 9:35 ` William Lee Irwin III
2002-12-05 14:24 ` bill davidsen
2002-12-03 20:33 ` Martin J. Bligh
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=20021204115819.GB1137@gallifrey \
--to=gilbertd@treblig.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=davej@codemonkey.org.uk \
--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®