Slashdot Mirror
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."
Linux 2.6.27 is out, OpenBSD 4.4 is in!
Trolling is a art,
It's a shame this won't be in the upcoming Lenny release of Debian. The in-kernel support for heaps of webcams via gspca is a very nice user-visible element of this release.
http://release.debian.org/emails/release-update-200808
Although, I guess they made the decision for 2.6.26 before they realised that a September release would be an impossible target.
Ask me about repetitive DNA
In only 3 months, all of this code has been completed and reviewed by multiple developers. This happens *every* three months. The pace at which the Linux kernel is moving and yet still maintaining quality is incredible. It is clearly the case that the Linux kernel has hit a new kind of critical mass and is now a form of software development that has never been seen before. The sheer number of people involved changes what is possible. If you suggested that every single change to the codebase be reviewed by multiple developers in a traditional proprietary software development house you would be, rightly, laughed at. There simply isn't the resources.
How we know is more important than what we know.
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.
Before you get all excited about running UBIFS on your USB drive, take note: UBI is not for consumer flash media. These devices already incorporate hardware to hide their flash nature so they look like a plain old block device to your OS. UBI is for pure flash devices that directly expose the quirks and distinct characteristics of the underlying media.
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?
what number is Vista?
666
Yeah, embedded devices definitely. It'll be awfully nice to see simple flash chips soldered onto a board rather than someone bolting an SD or compact flash socket onto them just so you can have a boot device.
Fragile, more expensive, and adds another physical item that can break. And not only that, but you can drop about 20-30 dollars worth of non-essential hardware from your design and still be on target. If you do any embedded work you know how big 20 dollars worth of hardware savings is. This new driver is *huge*.
Weaselmancer
rediculous.
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.
> Any chance that this will fix some of the ACPI problems with Linux?
Just to be clear, ACPI problems are motherboard problems, not Linux problems.
If the ACPI function of your motherboard is correct and compliant with the ACPI specification, Linux will work just fine.
Part of the motherboard ACPI problem is that Windows expects, and uses, some functions within ACPI that are not compliant with the ACPI specification ... you know the drill: embrace, extend, obscure, try to screw the opposition ...
Fortunately with ACPI we have not quite yet got to the "extinguish" phase.
I know this is going to get modded as "off topic", but let's cover this...
SYSTEM and Local System are basically one and the same, and are almost perfectly synonymous with root. Network Service would be the equivalent of the "nobody" user - i.e. an account that you can use to run low-privilege services. Administrator would be the same as a user with administrative privileges in Linux (perhaps someone in the sudoers list). The trouble, of course, was that, until Vista/2008 came along, it was trivially easy for an Administrator to escalate to SYSTEM - you just had to run a scheduled job in interactive mode (think of a cron job with no password required) and you'd not only have root access, you'd also have access to the current user's console. For an administrator, this came in handy - of course, what was handy and convenient for an administrator was just as handy and convenient for someone else.
It'd be the best April Fools day ever.
How much of the code is from Linus himself nowadays? I thought he mostly reviewed/rejected patches, and occasionally, once every to or so years, accepted a patch or two. ;-)
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.