Slashdot Mirror
Linux Kernel 2.6.14 Released
digitalderbs writes "Linux kernel 2.6.14 was released on 10-28. OSnews reports on new features like 'HostAP, FUSE, the linux port of the plan9's 9P protocol, netlink connector, relayfs, securityfs, centrino's wireless drivers, support for DCCP (currently a RFC draft, PPTP, full 4 page-table support for ppc64, numa-aware slab allocator, lock-free descriptor lookup' and many other things. The changelog is also available."
Obligatory "you must be a Gentoo user" response.
'Yes, firefox is indeed greater than women. Can women block pops up for you? No. Can Firefox show you naked women? Yes.'
The "comprehensible changelog" is slashdotted. Why is the high-level feature list of the release such a low priority, though so demanded? I know programmers prefer writing C to writing English (or Finnish, or Hindi, or German). But what good is code people don't install because they don't know what it does for us? There are so many people hanging around OSS projects who can't or don't contribute to the code. Surely some of those people can help by at least distilling the changes into a brief description. Release notes might not be the most important product of a release cycle, but they often control everything that product consumers do after the release is published.
--
make install -not war
Does anyone know if/when reiser4 will be included into the mainline kernel? I recall reading a kerneltrap interview a while back with Andrew Morton, in which he basically said "sure, why not?" to including it into the next release..
Best regards, A.C.
Hasn't the kernel pretty much reached the point where, for the average user, the only problems are those that just can't be fixed -- in other words, drivers for proprietary devices that haven't had their specs released by the manufacturers?
Find free books.
"The problem's all inside your head", she said to me
The crap filter is annoying, I agree
You can defeat it if you do it logically
There must be fifty ways to troll on Slashdot
She said it's not really my habit to intrude
The sensationalist titles are often misconstrued
The editors' spelling may be somewhat crude
There must be fifty ways to troll on Slashdot
Fifty ways to troll on Slashdot
Mods are on crack, Jack
Repost spam, Sam
GNAA, Ray
Just set yourself free
Get a first post, Gus
You don't need to discuss much
Hit the refresh key, Lee
And get yourself free
Goatse.cx Tex,
Widen the page, Dave
Stephen King's dead, Fred
Just set yourself free
Change the article text, Gus
You don't need to discuss much
BSD's dead, Lee
Just get yourself free
Although it grieves me to see Zonk in so much pain
I post "I fail it!" and then start to smile again
Netcraft confirms that Wikipedia explains
About the fifty ways to troll on Slashdot
She said why don't we both karma whore tonight
Thinks about your breathing, you'll begin to see the light
She poured hot grits down herself and I know she was right
There must be fifty ways to troll on Slashdot
Fifty ways to troll on Slashdot
Is it whack, Jack
Viewing tubgirl, Earl
Mod up a flame, Shane
Just set yourself free
KDE sucks, Gus
You don't need to discuss much
Referral link, Lee
Just set yourself free
That's where they come from. However, the version included in this kernel is a bit lower than the latest release on sourceforge. (1.0 vs 1.0.8 if I'm correct)
Released October 27, 2005 changelog
Numa-aware slab allocator: It creates slabs on multiple nodes and manages slabs in such a way that locality of allocations is optimized. Each node has its own list of partial, free and full slabs. All object allocations for a node occur from node specific slab lists (commit - benchmarks)
Lazy page table copies in fork() for VMAs without anonymous pages (the ones with anonymous pages are still copied): Defer copying of ptes until fault time when it is possible to reconstruct the pte from backing store, speeding up fork() greatly specially for processes using lots of shared memory (commit)
Add /proc/$PID/smaps: This file will shows how much memory is
resident in each mapping. Useful for people who want to perform memory
consumption analysis (commit)
Add /proc/$PID/numa_maps: This file will show on which nodes pages reside (commit)
Lock-free file descriptor look-up (commit) - (commit)
Four-level page table support for the ppc64 architecture: extends the usable user address range to 44 bits (16T). (commit)
Support hotplug cpu on 32-bit SMP powermacs: When a cpu is off-lined, it is put into sleep mode with interrupts disabled. It can be on-lined again by asserting its soft-reset pin, which is connected to a GPIO pin (commit)
Add TASK_NONINTERACTIVE task state bit to the cpu scheduler: It can be used by blocking points to mark the task's wait as "non-interactive". This does not mean the task will be considered a CPU-hog - the wait will simply not have an effect on the waiting task's priority - positive or negative alike (commit)
PPTP (Point-to-Point Tunneling Protocol) support: RFC 2637. Used to implement VPN products (notably, Microsoft in all the Windows versions). Wikipedia article (commit)
DCCP: "Datagram Congestion Control Protocol". Datagram protocol (like UDP), but with a congestion control mechanism. (LWN article) Currently a RFC draft (commit)
Implement SKB fast cloning: Protocols that make extensive use of SKB cloning, for example TCP, eat at least 2 allocations per packet sent as a result. To
Just a quick scan of pages, though, so I could be off on some of these.
Check out FuseFS, for example (see why it's cool). Or encfs (see O'Reilly article).
Linux is starting to go beyond emulating the Unixes of yore, to create a whole new world of computing.
Sorry - this isn't the MPPE patches. This is support for PPTP packets being tracked through iptables. What I believe this will let you do is have multiple PCs behind a Linux firewall be able to use PPTP at the same time (prior to this PPTP through a Linux iptables firewall would work for only one PC at a time.)
If it's anything like 3 was when it came into the kernel please leave it out. 3 was only let into the kernel because reiser bitched and bitched, but it was unstable and buggy. I have been much happier with ext3.
It has been statistically shown that helmets increase the risk of head injury.
If you're running an SMP AMD64, you need this version to avoid random segfaults. It turns out that 4-level page table support on all but very current AMDs tickles a processor bug. See this discussion on the kernel Bugzilla for more detail than you ever wanted to know.
Disinfect the GNU General Public Virus!
Linus won't order it in since Andrew Morton (his right-hand man) has already indicated that it will go in. There are a few concerns raised by Christoph Hellwig (lkml's resident pitt-bull) that Andrew Morton has asked to be fixed before it goes into vanilla. Mostly these issues have only held up inclusion (a filesystem would normally have got merged with just those style issues) because of concerns that after inclusion the code would be abandoned and even cleanups being opposed by the original developers as allegedly happened with reiser3.
features and performance are *not* the top priorities in Linux, the top priority is maintainability. The rate at which features and performance improvements are added is a consequence of the maintainability, which must not be compromised for the sake of a slightly cool filesystem.
and I'm not blaming Hans.
Reading that thread, I'm not sure why. ReiserFS may be the bees' knees, but that's no excuse for that kind of behavior. Kernel style is kernel style; if Reiser thinks they should change kernel style, that's a reasonable thing to discuss, but the fuck-you-my-code's-better-than-your-crappy-code routine sure isn't the way to go about it.
The vfs already has modularity, and the vfs is *the* Linux filesystem where the filesystems are modules that implement separate storage backends but all the same semantics.
One problem with reiser4 (now addressed in the code proposed for inclusion at this time) was that it changed some of the defined semantics of the vfs. This bit won't go in until it is thoroughly discussed and user-space has subsequently been prepared for it (and deprecation of the old behaviour widely expected).
The problem with the modularity of reiser4 is that is implemented fully inside reiser4 instead of being designed as a modification of the vfs where reiser4 simply provides one storage backend. The reiser4 modules should have been put right up behind the vfs as a proof of concept for the first integration, where the new modularity features could be moved bit-by-bit into the vfs, where all filesystem are then just a storage backend and all could be easily made to support the transaction and query facilities expected.
Some of the style problems included things like generic datatypes being implemented in the reiser4 directory instead of as a general facility for the kernel as a whole. Most of these were fixed, I believe, but AFAIK the problem of the level at which the modularity is implemented, and the failure to distinguish between semantic/feature modules and storage backend is not a good design.
There goes the last *BSD user...