Linux Kernel 2.6.11 Released
Xpilot writes "Linus Torvalds has just announced the availability of the newest Linux kernel release, 2.6.11. The newest addition to Linux that's stirring up some excitement is the inclusion of Infiniband support. You can get it from the usual mirrors at http://kernel.org/mirrors."
InfiniBand, which is derived from its underlying concept of "infinite bandwidth,"...
Umm... I don't know about you... but that description didn't help me much... infinite bandwidth? What is this? How is this? How does linux get past physical hardware limitations that other os's can't?
---
Programming is like sex... Make one mistake and support it the rest of your life.
Does ACPI suspend work on more laptops? Inability to suspend is a major problem with Linux on laptops right now, as there are more and more ACPI-only laptops. The situation is considerably worse compared to APM, in my experience.
Ross Schibler, CTO of InfiniBand vendor Topspin Communications, told internetnews.com. . . . "Now that the technology has matured to such a point that Linus has accepted it into the kernel, the way is paved for greater distribution of the code and accelerated deployment of the technology," Schibler said.
That makes for an interesting comment, previously people have been ignoring linux and gunning for windows.
ato
This is for Promise Serial ATA controllers (PCI card, not built into the motherboard). Specifically, the Promise FasTrak TX2Plus (rebranded as a Maxtor SATA/150)
You got it to work? With which vendor's card?? At this point, I am so frustrated, I'm willing to throw money at the solution and buy a new Serial/Parallel ATA controller, if it is affordable enough ($20-30). My understanding, however, was that libata itself (not just the individual drivers, like sata_promise) had no support yet for the PATA connector on any SATA adapter.
There are more to the issues than device permissions. The main part of it is that cdrecord needs to lock some of its buffers into non-swappable memory. This is a priveledged operation in an unpatched kernel.
I believe the patches allow trusted(?) applications to lock small amounts of this memory without requiring root.
Something like that, I follow along enough to know what's going on, but don't understand everything to it.
The kernel part of the driver has about 250K of source code (about half of which is header files) and 3.5 megabytes of binary. None of the userspace code is open. How is that "mostly open source"?