From: kaih@khms.westfalen.de (Kai Henningsen)
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: is KERNEL developement finished, yet ???
Date: 07 Dec 2002 22:34:00 +0200 [thread overview]
Message-ID: <8bPzdF91w-B@khms.westfalen.de> (raw)
In-Reply-To: <aso4kq$2ka$1@penguin.transmeta.com>
torvalds@transmeta.com (Linus Torvalds) wrote on 05.12.02 in <aso4kq$2ka$1@penguin.transmeta.com>:
> In article <000901c29c5d$6d194760$2e833841@joe>,
> Joseph D. Wagner <wagnerjd@prodigy.net> wrote:
> >
> >Unix (and Linux) developers are far too concerned with clinging to the
> >30-year-old outdated POSIX standard, which creates numerous problems when
> >trying to advance new features.
>
> No.
>
> Only stupid people think they should throw away old proven concepts.
> What happens quite often in academia in particular is that you find a
> problem you want to fix, and you re-design the whole system around your
> fix.
Well, yes and no.
Yes, it's usually a bad idea to do that and expect to get a production-
level kernel out of it.
But on the other hand, there's a lot that *could* be done with OS kernels
that has never been tried (even though I certainly couldn't give a list).
Until someone implements one of those ideas, and experiments with the
results for a while, it's impossible to know what it would be worth in
practice. (I certainly wouldn't want to trust a theoretical evaluation!)
Then, *if* it looks good in an experimental OS, people still need to
figure out how to make use of it in a more traditional kernel. Sometimes
that's where it breaks. Sometimes not.
If you just remember that academic OSes are *research*, not production
material, then they are fine. Unfortunately, too many people (including
many academics) forget that.
There's a reason we have both science and engineering, and they're not the
same discipline.
MfG Kai
next prev parent reply other threads:[~2002-12-07 22:27 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 2:00 is KERNEL developement finished, yet ??? Ed Vance
2002-12-05 12:24 ` Shane Helms
2002-12-05 12:54 ` Joseph D. Wagner
2002-12-05 13:15 ` Andreas Schwab
2002-12-05 18:07 ` Linus Torvalds
2002-12-05 19:52 ` Shane Helms
2002-12-05 20:03 ` Linus Torvalds
2002-12-05 20:09 ` is KERNEL developement finished, yet ??? (ACLs) Tupshin Harper
2002-12-06 10:38 ` Jakob Oestergaard
2002-12-15 5:29 ` Tracy R Reed
2002-12-07 20:34 ` Kai Henningsen [this message]
2002-12-05 18:09 ` is KERNEL developement finished, yet ??? Alan Cox
2002-12-05 17:47 ` yodaiken
2002-12-05 19:08 ` John Bradford
2002-12-06 6:15 ` Joseph D. Wagner
2002-12-06 6:30 ` John Alvord
2002-12-06 9:48 ` Alvaro Lopes
2002-12-07 20:43 ` Kai Henningsen
2002-12-07 20:39 ` Kai Henningsen
2002-12-09 14:08 ` Jesse Pollard
2002-12-10 0:26 ` H. Peter Anvin
2002-12-05 14:33 ` Mikael Pettersson
[not found] <sdef301b.011@mail-01.med.umich.edu>
2002-12-05 16:36 ` Joseph D. Wagner
2002-12-06 3:29 ` Keith Adamson
[not found] <sdef2367.029@mail-02.med.umich.edu>
2002-12-05 15:17 ` Joseph D. Wagner
2002-12-05 15:38 ` Dave Jones
2002-12-05 15:44 ` Eric Weigle
-- strict thread matches above, loose matches on Subject: below --
2002-12-05 14:58 Nicholas Berry
2002-12-03 13:03 cs driver SANTHOSH K
2002-12-04 15:26 ` is KERNEL developement finished, yet ??? Shane Helms
2002-12-04 17:01 ` Joseph D. Wagner
2002-12-04 18:38 ` Alan Cox
2002-12-04 18:07 ` Richard B. Tilley (Brad)
2002-12-04 18:21 ` Richard B. Johnson
2002-12-04 18:39 ` Erik Andersen
2002-12-05 16:59 ` Bill Davidsen
2002-12-05 0:27 ` jeff millar
2002-12-05 23:55 ` Frank van Maarseveen
2002-12-06 0:24 ` Shane Helms
2002-12-06 3:00 ` jeff millar
2002-12-06 3:36 ` Miles Bader
2002-12-06 8:55 ` Helge Hafting
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=8bPzdF91w-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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