Slashdot Log In
Alan Cox Leaves Red Hat
Posted by
CmdrTaco
on Tue Dec 30, 2008 11:11 AM
from the bet-wherever-he's-going-he'll-have-electricity-and-heat dept.
from the bet-wherever-he's-going-he'll-have-electricity-and-heat dept.
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.'"
Related Stories
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
The best of luck! (Score:5, Interesting)
Re:The best of luck! (Score:5, Funny)
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.
Parent
Re:The best of luck! (Score:5, Funny)
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!
Parent
Re:The best of luck! (Score:5, Funny)
I'm so ashamed of myself for laughing at that.
Parent
Re: (Score:3, Funny)
After seeing this story tagged coxblock I was reminded of a discussion I had yesterday with my father about how Cox (the ISP) was blocking incoming port 80 requests. The phrases coxblocking and coxblocker came up more than a few times.
Re:The best of luck! (Score:5, Funny)
You keep seeing the word "resources" in postings from Human Resources? Man, that really is quite odd.
Parent
Re:The best of luck! (Score:5, Funny)
No it doesn't. It implies sodium hydroxide
Parent
There is speculation... (Score:5, Interesting)
Re:There is speculation... (Score:5, Interesting)
Yep, that's exactly what I was thinking.
For as long as I've been following (and been ever so slightly involved in) Linux development, oh, say from the mid-late 90s, Alan Cox has nearly always been there hacking primarily on device drivers.
Intel has steadily picked up more Linux kernel hackers over the past 5 years or so who seem to focus on device drivers (e1000 NIC drivers) but also employ others who have very broad-based and deep knowledge of the kernel. Alan Cox seems to be a good fit with his long history of kernel development and focus on low-level drivers.
So good for Alan for changing things up a bit, and good for Intel for hiring another full-time Linux developer! Hopefully this leaves room for Red Hat to pick up another developer in his place.
Parent
Red Hat is the wrong place to develop drivers... (Score:5, Insightful)
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!
Parent
Is it? And the right place is ... ? (Score:5, Insightful)
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. ... This move is really more a reflection of the continuing maturity of the Linux Operating System!
God help us if linux gets as, ahem, MATURE as Windows. Microsoft's crappy OS code is only exceeded by the unbelievably crappy driver code turned out by OEMs.
Tracking down (bug-ridden) drivers for everything is the single factor that makes Windows' out of box experience a living Hell (And accepting them only on floppies is the single factor that will eventually kill off XP).
The contrast with linux is eye opening to former benighted Windows users. Not only are all your drivers right there, but all the apps you need are a (free) click away.
Anyway, it's not OS packegers who develop linux drivers; its kernel developers - who are exactly the people with the skills to do the best job.
Parent
Source vs. Binary (Score:4, Informative)
One of the nice benefits of having driver source available is that the kernel developers can fix them if they understand the device itself. The original designer of the device is always in the best position to write at least the initial driver code.
One of the big rules in kernel development is that "if you break it, you have to fix it."
Having a good-quality original driver from the manufacturer means that the driver will be ported to new kernel versions, and any incompatibilities introduced are fixed by the person on the kernel team who made them break.
Parent
Re: (Score:3, Insightful)
In Windows' case, the drivers are binary.
But in the Linux world, they will be (already are) largely open source. If a vendor puts out a crappy driver, people who know better can submit patches, and people who don't know will quickly learn who to avoid.
Re: (Score:3, Funny)
Why do they name the drivers? And why Alan Cox? Is it one of those easter eggs where naming your file a certain way does something?
Re: (Score:3, Interesting)
This is not to say that Red Hat
Re:There is speculation... (Score:4, Informative)
It seems that this article [lxer.com] referred to by the main article [ostatic.com] speculates incorrectly, saying that:
whereas Alan actually wrote:
a few lines below.
Parent
Re: (Score:3, Insightful)
For that matter, why should Red Hat fund development on the sorts of thing that Alan Cox works on, if hardware vendors are willing to fund it? Intel can even get developers internal documentation and (most importantly) face time with hardware designers who can explain things that they didn't think to document (or that they documented in a huge specification that's too big to find the little detail in).
There's no reason for Red Hat to have a collection of kernel developers working on stuff that Red Hat doesn
Re: (Score:3, Insightful)
The American cultural system would collapse
Choose one of:
A) What is this American culture you are speaking of?
B) You say that, as if it were a bad thing...
Alan Cox? (Score:4, Funny)
Who's he?
Re:Alan Cox? (Score:4, Funny)
He used to be a hilarious DJ on WXDX in Pittsburgh that I listened to in college.
http://en.wikipedia.org/wiki/Alan_Cox_(radio_presenter) [wikipedia.org]
oh wait...
Parent
Re:Alan Cox? (Score:4, Funny)
I don't know him but does he run Linux?
*looks him up on wikipedia*
Now, I am an informed individual why haven't I heard about him or this "Richard Stallman" guy? Well they both have long beards, they might be good programmers.
Parent
Re:Alan Cox? (Score:4, Interesting)
Parent
Re: (Score:3, Funny)
I once met a girl at a party
Teach us, oh master!
Hmm. (Score:2)
Doesn't mention what type of hardware he's going to be working with, though.
General? Or are we going to see a jump in quality in Linux support of Intel WiFi/VGA/CPU at the exclusion of others. Anyone know how software development works at Intel?
Re: (Score:3, Insightful)
Alan Cox decides what he works on. He'll have more access to Intel hardware and specifications but Intel has no chance on directing his work.
There are a lot of companies that would jump to have him work for them. If Intel tells him something he doesn't like, he could leave at his whim to one of them.
Re: (Score:3, Insightful)
I doubt Intel would be too hurt by his departure either. You greatly over-estimate how important he probably is to Intel. He'll likely do what they ask; he is being paid by them, you know? Unless you think he's some kind of unprofesional crybaby..
Re: (Score:3, Funny)
Re: (Score:3, Funny)
Higher salary? (Score:5, Insightful)
If he gets a higher salary, why not? People have been motivated for less.
Re:Higher salary? (Score:5, Insightful)
Parent
Re: (Score:2)
Seriously. I've known plenty of people that have stepped out of high paid positions to go work someplace where they'll have more fun. If you're making 6 figures but you spend 10 hours a day hating everything, what's the point? There's no reason not to just make less doing something you actually enjoy.
I've known several people who did that, but in all but one case they did it after banking some serious coin first and buying houses. Its easy to think like that if you have the financial security to do it, most people don't.
As an Intel Employee..... (Score:5, Funny)
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.
Re: (Score:3, Funny)
That's because you don't have a window view, right!!? :)
Re: (Score:2)
Alan Cox in two weeks? [ytmnd.com]
Re: (Score:3, Informative)
Doesn't Cox "work from home?"
Home being in the UK somewhere.
Re: (Score:2)
Re: (Score:2)
As a former Intel employee, I have to echo this sentiment. Intel buildings are notoriously bland and ugly, as they refuse to spend any money on architecture, and the cafeterias have mediocre food for outrageous prices. My current employer has a cafeteria with mediocre food as well, but at least the prices are normal.
Intel has some nice things about it as an employer, but the cafeteria isn't one of them, especially with Intel's typically mediocre (or less) pay. This may have changed since I left though, s
Re:As an Intel Employee..... (Score:4, Insightful)
And as a Red Hat employee, I can say that Alan's leaving isn't a signal that anything's amiss at Red Hat. Quite the contrary, actually. Alan's not going to leave behind Linux: he's going to continue that with someone else signing his pay check. And by working for Intel he's going to get to work on future hardware sooner.
For my job I deal with some upcoming hardware that requires someone like Alan getting to it before I even touch it, since a working kernel would make my job easier.
Parent
Anyone care to speculate about his compensation? (Score:3, Interesting)
Could anyone speculate about what his compensation was like?
I always wondered how much folks like Allan Cox are paid.
I mean...they do low level coding that I will never be able to do.
So what is the salary like in jobs like these?
Re:Anyone care to speculate about his compensation (Score:4, Interesting)
Parent
Re: (Score:2)
That's good money in this economy. I work in the health-care field; the money is not all that bad but one has to "learn" to live with all kinds of crap.
Back stabbing by fellow employees and the fact that you are not appreciated are quite common. Members of the public appreciate the doctors more.
It is the case although nurses and those close to patients know more about the patient than the doctors, and doctors normally go by nurse's opinions. I guess it comes with the territory.
I would assume that because ve
Re: (Score:3, Insightful)
That's good money in this economy.
It's decent money (well, until inflation rears its ugly head soon, which it may or may not do), but it's not great. But the bad thing about it, as the previous poster noted, is that it's not much more than the average bumbler gets. In engineering, it's pretty easy to get $80-90k with relatively little experience, or with a not-so-great track record of performance, just by moving around a little. If you're a star performer, in fact, you'd be lucky to get raises sufficient
Re: (Score:3, Informative)
In engineering, it's pretty easy to get $80-90k with relatively little experience, or with a not-so-great track record of performance, just by moving around a little. If you're a star performer, in fact, you'd be lucky to get raises sufficient to make much more than new hires who left their previous job because they didn't get any raises (i.e. not great performers), and the new company wants to pay them "market rate". Typically, you'll only match the new hires with your raises. So what, exactly, is the incentive to be a star performer? There is none. You can be a total slacker instead, just change jobs every few years, and do just as well as the guys putting in 90 hours/week and doing the work of several lesser engineers.
This is absolutely true... where I work, the pay ranges that I know of for all north american sites, as of last year, were:
MTS: 103k-168k
SMTS: 115k-187k
I'd say roughly MTS means 7+ years of experience, and SMTS means 9+ years, give or take.
Of the people that were brought in at their current level, most (say around 80%) are around the median of those ranges, tending to be a bit higher. Of the people that were promoted to those levels, most are in the bottom 25% of the salary range.
Now, there is certainly
Re: (Score:3, Funny)
So you think it's ethical to work really hard for no extra compensation?
If so, I've got a lot of work I could assign you. I don't have any money to pay you, but if your work ethic is high, you should be happy to take on this work for no pay. Please let me know what your skills are, so I can provide you with suitable work.
Bu cryn newid mewn deng mlynedd (Score:3, Informative)
I first stumbled on Slashdot ten years ago when Alan Cox mentioned in his online diary (a novelty in those days) that it was nice that even Slashdot were carrying it as a story.
I knew Alan from my uni days when I heard the outrageous rumour that SUCS (the comp.soc.) were trying to put real Unix onto a PC.
Alan Cox is a Good Influence (Score:5, Interesting)
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.
Re:Alan Cox is a Good Influence (Score:5, Informative)
Parent
Re: (Score:3, Interesting)
He is also very polite when hero worshippers (me) come up to him in public (The Green Man Music Festival), just to say hello.
thought it was over 10 years (Score:3, Interesting)
He was writing his diary as a redhat employee since 1997. Too bad he got caught up with that welsh fad & then the business school fad of the early 2000's. Hopefully he realizes the value of low level programming again.
Re: (Score:3, Funny)
Probably "2006: Year of the Linux Desktop".