Linux 2.6.27 Out
diegocgteleline.es writes "Linux 2.6.27 has been released. It adds a new filesystem (UBIFS) for 'pure' flash-based storage, the page-cache is now lockless, much improved Direct I/O scalability and performance, delayed allocation support for ext4, multiqueue networking, data integrity support in the block layer, a function tracer, a mmio tracer, sysprof support, improved webcam support, support for the Intel wifi 5000 series and RTL8187B network cards, a new ath9k driver for the Atheros AR5008 and AR9001 chipsets, more new drivers, and many other improvements and fixes. Full list of changes can be found here."
W00t lots of goodies in this one. So... about time to change from the 2.6.infinity_and_beyond scheme to something else. What say you? I think the 2.6.x should have been left behind when the scheduler changed.
So what kind of flash hardware is this for? Embedded devices, apparently. But maybe as flash storage becomes more common, more devices will support raw access?
Olympus' xD card format essentially specifies a direct connection between the NAND flash chips and its external interface.
It's weird and proprietary, yes. However, it's already being done, and there are arguments to be had for minimizing the amount of circuitry on the memory card itself. Interacting directly with Flash isn't as uncommon as you might think it, and can be of huge benefits for portable/embedded devices that require low power consumption.
-- If you try to fail and succeed, which have you done? - Uli's moose
If viruses were unique to Windows, we wouldn't have "root"kits. Instead, they'd be "Administrator"kits or perhaps "SYSTEM"kits.
You are clearly one of those arrogant assholes since you think there is such a thing as a pecking order in cyberspace.
As an arrogant asshole, you need to know you are one of the core reasons why Linux is only slowly gaining acceptance by the masses because you're too good to stoop to a "newbie's" level.
That being said...nah, you're still an arrogant asshole.
It'd be the best April Fools day ever.
As far as I see, the real change is that what was the 2.4 and what was the 2.5 trees are now kept very close together. Active work (was 2.5) is done on the XX.YY.ZZ-preNUM kernels, it's all polished/troubleshot/reviewed in the XX.YY.ZZ-rcNUM kernels, and then it gets released. What was once 'stable tree' (2.4) work is now done on the XX.YY.ZZ.1 .2 .3 releases, and the developers move to XX.YY.ZZ+1-preNUM.
It seems to work quite well, and now you no longer have to meddle with dark arts and unsupported known-broken dev kernels to get recent hardware working. Win win all around IMO.
No more backporting/sideporting/up/down/leftporting to get current hardware code into current kernels, just all the dev community working on one codebase. Makes progress a lot more straightforward and apparently better/cleaner/less buggy.
The preceding comment is my own, and in no way construes an opinon of the Emperor of Mankind.
Right. Because it's impossible to do on Windows and Mac. You need to wait until the next version of the entire operating system comes out, and then pay for that.
So yes, please switch so you don't even have the option of doing what a Linux user mentions casually in conversation. Less is better, right?
(WTF?)
So? Download and build your own kernel..
Or get Windows or Mac and never have to hear that.
I bet you buy your LEGO preassembled too.
I bet he bought his TV and refrigerator preassembled too.
(don't flame me bro, I also use Linux all the time, but you asked for it ;-))
To be fair, if it was Windows or a Mac, adding support for a webcam would be as easy as installing a binary driver blob. I like Linux, but compiling drivers in to the kernel (and hence needing to compile it yourself, at times) has always been one of it's biggest annoyances.
Last time I looked about 9 months ago there were well over 3000 build options for the 2.6 kernel. Thats probably gone up a lot. I used to build my own kernels , anything up to 2.4 was do-able. But 2.6 is so complex with so many options which frankly mean nothing to me , that you would end up with a right dogs dinner thats far worse than anything the distributions could produce and you'll probably find you missed out some important functionality and/or dependency for something to work correctly and have to start again.