Linked by David Adams on Wed 24th Sep 2008 22:44 UTC, submitted by snydeq
Thread beginning with comment 331662
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2005-07-24
We've already covered this.
But before I address that, I would like to address (again) something that is more important.
Jim Zemlin of the Linux Foundation has made some undiplomatic and poorly considered remarks which call his judgment into question. If you read here, and also more Linux specific sites like lwn.net, you will see that most of us in the Linux community refuse to condone his gratuitous attacks. Some of us are emailing the Linux Foundation to express our displeasure.
Please decline to participate in or encourage any rock throwing war within our POSIX-like OS community. It's counterproductive, a waste of time, and plays into the hands of... mumble-mumble.
Now. That said... the Linux kernel's user space ABI is sacred and has been all the way back to the early 90's. All the moaning we hear about the *internal* ABI changing often confuses people into thinking otherwise. Furthermore, it has been a *very* long time since I have had a problem involving glibc versions, which would be the next most important case. (The last time I had such a problem, the company providing the app and updates had been ignoring a *loud* glibc deprecation warning for 5 years!) And if you have a proprietary app that *does* depend on old libraries, you still don't really have a problem since the enterprise distros allow you to stick with the same major version for *at least* 7 years. And then often provide "-compat" packages to get you by for another 7 years.
But if Solaris does an even better job of providing backward compatibility, that's fine with me, and is likely both a strength and a weakness.