Canonical Goes It Alone with Unity
Posted May 23, 2010 2:05 UTC (Sun) by dlang (subscriber, #313)
the new 2.6 development model was created specifically to address these sorts of problems.
I'm not saying that when RedHat implemented a feature they did so to deliberately lock users in to their flavor of Linux, but when the upstream developers went a different direction and didn't accept what they had already shipped to customers (and had companies like Oracle depend on) that's the effect that it had.
Posted May 23, 2010 3:12 UTC (Sun) by rahulsundaram (subscriber, #21946)
Posted May 23, 2010 15:26 UTC (Sun) by corbet (editor, #1)
Whether competition has anything to do with any perceived changes is not clear to me, though. I suspect it has more to do with both the company and the communities it works in growing up.
Posted May 24, 2010 18:30 UTC (Mon) by foom (subscriber, #14868)
RH's non-upstreamed tux patches caused me pain recently(ish). Turns out TUX added a flag to the open syscall named O_ATOMICOPEN. It used the next available O_ flag value after those used in upstream kernels. That flag was not upstreamed. Upstream then added a flag to open called O_CLOEXEC. They (of course) also used hte next available flag value.
So, new binaries which attempted to use O_CLOEXEC (even when they attempted to test for its existence before using it) would fail badly when it returned some completely unexpected random error value...
Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds