Alan Cox Leaves Red Hat
ruphus13 writes "Alan Cox — one of the lead Linux kernel developers at Red Hat — is leaving the company after 10 years and is heading to Intel, where he can focus on more low-level development tasks. Some are speculating whether this is indicative of a shift to a more 'application-centric' vision at Red Hat. From the article: 'Red Hat is integrating more application related, user- and enterprise-centric tools into its well-established "low-level," "core" development and support tools. It'd be more worrisome if Red Hat neglected to strike out in this direction. Cox was with Red Hat for ten years, and regardless of any suspected change of course within the company, that's a fair amount of time.'"
Did You Know? After maintaining a vow of silence for almost 10 years, Red Hat Linux founder Marc Ewing now freely admits that he named Red Hat Linux after Limp Bizkit frontman Fred Durst's trademark red New York Yankees baseball cap.
Durst and Ewing met in Ewing's hometown of Raleigh, North Carolina (Durst was raised in Gastonia, NC), where they became fast friends, sharing the same passion for low-level system programming.
Durst collaborated with Ewing on the first preview beta of Red Hat Linux before the demands of his rocketing stardom forced him to abandon his hobby and tour with his band.
Durst's position on the development team was filled by Damien Neil, and not many know of his contribution to the popular Linux distribution; however, a google search through the source code on Redhat.com (http://www.google.com/search?q=wfd+site:redhat.com) reveals many snippets of code authored by 'wfd', Durst's initials (William Frederick Durst).
Durst asked Ewing to keep his 'geeky' roots a secret as it would not lend itself to Durst's bad boy image, but as Ewing points out, it was "only a matter of time" before the origins of his NASDAQ-100 company's name were uncovered.
Where does there always have to be speculation, from completely uninformed people? From my little knowledge of Alan Cox, from mailing lists, he always seems like the kind of guy who likes the lower-level details, and I imagine that few companies will be more interested in tweaking and improving the low levels than Intel. If they saw his obvious talent, and offered him a better job at better pay, then why not move? Alan Cox leaving Redhat doesn't have to say anything bad about them, maybe it says something good about Intel, and the things they are getting more involved in?
Combination - fun iPhone puzzling
Well, that makes sense. Red Hat got rid of Durst and hired Alan Cox because they figured it was better to have a hardcore Cox than a Limp Bizkit!
My blog
If the Intel position allows Cox to do more of the type of development that interests him, or simply offers a different view from the cafeteria windows...
As an Intel employee, I have to say that if you're choosing to work at Intel for the view or the cafeteria, you have made an incredibly poor life choice.
When you look at it, Red Hat is the wrong place to develop drivers. They should be developed by the vendors of the drivers, not the O/S packager.
It has been necessary so far to develop drivers at Red Hat simply to bootstrap the O/S. But now, Linux is becoming more popular every year, most enterprises have plans to deploy Linux in annually increasing scopes, and the "upward spiral" that Bill Gates (ghost-)wrote about 10 years ago in "The Road Ahead" is happening for the GNU/Linux system.
Red Hat doesn't develop devices. Device vendors develop devices, and it's their expertise in how their own devices function that makes them best qualified to write device drivers for the whatever O/S.
This move is really more a reflection of the continuing maturity of the Linux Operating System!
I have no problem with your religion until you decide it's reason to deprive others of the truth.
What I have observed about Alan Cox in the lkml:
1. Does not buy into hero worship of kernel developers no matter how senior.
2. Does not get nasty when outsiders address him in the mailing list.
3. Is a champion of 'perfect is the enemy of the good' principle.
4. Does not froth at the mouth when someone mentions business reasons for needing a particular addition or change.
There are many on that list with big names that stumble on one or more of the above.
You keep seeing the word "resources" in postings from Human Resources? Man, that really is quite odd.