Slashdot Mirror
Linus Announces the 2.6.25 Linux Kernel
LinuxWatch writes "'It's been long promised, but there it is now,' began Linux creator Linus Torvalds, announcing the 2.6.25 Linux kernel. He continued, 'special thanks to Ingo who found and fixed a nasty-looking regression that turned out to not be a regression at all, but an old bug that just had not been triggering as reliably before. That said, that was just the last particular regression fix I was holding things up for, and it's not like there weren't a lot of other fixes too, they just didn't end up being the final things that triggered my particular worries.' There were numerous changes in this revision of the OS. The origins of some of those fixes is detailed in Heise's brief history of this kernel update."
Sorry we only make engines and provide them to all the major manufacturers. Please speak with them about the accessory packages.
"numerous changes in this revision of the OS"
Asking people to call it GNU/Linux is one thing, but it's not much to ask Slashdot not to call a kernel changelog an OS changelog.
Please help publicise swpat.org - the software patents wiki
And that has precisely what to do with the kernel? X is in user space. If you want to replace X with any other windowing system you like, just port it or write it. And when you've written something as powerful and stable as the X Window System, come back and tell us about it.
I'm old enough to remember when discussions on Slashdot were well informed.
Live today, because you never know what tomorrow brings
Linux devs are working their asses off in their parents basements, hacking and testing drivers for hardware that they don't have access to the interface specifications for. If things still look a little shakey, just remember to be glad that they work at all, given the hours of work for $0 return.
When you are done giving thanks, complain to your hardware manufacturer, who does make money from the deal, and does have the full specifications - AND for reasons unknown, have turned down the offer of OSS developers writing the drivers for them, for free .
*See also: Canon
Well, you go run some benchmarks and prove that there's a big win to be had by moving to a non-IPC based model of communication. A significant rewrite like that requires some serious numbers to back it up, and so far, all you've provided is anecdotes and gutfeel, and my friend, that ain't enough.
Oh, for pity's sake. Throw all your engineering discipline out of the window (ha!) and fall back on gut feel. and superstition. The fact is that Linux (with X Windows) performs much better on the same hardware than either Windows or MacOS. Why is this? Until you've shown that X Windows is a significant cost, then you really don't have any argument beyond hand-waving.
I have this to add: I personally have been using the X Window system for eighteen years. I've used it on hardware which had an 8MHz - MHz, not GHz - processor. I've used it on hardware that had 8Mb - Mb, not Gb - of RAM. The X Window system performs perfectly well on that hardware spec. It's always outperformed every other windowing system on the same hardware, and it still does now.
Basic engineering tenet, known to all old engineers (but obviously not taught to young ones): if it ain't broke, don't fix it.
I'm old enough to remember when discussions on Slashdot were well informed.
Benchmarks may not help as well. Gut feel is sometimes the best we get.
That has to be the most absurd thing I've read in a long time. Either you're not a software developer, or you're an incredibly bad one. Either way, it's clear your opinions regarding X can probably be safely ignored.