| |||||||||||||
ExamplesExamplesPosted May 23, 2010 15:26 UTC (Sun) by corbet (editor, #1)In reply to: Canonical Goes It Alone with Unity by rahulsundaram Parent article: Canonical Goes It Alone with Unity TUX is a clear example of a kernel feature shipped by Red Hat which was never upstreamed - or even attempted to upstream. I also had fun in the first revision of the driver book because there were RH-specific API features in their kernel. 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.
(Log in to post comments)
Examples Posted May 24, 2010 18:30 UTC (Mon) by foom (subscriber, #14868) [Link]
A personal anecdote:
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...
|
|||||||||||||