All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shane Helms <shanehelms@eircom.net>
To: linux-kernel@vger.kernel.org
Subject: is KERNEL developement finished, yet ???
Date: Wed, 4 Dec 2002 15:26:57 +0000	[thread overview]
Message-ID: <200212041526.57501.shanehelms@eircom.net> (raw)
In-Reply-To: <F6E1228667B6D411BAAA00306E00F2A51539BA@pdc2.nestec.net>

I'd like most of you to answer the following question, that includes even 
Linus.

I love C programming at low level (ie kernel, embedded, etc) and i'm seriously 
good at it. But don't know whether I should persue it as my main Career or 
just as an Interest. 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 ?

I'm starting a Post-Graduate studies at April, and 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) ?????

please reply, and if in favor of kernel developement, try to name some areas 
where there yet relies hope.

Thanks,

Shane

  reply	other threads:[~2002-12-04 15:20 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 ` Shane Helms [this message]
2002-12-04 17:01   ` is KERNEL developement finished, yet ??? 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
  -- 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=200212041526.57501.shanehelms@eircom.net \
    --to=shanehelms@eircom.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.