public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shane Helms <shanehelms@eircom.net>
To: Ed Vance <EdV@macrolink.com>, "'jeff millar'" <wa1hco@adelphia.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is KERNEL developement finished, yet ???
Date: Thu, 5 Dec 2002 12:24:50 +0000	[thread overview]
Message-ID: <200212051224.50317.shanehelms@eircom.net> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D1A33CD5@EXCHANGE>

On Thursday 05 December 2002 02:00, Ed Vance wrote:
>
> Oh, ye of little imagination.
>
> It's only polishing because the new work must merge into the
> framework imposed by the old work (un*x legacy environment).
>
> If you assume nothing about OS architecture, there are still
> huge vistas of unexplored solution space, where no one has gone
> before. It's just really hard for engineers to let go of the
> stuff that works and start climbing from the bottom of the
> mountain.
>
> cheers,

I can agree that target based OSes are becoming popular these days, and 
leading companies try to build an optimized, task specific OS for their 
particular hardware and need.

But, if you're implying that we can start once again from bottom, and come up 
with something better that unix (which has been opensource, around for long 
while, tested and developed by many as well) I _HIGHLY_ doubt, and disagree. 
This is unless main kernel developers *confess* that some incorrect design 
decisions were made at the start (at a major section or so), which now 
they're forced to comply with, and let such bugs traverse through kernel 
versions, and there is no way to remove them, unless start from scratch 
again.

I doubt there be any such errors (mistakes) if ANY. but then, i'm not a kernel 
developer, and new to this whole mailing list !!

Shane

  reply	other threads:[~2002-12-05 12:18 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 [this message]
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       ` is KERNEL developement finished, yet ??? Kai Henningsen
2002-12-05 18:09     ` 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=200212051224.50317.shanehelms@eircom.net \
    --to=shanehelms@eircom.net \
    --cc=EdV@macrolink.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wa1hco@adelphia.net \
    /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