Talking With 2.0 Kernel Maintainer David Weinehall
Jeremy Andrews writes "While the recently released 2.6 Linux kernel is all the rage these days, the much older 2.0 kernel is still alive and kicking. KernelTrap has interviewed David Weinehall, the maintainer of the 2.0 Linux kernel. David became the 2.0 maintainer in December of 1999, after Alan Cox moved on to work full time on the 2.2 kernel. In this interview David talks about what's involved in maintaining the 2.0 kernel, who uses it, when we can expect the impending release of 2.0.40, why you should upgrade (if you're still running 2.0.39), and more."
It's like the people that still use Windows 95, sure it's not as new and flashy, but it still runs on the crappy hardware from years ago... And sometimes, that's all you need.
Still maintaining the 1.0 kernel? :)
This space is not for rent.
Isn't it great? One of the best things with free software is that anyone is free to maintain and support it for as long as they wish. Compare to say, NT 4.0, which is perfectly capable for some tasks, but users are forced to switch because MS cuts support (read: no more security updates.)
.: Max Romantschuk
Not many people realize that a lot of us in the aerospace community rely on older versions of the kernel due to its "nimbleness" for fly-by-wire systems, etc. A lot of us don't need the newer features of more recent kernels, and having something that does the bare minimum--fast-- is optimal.
We really have to be thankful that people maintain the older versions!
I've got at least a dozen production machines which have been going since Slackware 3.6, so I'm very glad to see the 2.0 kernels still being 'overseen' by someone.
The hardware is old, it works with the 2.0.x kernels, it works fast and without issues (except for exploits of course), so why bother making a radical change which might end up breaking more by moving to the latest.
There's you're answer to "who's using it"... Debian!
I have to admit, I suspected it all along...
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
Thats kinda why I find it more surprising that people use the older versions of the kernel, considering its not costing you more than a few minutes time to download the latest tarball from your local mirror, and setup a new kernel!
I think that's where you're missing the point.
The way the kernel deals with devices changed a great deal between 2.0.x and 2.2.x and even moreso for 2.4.x, if you've got some custom apps that work just fine on the hardware that you're using, what's the point in upgrading?
No risk of having to debug unforseen problems with running your app in a new environment.
If it ain't broke, don't fix it.
LK
"Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
2.6.2 has been out for several hours now ... (changelog here) - surprised /. hasn't picked this up yet. It's not like the /. editors care about hammering a site. :)
How come that such a skilled person with enough references can't find a job?
Oh crap, that's screen burn-in.
after reading his interview, it seems to me as if there are still fairly frequent problems with 2.0 relating to stability and potential security problems.
I don't recall hearing about these problems all that often with the newer 2.4; is it just my perception, or are the new kernels more soundly written than the older ones?
~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
the 2.0.x kernel is used HEAVILY in embedded systems. this is a place where it takes YEARS to get things certified safe to run by the engineers.
Can I install 2.6.1 on that system and run it? you bet I can, and with no speed loss. but I lose the knowledge that the kernel will NOT be a point of failure. Absolutely nobody can tell me the exact failure points of the 2.6 or even the 2.4 kernels. while the 2.0 kernel is completely documented and certified by the in house people here to be 99% solid. (Windows CE get's a 50% rating, a full 5% higher than windows nt,2000,xp) While QNX and BSD here are still below 80% as far as the testing people rate it... and that is what matter's to us.
Not something that a know-nothing with no credentials says in the press.... what we see in real testing over the course of a 24 month period trying to force it to fail. (Yes, even baking the board beyond operating temps...)
all this for testing a firmware for upcoming cable tv boxes and other embedded systems related to video/communication.
If a kernel maintainer can't find a programming job then the programming profession is pretty much destroyed already.