Slashdot Mirror
Linux 3.9 Released
hypnosec writes "After a week's delay Linux 3.9 has finally been made available by Linus Torvalds. Last week Torvalds released the rc8 stating that he wasn't 'comfy' releasing the final version yet and that 'another week won't hurt.' Torvalds noted in this week's announcement that last week had been very quiet as there were not many commits and the ones which were there were 'really tiny' so he went ahead with the release of Linux 3.9."
it's not in TFS, not in TFA... what's new in 3.9?
Slashdot, fix the reply notifications... You won't get away with it...
You have no real idea unless you read the release notes in depth whether 3.8 to 3.9 is a big change or just a bunch of relatively small incremental changes and bug fixes and Linus just fancied upping the minor version number.
Well that's how the progress bar counts so I don't see why it shouldn't be valid for everything else.
1... 2... many... 98%... 5... done
Among other things 3.9 includes experimental kernel-level Raid 5 and 6, caching slow of storage devices by fast ones, support for more graphics cards and audio devices, as well as improved power management.
What's wrong with that? That's how release candidates are supposed to work. You already do all your testing before the first rc. After releasing an rc you wait for anyone downstream to report problems. If there are no reports then that your final stage of QA is done and you accept the candidate.
http://www.h-online.com/open/features/What-s-new-in-Linux-3-9-1845705.html
09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
KernelNewbies isn't reachable at this time so a nice review of cool new features in Linux 3.9 is available at The H Open.
Live long and propser!
This version includes my patches for large HOSTS file support. Previously, the kernel used a fixed buffer size for the HOSTS file entries. relatively largeish (1 million+ entries) overflowed it and entries were dropped. 3.9 will dynamically resize (zero-copy algorithm) so the Linux KERNEL now officially has the best HOSTS file support anywhere.
You omitted the most epic part of the Windows family: Windows ME!
Actually Windows NT kernel is only on 6.2, not 8.
http://en.wikipedia.org/wiki/Microsoft_Windows_NT
Mod me down, my New Earth Global Warmingist friends!
It's been around in the form of bcache for ages now and bcache is considered stable -- it is already in production-use. It's a pretty nifty thing, can be configured to your needs to quite a large degree and it's smart enough not to cache large, sequential reads/writes. If you're interested check out http://bcache.evilpiepirate.org/ and http://atlas.evilpiepirate.org/git/linux-bcache.git/tree/Documentation/bcache.txt?h=bcache-dev
Thanks for the link. I chased down the dm-cache stuff a bit, looking at it vs. bcache, which we'll see in June, probably. The primary differences seem to be that dm-cache is a bit more generic and easier to work with and it allows some manual allocation of the different types of disk data to be cached, while bcache seems to be targeting SSD's specifically, with wear-leveling sensitive write patterns, use of TRIM, and in-kernel code to validate the cache drives for preventing stupid user tricks.
EnhanceIO might also be targeting 3.10, which is a descendant of flashcache, which uses the layered device approach, while dm-cache and bcache are side-loaded. EnhanceIO uses udev rather than in-kernel code to prevent the stupid user tricks. I got the sense that 3.10 was possible for EnhanceIO but not as certain as bcache.
I'm current using flashcache on my non-ZFS systems; it looks like I'll be waiting for 3.10 and use bcache for my next upgrade.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
What I was saying was that there is a world of difference between a wishy-washy statement of "I guess" and an explicit "I believe".
Firstly, when it comes to kernel testing, no news is usually good news. But it's never a sure thing, and it's hard for one person to test it all.
Second, the newest kernel release is usually considered "bleeding edge", at least as far as enterprise goes. It's never a sure thing. Implying it's a sure thing and will for sure not catch your datacenter on fire is probably a Bad Idea.
Thirdly, who cares if Linus says "guess" or "believe". Both translate to exactly the same thing to me, given the context: "I'm pretty sure this is ok, but don't use this until you've backed up your important cat pictures." It's well known he's a bit bunt. Shit man, just be happy he didn't insult your mother in the header.
What about Bob?
Im SAILING!!!!!
There is no right to feel safe thru security vaudeville at the expense of everyone's freedom, privacy and tax money.
I really don't know what you expect. The only time I'd expect him to say "Upgrade NOW!" is if there were something very wrong with the prior release.
Perhaps you've been too immersed in advertisements, so that anything that isn't an ad doesn't sound right? I've NEVER been totally comfortable about any program I've written, and the things I write are small pieces compared to a kernel.
I think we've pushed this "anyone can grow up to be president" thing too far.
That android developers can run Goldfish with a native kernel to simulate a virtual Android device and thus write apps a little bit easier?
An over-the-top subject line no doubt, but as a Linux (LMDE) home user, I am a little concerned about this wonderful OS ecology apparently in just one Torvalds-shaped basket. It seems odd to me that this experience - where community involvement is so beneficial - has a single person that has total thumbs up / thumbs down power.
Yes, this is mostly Linus' baby, but assuming he's not immortal, how much planning is going into the inevitable transition? History is littered with examples of rapid decline / fall / outright war (aka forking) after the strong, hands-on founder is gone. I don't want something as precious as Linux to be destroyed in interneciene BS as that is just what its many enemies desire and will outright foment.