From: "Joseph D. Wagner" <wagnerjd@prodigy.net>
To: "'Shane Helms'" <shanehelms@eircom.net>, <linux-kernel@vger.kernel.org>
Subject: RE: is KERNEL developement finished, yet ???
Date: Wed, 4 Dec 2002 11:01:45 -0600 [thread overview]
Message-ID: <001901c29bb6$d4f98270$6c873841@joe> (raw)
In-Reply-To: <200212041526.57501.shanehelms@eircom.net>
> My question is, is there, yet, any area at this low
> level to be discovered and developed on ? or as most
> ppl say, are the interesting parts over and it's just
> now into patches, bugs and slight
> enhancements/optimizations/securities ?
Ha ha ha. Kernel development over. That's rich. I can't speak for the
Linux kernel developers; they're a vindictive group (and the "to-do"
list of their vision for future kernel development is no where to be
found).
However, I know Mach and GNU Hurd, which are both microkernels, have
plenty of room for low-level pioneers.
Personally, I think the most interesting aspects of kernel development
and research are taking place on microkernels.
> need to know, whether it's worth going into Computer
> Architecture Group as my main career, or shall I stir
> towards a another area like networking which is still
> in developement, and plenty of jobs (but not as
> interssting as kernel/OS programming) ?????
Do both. Or, ask yourself this: Would I rather do something I love and
risk being unemployed, or have plenty of job security with only
moderately entertaining tasks? It's up to you, and maybe the job market
for kernel development isn't that bad.
Another aspect of computer science you might want to consider is
compilers; that's always low level, and they may need those people for
all those hand- held devices.
Joseph Wagner
next prev parent reply other threads:[~2002-12-04 16:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2002-12-05 2:00 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-07 20:34 ` 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
2002-12-05 14:58 Nicholas Berry
[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
[not found] <sdef301b.011@mail-01.med.umich.edu>
2002-12-05 16:36 ` Joseph D. Wagner
2002-12-06 3:29 ` Keith Adamson
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='001901c29bb6$d4f98270$6c873841@joe' \
--to=wagnerjd@prodigy.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shanehelms@eircom.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