Linux 3.11 Released 98
hypnosec writes "Linus Torvalds has just announced the release of Linux 3.11 as anticipated. Torvalds notes that the final version doesn't bring in a lot more than what is already present in the rc7, but it does include fixes — most of them in networking, file systems, and audio."
Re:Is it for Workgroups? (Score:2, Insightful)
I think we're pretty much past that joke by now.
A dozen articles on this website already mentioned that, after even Linus himself mentioned Windows for Workgroups 3.11.
And to all the people using karma to 'thumbs up' those Workgroups comments: get a life.
Re:Is it for Workgroups? (Score:5, Insightful)
I think we're pretty much past that joke by now.
This is slashdot. Think again.
Re:Lovin' my Linux 3.8... (Score:3, Insightful)
isn't linux suppose to run on a toaster? But whenever someone brings up a problem its their piece of shit, and of course no one is having issues, no one else fucking uses it
Re:Lovin' my Linux 3.8... (Score:2, Insightful)
The first does not follow from the other.
One common problem is broken hardware, with an undocumented workaround in the Windows driver. Or a broken Windows standard driver, with an undocumented workaround in the hardware.
Once you get the BIOS involved, it gets even worse. Nowadays, the BIOS can do things differently depending on the OS. One motherboard had a BIOS workaround for an old bug in a 2.6 or 2.4 kernel. The next kernel version fixed the bug, and that motherboard stopped working under Linux. Make the Linux kernel identify itself to the BIOS as being XP, and everything works.
And then there's the (hardware or BIOS) features that doesn't get used by the current version of Windows, and so nobody bothers implementing them correctly. Linux, however, uses those features, and thus doesn't work. When the next Windows version uses those features, we often end up back at broken hardware with a workaround in the Windows driver.
An example: Linux was among the first to support the ATA TRIM command, and certain CD-ROM drives (I think), rather than responding with "No such command, this is not an SSD", instead entered firmware flashing mode. Not just a case of Linux not working with the drive, the drive was actually bricked in that the firmware was overwritten with random data.
Another: The Samsung UEFI machines that did not check the size of the data sent to the UEFI non-volatile RAM area. Windows only sent a few K, so no problem there. Linux used it for crash logging, and rather than reporting "not enough memory", UEFI gladly filled the entire area, leaving no space for it's own use, which was required to boot any OS.