Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Linux Kernel 2.6.24 Released

Soulskill posted more than 6 years ago | from the new-toys dept.

Software 108

LinuxFan writes "Linus Torvalds has released the 2.6.24 Linux Kernel, noting that he and most of the other key Linux developers will be flying to a conference in Australia for the next week. As the whole team will be down under while the kernel is being tested by the masses, Linus added, "Let's hope it's a good one". What's new in the latest release includes an optimized CFQ scheduler, numerous new wireless drivers, tickless kernel support for the x86-64 and PPC architectures, and much more. Time to download and start compiling."

cancel ×


Sorry! There are no comments related to the filter you selected.

Niggers worldwide celebrate. (-1, Offtopic)

Anonymous Coward | more than 6 years ago | (#22179048)

They hear "ubuntu" and go feral. Heck, they go feral when they see a watermelon slice.

Ron Paul

Way to go (-1, Offtopic)

Anonymous Coward | more than 6 years ago | (#22179050)

yum update > make

Wow. Lots of stuff. (5, Interesting)

MostAwesomeDude (980382) | more than 6 years ago | (#22179056)

On one hand, things like the VM dirty writeback adjustments and default cpufreq frequency governors, as well as dynticks for more arches, are big performance improvements. On the other hand, they broke wireless packet injection patches for a lot of drivers... At any rate, I'll have to try this just to see if it really performs better. Things like laptop_mode which rely on optimized scheduling and writeback code should see improvements.

Yeah tick less is fine stuff (4, Informative)

emj (15659) | more than 6 years ago | (#22179270)

Reducing wakups on laptops is very interesting suff, I've seen some post on how muche better the NO_HZ is making things, e.g. Ross went from 164w/s to 5w/s [] just waking up 5 times per second makes the CPU pretty cool...

more power save links (2, Informative)

emj (15659) | more than 6 years ago | (#22179280)

I was going to post this on Thinkpad wiki on power consumpton [] , but sadly the page is not working atm..

Re:more power save links (2, Funny)

Nukenbar (215420) | more than 6 years ago | (#22181786)

A lot of links don't work 'at the moment' when you post them on Slashdot!

Catching up to Windows on power (2, Interesting)

dpilot (134227) | more than 6 years ago | (#22180346)

From everything I've heard, Linux is still only catching up to Windows in terms of power consumption. It's fun because we hear all of the details, and until someone builds some nifty package, we script all of the dial-tweaks ourselves. Part of the fun is knowing the dials and what they do, but I guess that's not fun for everyone, some want it to just work, and we're getting there. As long as I can still see the dials, understand them, and tweak them, good automated default power management is good, too.

But from a methodology viewpoint, does anyone understand the road Windows has trod, and how they have gotten to where they are? For instance, things like the tickless kernel are pretty fundamental. Is the Windows kernel tickless, or how do they get their power down if it isn't?

Re:Catching up to Windows on power (2, Insightful)

JasterBobaMereel (1102861) | more than 6 years ago | (#22180492)

What you do is you get the hardware manufacturers to write their device drivers to your specs so you can rely on devices going to sleep and waking up properly and reliably then you can write easily make the system consume very little power

The you write the system so that it uses more memory than you have and so swaps to disk constantly so that it uses huge amounts of power when working and only saves any power when the whole system goes to sleep ....

Re:Catching up to Windows on power (1)

Andy Dodd (701) | more than 6 years ago | (#22180696)

Windows power management used to SUCK in early versions of XP. XP's support for SpeedStep on Pentium 4-M CPUs was abysmal, for example. The Windows 2000 SpeedStep app from Intel (which didn't work in XP) was lightyears ahead of what XP had built in. Back in 2001-2002, Linux could easily blow away a Windows machine in terms of power consumption. Since then XP has improved due to lots and lots of "behind the scenes" tweaks, and to some degree, hardware manufacturer cooperation.

For example, one of the few things the Linux NVidia drivers still don't support well is power management. (ATI isn't any better in this regard though.)

Re:Catching up to Windows on power (1, Insightful)

Anonymous Coward | more than 6 years ago | (#22180832)

Then you probably heard wrong. You might be confusing it with ACPI support - a standard which Windows does not implement correctly, which Microsoft give away defective tools for implementing (resulting in defective support for ACPI on many machines, particularly laptops), and which manufacturers support by testing against Windows only. It works in Windows only because hardware manufacturers make it work in Windows, but tends not to work so well in Linux.

In all other respects, Linux is way ahead on power consumption. Things like a tickless kernel, or tools like PowerTOP simply don't exist on Windows. If you have a laptop that's well supported under Linux, it'll tend to last a lot longer than it does under Windows.

Comparing to Mac OS X is a different matter entirely.

Re:Catching up to Windows on power (1)

darkwhite (139802) | more than 6 years ago | (#22184714)

The original poster heard right, and you're spreading misinformation. Windows XP is way better at conserving battery power than Linux. Tools like powertop and tickless have been enabling great improvements in power consumption but it's still nowhere near that of XP.

Re:Catching up to Windows on power (5, Interesting)

ThePhilips (752041) | more than 6 years ago | (#22187716)

It is sad reality the people keep mixing up technology and products.

Linux (as kernel and piece of technology) is far ahead of most OSs in power management and especially in power saving.

But. Take fresh Windows XP installation - it would give you decent up-time from single battery charge. Take Mac OS X - it would give you excellent up-time from single battery charge. Now take Linux's distro with X.Org/GNOME/KDE/etc - and it would eat any battery in under two hours.

It is possible to optimize Linux to be extremely power efficient, yet lion share of applications written for PCs simply fail on portables.

From recent example. I'm reading lots of PDF ebooks - under Mac OS. Trick is to scroll document to the end and then go back to place were you stopped: Mac OS would cache the file and hard drive will not wake up for the whole time you read thru the PDF. Linux? - Ubuntu/Kubuntu/SUSE/YellowDog were tried - hard drive is always spinning. Always. Non-stop. I stopped even trying to investigate what keeps it spinning - just went back to Mac OS. Because battery lasts under Linux for about 2 hours - while Mac OS on the aging iBook easily does 6 hours. But honestly, even if battery charge set aside, the noise produced by constantly spinning hard drive me slowly crazy.

Conclusion: excellent power management of kernel != end-user application are designed with power efficiency in mind.

P.S. Most common offenders are X.Org with its ~/.xsession-errors (as if end-users cared about all the cruft in there - developers simply do not look there at all) and syslogd which periodically (by default every 20 minutes) write marker into logs.

Maureen Dowd's Gigantic Vagina (-1, Offtopic)

Anonymous Coward | more than 6 years ago | (#22179402)

Have you heard about Maureen Dowd's enormous vagina? The Rude Pundit was having a late lunch with a New York Times insider, in that he had had parts of his body inside Maureen Dowd, and he spilled the beans about spilling his seed in Maureen Dowd's pudenda. "Her labia are like goddamn Dumbo ears," he said, sucking down his third vodka martini of the afternoon, jamming a fancy french fry into some bernaise that had been stained with the blood of his rare steak. "No, really, when I was going down on her, I felt like I was wearing moist earmuffs."

Apparently, Dowd's vulva is large enough to fit "three, four elephant dicks. And Tarzan could swing from her clit." He is a man who enjoys his pussy, and he'd be quite adept at having some box lunch if his appetite at the downtown steak joint was any indication. He continued, for, indeed, once a man starts talking about outsized poonani, there's no way to stop him. "Yeah, fucking Maureen Dowd is like launching a bottle rocket into the Grand Canyon," he said, using a chunk of fat to wipe up the remaining eggy sauce. "I think I lost my watch in there." And, yes, his wrist was watchless.

The Rude Pundit asked his dining companion why he fucked Maureen Dowd. "Have you read her shit lately?" he said. "What the fuck? Seriously. What. The. Fuck." He talked about her strange, ongoing assault on the Democratic candidates (and potential candidates) for President. "In the last month, this kooky kooz has called [] John Edwards a 'metrosexual' 'cause he got an expensive hair cut - lemme tell ya, her dye jobs ain't exactly Clairol off the shelf at CVS. She may as well have just gone Coulter on Edwards' ass and said he was a 'faggot.'

"Then Dowd went off on Barack Obama's wife [] for acting like a real human being in a real marriage, saying that 'some' saw her as 'emasculating.' And now she's going [] after Al Gore for being fat, not even paying attention to his new book, but only to if he's gonna lose weight to run for President. Oh, and how he eats a lot. She may as well have pointed her bony ass finger at him like she was on a playground and yelled, 'Fatty-fat-fat, you fat fuck.' You gonna eat that roll?"

The Rude Pundit gestured for him to have at. "By the way, when Maureen Dowd puts her hand around your cock, it feels like an old tree trying to eat a hot dog," he said. But that didn't answer the question. Why did he fuck Maureen Dowd?

He stared, a tinge of regret, a bit of horror, maybe even a shade of sadness, as if he mourned for lost innocence, passing through his eyes. "Because somebody had to," he said. "Someone had to take one for the team. Because in her column today she said that Bill Clinton's girth back in the day was 'roguish,' when, during his presidency, she barely ever missed an opportunity to mention it, like it made him into an overweight rube."

He was on a tear, a man driven to confess, to justify his actions. "Because she seems to think that feminism is about taking down other feminists, men and women. She's just ninety degrees from Ann Coulter in the way she seems to want a real man, one who's not a fat, emasculated metrosexual, to fuck her hard. And, goddamnit, I decided I was that man."

He started to cry, wiping his mouth with his napkin and tossing it on his plate, which only contained a leaf of escarole. "But what I can't get out of my head," he said, "is her vagina, like some undersea beast, nestled in the rocks and coral of her legs. Sometimes, at night, man, I can still hear my watch, its ticking echoing off the walls of her cervix. Hell, if I took a flashlight to her, I'd probably find cave drawings in there."

Taking his hand, the Rude Pundit assured the anonymous New York Times insider that the world would be warned away from Maureen Dowd's expansive vagina, yes, truly a shallow way to judge a woman, but she deserves nothing less.

Anti-Fragmentation? (4, Insightful)

kripkenstein (913150) | more than 6 years ago | (#22179500)

The updates most interesting to me are the anti-fragmentation patches,

Tests show that about 60-70% of physical memory can be allocated on a desktop after a few days uptime. In benchmarks and stress tests, it has been found that 80% of memory is available as contiguous blocks at the end of the test. To compare, a standard kernel was getting ~1% of memory as large pages on a desktop and about 8-12% of memory as large pages at the end of stress tests.
Perhaps someone can clarify exactly what this means? Reading the beginning, it talked about 4K pages, device drivers, and such, so I assumed it would just be relevant to the internal workings of the kernel. However, the quote I pasted above seems to indicate it might impact desktop performance as well.

I commonly see on my desktop, after several days uptime, that quite a lot of memory is being used (and I know how to ignore cache/buffers, as well as swapcache - that isn't the issue). Logging out and logging back in returns memory to reasonable levels (and the system becomes more responsive, but then I guess if I bought more memory I could accomplish that as well). Now, I've generally read that the problem was indeed memory fragmentation, e.g. here [] , but this would be internal fragmentation inside an app, and thus not relevant to the kernel, I believe? If someone can explain this issue I'd be grateful.

Re:Anti-Fragmentation? (1)

pmontra (738736) | more than 6 years ago | (#22180276)

I googled a little and found this article [] . I'm not sure that this is all of the story, but it should be a good starting point for further investigations.

Re:Anti-Fragmentation? (4, Informative)

Anonymous Coward | more than 6 years ago | (#22180630)

He's talking about how the memory blocks allocated to user programs are actually laid out in physical memory. Think of it like this: if we have programs A, B, C, and D using memory (and F for free), before the physical memory may have been allocated something like this:

And now more like this:
AABBBAFFFCCCCDDFFFFF (free memory is in large contiguous chunks)

This is not something that userspace programs will notice directly, but it does affect performance of the machine. Keeping free space and other areas contiguous allows for better caching performance and faster access.

Re:Anti-Fragmentation? (0)

Anonymous Coward | more than 6 years ago | (#22181396)

Keeping free space and other areas contiguous allows for better caching performance and faster access.

This makes no sense. Your average cache line is tiny compared to a memory page. Additionally pages are aligned, meaning that they are already "optimized" for the L1 & L2 caches.

Re:Anti-Fragmentation? (1)

X0563511 (793323) | more than 6 years ago | (#22184200)

It does make sense. When your ram passes a row to the CPU caches, it's nice when most of that row is related somehow. The large blocks of free space help ensure that A/B/C/D/E don't get all mixed up next to each other.

Re:Anti-Fragmentation? (1)

kelnos (564113) | more than 6 years ago | (#22188192)

Modern CPU cache lines are typically on the order of tens or hundreds of bytes. Yes, bytes. Not kilobytes. Memory fragmentation doesn't really affect CPU caching. Fragmentation does, however, affect allocation/deallocation performance as well as application memory access speed.

Re:Anti-Fragmentation? (1)

cbart387 (1192883) | more than 6 years ago | (#22180794)

It sounds like it's talking about memory management for external fragmentation. Here [] is an article that looks like it is talking about those patches. Here [] is a site that seems to explain memory management pretty well. I could try explaining stuff myself but I'd probably miss some of the nuances (I'm no OS expert by any stretch).

Re:Anti-Fragmentation? (1)

justthinkit (954982) | more than 6 years ago | (#22181650)

I am curious if any versions of Windows provide this feature. If not then chock one up for Linux...

Re:Anti-Fragmentation? (1)

Hatta (162192) | more than 6 years ago | (#22182196)

Why is memory fragmentation a problem? It's not like your RAM has to move a physical head to read non-contiguous blocks.

Re:Anti-Fragmentation? (0)

Anonymous Coward | more than 6 years ago | (#22182706)

It can effect the CPU cache. It is easier for things to fit in the cache if things are packed closer together, and the cache is about 100 times faster than RAM.

Reducing fragmentation also means that less RAM will be wasted. You could have problems if you try to allocate a megabyte sized block and all the RAM has been broken into kilobyte sized chunks.

Re:Anti-Fragmentation? (1)

Azarael (896715) | more than 6 years ago | (#22183738)

After your system has been up for a while, the list of 'free memory' updated by malloc() and free() gets fairly fragmented into odd sizes, that are spread out (especially if you aren't allocating in sizes near powers of 2). The more fragmented this list gets, the longer it takes for malloc to locate a block of memory that fits the size that you want. If I understand correctly, this change should make it possible to keep the free list more organized.

Re:Anti-Fragmentation? (1)

spitzak (4019) | more than 6 years ago | (#22185132)

malloc allocates pieces of the processes virtual address space to the program. All this fragmentation disappears when the program exits, so this is not exactly a problem with "the system being up for awhile". However similar problems exist in the kernel memory allocation and those problems do persist until the system is rebooted.

As far as malloc goes, I don't believe fragmentation really slows it down, it has algorithims for immediately identifying a block of sufficient size, and does not do a search. It may slow down freeing slightly. The real problem is that all the useful items end up spread over a much larger amount of virtual memory and thus uses a lot more of it. This means more swapping (further made painful as lots of those swapped pages are partially filled with pieces of free blocks), and it also means malloc may fail to allocate something because no free block is big enough and your program will crash. And it means inefficiency in loading stuff into cache memory.

The system has some advantage that the use of VM means that (in most cases) it does not need to fit an allocation request in one hole because it can split it up into seperate pages (exceptions are where hardware actually requires contiguous real memory addresses). Also it only works with pages so if swapping happens it does not waste time reading/writing the data in the holes. But as many pointed out, if the memory is not contiguous then it does not load into caches efficiently, as the modern caches are far larger than the pages.

Re:Anti-Fragmentation? (1)

X0563511 (793323) | more than 6 years ago | (#22184284)

Correct, but unlike your hard drive, RAM is fetched into cache for processing in "rows", and there is only room for so many rows. The more related stuff is together in RAM, the less "swapping" rows in/out of cache occurs. With multicore systems, this is even more important, as processors must synchronize to be sure they don't manipulate data cached by the other core... further dragging things down as more RAM access occurs.

Just like the hard drive is orders-of-magnitude slower than RAM, RAM is orders-of-magnitude slower than cache, is only read/writable 20% of the time or so (refreshing, row/column selecting, etc)

Re: Anti-Fragmentation? (2, Informative)

Dolda2000 (759023) | more than 6 years ago | (#22190322)

I'm not sure exactly how this works, so I can't go into all too nitty-gritty details, but basically, it's like this.

x86 CPUs (and probably amd64 as well) allow the kernel to choose between two page sizes: The usual 4 kB ones and a much larger size (I think it's 1 MB or so). The performance issue is that if the kernel can keep the physical RAM pages that back a large contiguous virtual mapping contiguous in physical RAM, it can use one of the jumbo pages instead of potentially hundreds of 4 kB pages. Doing so saves both page table space by itself, but more importantly, it allows the CPU to cache the page table in much fewer TLB rows. If a 1 MB mapping can be cached in one TLB row, the CPU won't need to swap TLB entries back and forth from the physical page table. Even if the page table may be cached in the normal CPU memory cache, it would still result in far better bus performance.

Re:Wow. Lots of stuff. tsarkon reports (-1, Offtopic)

Anonymous Coward | more than 6 years ago | (#22179892)

Tsarkon Reports 9 Step Yoda Grease 9 steps to greasing your anus for Yoda Doll Insertion!
v 4.50.0
$YodaBSD: src/release/doc/en_US.ISO8859-1/yodanotes/9stepprocess.sgml,v 4.50.0 2008/01/25 01:20:45 tsarkon Exp $
  1. Defecate. Preferably after eating senna, ex lax, prunes, cabbage, pickled eggs, and Vietnamese chili garlic sauce. To better enhance the please of this whole process, defecation should be performed in the Return of the Jedi wastebasket for added pleasure. []
  2. Wipe ass with witch hazel, which soothes horrific burns. (Rob "CmdrTaco" Malda certifies that his lips, raw like beaten flank steak from nearly continuous analingus with dogs, are greatly soothed by witch hazel.)
  3. Prime anus with anal ease. [] (Now Cherry Flavored for those butthole lick-o-phillic amongst you - very popular with 99% of the Slashdotting public!)
  4. Slather richly a considerable amount of Vaseline and/or other anal lubricants into your rectum at least until the bend and also take your Yoda Doll [] , Yoda Shampoo bottle [] or Yoda soap-on-a-rope [] and liberally apply the lubricants to the Doll/Shampoo/Soap-on-a-rope.
  5. Put a nigger do-rag [] on Yoda's head so the ears don't stick out like daggers!
  6. Make sure to have a mechanism by which to fish Yoda out of your rectum, the soap on the rope is especially useful because the retrieval mechanism is built in. []
  7. Pucker and relax your balloon knot several times actuating the sphincter muscle in order to prepare for what is to come.
  8. Slowly rest yourself onto your Yoda figurine. Be careful, he's probably bigger than the dicks normally being shoved up your ass! []
  9. Gyrate gleefully in your computer chair while your fat sexless geek nerd loser fat shit self enjoys the prostate massage you'll be getting. Think about snoodling [] with the Sarlaac pit. Read Slashdot. Masturbate to anime. Email one of the editors hoping they will honor you with a reply. Join several more dating services - this time, you don't select the (desired - speaks English) and (desired - literate). You figure you might get a chance then. Order some fucking crap from Think Geek. Get Linux to boot on a Black and Decker Appliance. Wish you could afford a new computer. Argue that cheap-ass discount bin hardware works 'just as well' as the quality and premium hardware because you can't afford the real stuff. Make claims about how Linux rules. Compile a kernel on your 486SX. Claim to hate Windows but use it for Everquest. Admire Ghyslain's courage in making that wonderful star wars movie. Officially convert to the Jedi religion. Talk about how cool Mega Tokyo is. Try and make sure you do your regular 50 story submissions to Slashdot, all of which get rejected because people who aren't fatter than CowboyNeal can't submit. Fondle shrimpy penis while making a Yoda voice and saying, use the force [] , padawan, feeel the foooorce [] , hurgm. Yes. Yes. When 900 years you reach [] , a dick half as big you will not have. []
All in a days work with a Yoda figurine rammed up your ass.



Tux is the result after trimming Yoda's ears off so that Lunix people don't rip themselves a new Asshole

What you can do with you ass after sitting on a GREASED UP YODA DOLL. []

y______________________________YODA_ANUS__- []
o_________________.'_:__`.________________y []
d____________.-.'`.__;___.'`.-.___________o []
a___________/_:____\_;__/____;_\__________d []
s_,'__""--.:__;".-.";:_:".-.":__;.--""__`,a []
e_:'_`.t""--.._'/@.`;___',@\`_..--""j.'_`;s []
x______`:-.._J_'-.-'L___`--_'_L_..-;'_____e []
________"-.___;__.-"__"-.__:___.-"________x []
y____________L_'_/.------.\_'_J___________y []
o_____________"-.___"--"___.-"____________o []
d______________.l"-:_TR_;-";._____________d []
a_________.-j/'.;__;""""__/_.'\"-.________a []
s_______v.'_/:`._"-.:_____.-"_.';__`.v____s []
e____.-"__/_;__"-._"-..-"_.-"__:____"-.___e []
x_.+"-.__:_:______"-.__.-"______;-.____\__x []
_v;_\__`.;_; I Yoda Have A _____:_:_"+._;__ []
y_:__;___;_;_Greased Up ME In __:_;__:_\:_y []
o_;__:___;_:_MY ASS! This Goes__;:___;__:_o []
d:_\__;__:__; On FOREVER!______:_;__/__::_d []

Ground Control to Yoda Doll Ballad : "Soddity"

Synopsis: --Major Tom goes to the bathroom and shoves a Yoda doll up his ass, and then gimps back to his desk to post AC Trolls on Slashdot. -Yoda Doll to Major Tom. - Yoda Doll to Major Tom. - Take your ex-lax bars and put my do-rag on. - Yoda Doll to Major Tom. - Commencing countdown, rope is on. - Begin insertion and may Goatse's love be with you. -- This is Yoda Doll to Major Tom, - You've rectally been flayed! - And the papers want to know whose shirts you wear. - Now it's time to leave the crapper if you dare. -- This is Major Tom to Yoda Doll, - I'm stepping through the door. - And I'm farting in a most peculiar way! - And my ass looks very different today. - For here... - Am I shitting in the tincan? - Far...too busy posting trolls. -- Slashdot censors you... and there's nothing I can do. -- Uploading one hundred thousand files, - I'm feeling very ill. - I don't think my feces know which way to go. - I can't tell my intestines from spaghetti- - code. Yoda Doll to Major Tom, your prostate's dead, there's something wrong, - Can you hear me, Major Tom? - Can you hear me, Major Tom? - Can you hear me, Major Tom? Can you hear... Am I shitting in the tincan? - My ass like a baboon's - Slashdot censors you - and there's nothing I can do.

The Yoda Pledge

I pledge Allegiance to the Doll
of the Greased Up States of Yodarica
and to the Republic for which it shoves,
one nation under Yoda, rectal intrusion,
with anal lube and ass grease for all.

hello.mpeg lyrics.
I'm doin' this tonight ,
You're probably gonna start a fight .
I know this can't be right .
Hey baby come on,
I loved you endlessly ,
When you weren't there for me.
So now it's time to leave and make it alone .
I know that I can't take no more
It ain't no lie
I wanna see you out that door
Baby , bye, bye, bye...

A picture of your ass after YODA. []

HOT COMMENT (0, Funny)

Anonymous Coward | more than 6 years ago | (#22179062)

Look on the bright side, a buggy Linux is still better than NT.

I'll shove my fist up your asshole, nigger. (-1, Flamebait)

Anonymous Coward | more than 6 years ago | (#22179066)

j/k! :D

but if you really want to do it we can.

R. Paul (anonymous)

Re:I'll shove my fist up your asshole, nigger. (-1, Troll)

Anonymous Coward | more than 6 years ago | (#22182102)

I've tried that on a black girl. Fucking hot. Too bad she wanted to commit.

Re:I'll shove my fist up your asshole, nigger. (-1, Troll)

Anonymous Coward | more than 6 years ago | (#22184810)

jump-kicked a gal in the twat once, myself. foot went right up there, it was the damndest thing. wore that girl like a snowshoe for a good half hour. true story.

Goatse! (-1, Flamebait)

Anonymous Coward | more than 6 years ago | (#22179072)

Goatse! []

Linus Torvalds announces 2.6.24 kernel (-1, Flamebait)

Anonymous Coward | more than 6 years ago | (#22179080)

Coming on the heels of the shocking recent admission that he was a buttfuckee of the late Heath Ledger, Linus Torvalds releases a new Linux kernel to distract his fans.

Will it work?

--Rip Ledger

Niggux kernel 0.0.1 announced (-1, Flamebait)

Anonymous Coward | more than 6 years ago | (#22179086)

After a watermelon and fried chicken feast, Leroy DuShiz announced the development of the Niggux kernel, a self-described "nigger's alternative" to Linux.

"To put it simply, it won't work," DuShiz was quoted as saying.


Merge Window? (2, Interesting)

AndGodSed (968378) | more than 6 years ago | (#22179088)

"Since I already had two kernel developers asking about the merge window and whether people (including me) traveling will impact it, the plan right now is to keep the impact pretty minimal. So yes, it will probably extend the window from the regular two weeks, but *hopefully* not by more than a few days."

Now THERE's confidence for you. Great news.

Re:Merge Window? (2, Insightful)

Anonymous Coward | more than 6 years ago | (#22179190)

I'm just wondering, should a core group be traveling together? What will the impact be if that plane impacts the ground?

Re:Merge Window? (5, Funny)

iMaple (769378) | more than 6 years ago | (#22179258)

There is a chance that some stupid airline CEO decided that their planes use The Evil Darklord's software for navigation. Of course we all know that noone would NEVER code a special condition in the software which says


On the other hand, there is nothing to worry about. This feature probably was shelved and is definitely going to be in the *next* version of the OS.

Re:Merge Window? (1)

WarJolt (990309) | more than 6 years ago | (#22179322)

*New builtin* The entire linux team was traveling to a conferance after releasing their final kernel. The pilot were recorded screaming "AHHHH BLUE SCREEN OF DEATH" Followed by an explosion of the right engine. The plane fell out of the sky moments later.

Re:Merge Window? (3, Funny)

Aladrin (926209) | more than 6 years ago | (#22179904)

Did you seriously just managed to misspell both words in 'News Bulletin'?

Re:Merge Window? (4, Funny)

Anonymous Coward | more than 6 years ago | (#22180314)

DId you seriously just manage to screw up correcting someone else?

Re:Merge Window? (3, Funny)

arkhan_jg (618674) | more than 6 years ago | (#22181074)

DId you deliberately screw up that correction of a correction? You did, didn't you.

Re:Merge Window? (1)

clem (5683) | more than 6 years ago | (#22183912)

This is just the kind of discussion that would be greatly enhanced if only there were a means of flinging poo over the Internet.

Re:Merge Window? (1)

ptudor (22537) | more than 6 years ago | (#22189878)


Re:Merge Window? (0, Redundant)

twilight00 (635706) | more than 6 years ago | (#22184744)

Your under arrest for ending this skit with a deliberate mistake.

Re:Merge Window? (0)

Anonymous Coward | more than 6 years ago | (#22185840)

You did, didn't you?

Re:Merge Window? (2)

Dolda2000 (759023) | more than 6 years ago | (#22190334)

Did you deliberately screw up that correction of a correction of a correction? You did, didn't you?

Re:Merge Window? (1)

mabinogi (74033) | more than 6 years ago | (#22180370)

No, it's a new built-in feature in 2.6.24

Re:Merge Window? (1)

WarJolt (990309) | more than 6 years ago | (#22189378)

Too much late night slashdotting.

Re:Merge Window? (1, Funny)

Anonymous Coward | more than 6 years ago | (#22179364)

Do they have wireless internet access on Mount Everest ? Its a well known prophecy that Linus can not die, till the dark lord reigns, so all he needs is internet. He'll be on a programming high I guess.

Re:Merge Window? (0)

Anonymous Coward | more than 6 years ago | (#22180290)

I'm just wondering, should a core group be traveling together?

Not to ruin everyone's "OMG teh Steve Ballmer will throw a chair at teh plane!" witticisms, but they're converging on Australia from their homes, not all sitting in the same cabin eating ziti and watching Everyone Loves Raymond.

& now back to our regularly scheduled programm (1)

RLiegh (247921) | more than 6 years ago | (#22189382)

OMG teh Steve Ballmer will throw a chair at teh plane!

carbon bootprint (0)

DrSkwid (118965) | more than 6 years ago | (#22179108)

keep up the good work !

Still no orinoco monitor mode (2, Interesting)

Anonymous Coward | more than 6 years ago | (#22179172)

The orinoco wireless drivers have supported monitor mode since 2004. Still not in the kernel today. Do any of the BSDs support monitor mode yet on this incredibly well documented chipset? I'll migrate if the answer's yes.

Re:Still no orinoco monitor mode (1)

Creepy Crawler (680178) | more than 6 years ago | (#22179246)

---The orinoco wireless drivers have supported monitor mode since 2004. Still not in the kernel today. Do any of the BSDs support monitor mode yet on this incredibly well documented chipset? I'll migrate if the answer's yes.

Good point. Would anybody more enlightened than I explain why the good orinoco drivers arent accepted in the kernel?

Evidently asking questions like this is flamebait... but why is this so WRT the kernel?

Re:Still no orinoco monitor mode (1)

MostAwesomeDude (980382) | more than 6 years ago | (#22179256)

What I would like to know, personally, is why the aircrack-ng patches for injection ( are still out-of-tree.

Re:Still no orinoco monitor mode (1)

Creepy Crawler (680178) | more than 6 years ago | (#22179296)

I can see why with aircrack...

Look at their release dates and patch revisions... none current. Kernel guys like seeing constant and timely patches. Community members who slack off are considered bad and all..

But I guess the wireless guys dont like these addons... Good for them, bad for us.

tickless kernel support? (1)

Mr2cents (323101) | more than 6 years ago | (#22179244)

Can anyone explain to me what "tickless kernel support" is?

Re:tickless kernel support? (5, Informative)

MostAwesomeDude (980382) | more than 6 years ago | (#22179274)

Can anyone explain to me what "tickless kernel support" is?
Sure. Basically, instead of having a regular tick in the kernel every handful of cycles to process interrupts and timers, processes are given long, dynamic timers with arbitrary lengths, which means that if an app wants to sleep for a relatively long period, it gets to sleep and not wake up the CPU, so the CPU sleeps longer and a lot of power is saved.

Re:tickless kernel support? (1)

JohnFluxx (413620) | more than 6 years ago | (#22180588)

Does this also mean that an app can also sleep for a very short period? Normally a sleep function is limited by the granularity of the kernel ticks. Will this make sleeping for, say, 1ms more accurate and reliable?

Re:tickless kernel support? (2, Interesting)

Andy Dodd (701) | more than 6 years ago | (#22180750)

There is another patch that adds high resolution timers to Linux. (Actually, another component of a gigantic patchset that has been rapidly getting mainlined over the past few kernel releases.)

I think CONFIG_HRTIMERS is already an option (may not default to on though). If it isn't, go find the RT_PREEMPT patchset. That includes (or if HRTIMERS is in the kernel, included) HRTIMERS, it's also where the NO_HZ option came from.

Re:tickless kernel support? (2, Funny)

Daimanta (1140543) | more than 6 years ago | (#22180918)

Basically, it prevents the computer from being ticked off thus preventing a hostile robot takeover.

Mirror list (0)

Anonymous Coward | more than 6 years ago | (#22179278)

Perhaps a mirror list would be appropriate: []

Re:Mirror list (2, Insightful)

TeknoHog (164938) | more than 6 years ago | (#22180056)

Is there an active and/or "official" Bittorrent site for Linux kernels? The local mirrors take some time to update, so global torrents would make more sense. Besides, people who download kernel sources are usually the kind that appreciate the benefits of BT and know how to use it.

Yay! (1)

Tribbin (565963) | more than 6 years ago | (#22179294)

It's always a nice read in the morning, that you don't need module-assistant anymore.

(rt61 Wireless)

ms hit-job? (0)

Anonymous Coward | more than 6 years ago | (#22179302)

all those developers in one place....

Bang up job (1)

Smordnys s'regrepsA (1160895) | more than 6 years ago | (#22179348)

Don't worry, I'm sure their rocket-launcher's computer's tracking interface will freeze up just moments before they press the fire button, so they'll have to fire it by visuals. Then, it will tragically fire 5 minutes later, while they're bashing the thing against the ground trying to get it to Just Work.

I am really grateful for this release (5, Funny)

eclectro (227083) | more than 6 years ago | (#22179416)

The weekend is almost here, and I am looking for something to do. I want to argue about the scheduler.

Re:I am really grateful for this release (1)

mightyQuin (1021045) | more than 6 years ago | (#22180246)

You just made my morning!
Let us also digress into a micro-kernel vs monolith-kernel discussion.

Re:I am really grateful for this release (4, Interesting)

ajs318 (655362) | more than 6 years ago | (#22180600)

Let us also digress into a micro-kernel vs monolith-kernel discussion.
Oh, that's an easy one. With a microkernel, you put up fences where they look pretty. With a monolithic kernel and loadable modules, you put up fences where as little stuff as possible has to traverse them. Ting! Next, please.

Re:I am really grateful for this release (1)

cbart387 (1192883) | more than 6 years ago | (#22186836)

Don't forget to compare the amount of _stable_ releases of Linux kernels (anyone have a number?) versus the GNU Hurd (zero). Didn't HURD development start almost a decade before Linus started on his work?

Re:I am really grateful for this release (2, Interesting)

0xABADC0DA (867955) | more than 6 years ago | (#22188128)

With a typesafe kernel like monotone or jxos everybody has a personal force field bubble around them that nothing crosses, and they just point at stuff outside their bubbles. Also, there are no laws because the force fields keep everybody perfectly safe all the time.

Re:I am really grateful for this release (1)

phobos13013 (813040) | more than 6 years ago | (#22180562)

would you believe i JUST upgraded to 2.6.23-r3 on Tuesday? I'm a kernel holdout, but hey, at least its better than the people who have been holding out to upgrade from 2.4.xx!!! Yea, the only reason I had to upgrade too was frickin gentoo dependency, I think because of KDE-base, whatever....

Re:I am really grateful for this release (1)

JackieBrown (987087) | more than 6 years ago | (#22188922)

You should have just skipped to the stable one then instead of using an outdated rc.

Re:I am really grateful for this release (1)

laejoh (648921) | more than 6 years ago | (#22180952)

I'm sorry, this is the abuse department. The argument department is next door!


Re:I am really grateful for this release (1)

mac1235 (962716) | more than 6 years ago | (#22181878)

Oh no, this abuse. Arguments are down the hall.

Re:I am really grateful for this release (3, Funny)

nagora (177841) | more than 6 years ago | (#22183864)

Arguments are down the hall.

No they aren't!

wireless drivers (1)

oliverthered (187439) | more than 6 years ago | (#22179832)

Could someone provide a quick summary of the wireless drivers that are now in the kernel as I don't know the chipset names for them and one of the sites appears to be /.ed.

Re:wireless drivers (2, Informative)

Jack Malmostoso (899729) | more than 6 years ago | (#22180304)

There you go:;a=tree;f=drivers/net/wireless;h=45adf0a95539e8a0ca5fddbb720319a9b7b39978;hb=HEAD []
If you want a suggestion on what to buy, support for Intel chipsets is very good. I have a 4965 device supported by iwlwifi and it works like a charm.

Re:wireless drivers (1)

schon (31600) | more than 6 years ago | (#22180730)

If you want a suggestion on what to buy, support for Intel chipsets is very good.
Unfortunately, unless you're an electronics engineer, purchasing a chipset doesn't do you very much good unless it's already on a card, and card manufacturers don't advertise which chipset is on a specific card (in fact, chipsets in many of the cheap cards get changed with other ones from batch to batch - I guess the cardboard boxes are more expensive to change than the electronics on the card.)

I'd love to get a wireless card with an intel chipset, but try finding a card that says they use them.

Re:wireless drivers (1)

Enleth (947766) | more than 6 years ago | (#22180996)

In the case of a laptop, that's easy. Intel makes the whole MiniPCI card and markets it with their brand. With a desktop, you can either try to find a working PCI card, or just... Well, buy a MiniPCI->PCI converter for $10 or so and you're done. That's what I did.

Re:wireless drivers (1)

leoxx (992) | more than 6 years ago | (#22184508)

Does the 4965 driver support LEAP yet?

Re:wireless drivers (0)

Anonymous Coward | more than 6 years ago | (#22180924)

From Google cache (of [] ): ...
  In Linux 2.6.22, the mac80211 (formerly d80211) wireless stack was
      merged, but not many drivers that use this new stack have been merged
      (only one). Linux 2.6.24 will have a lot of new wireless drivers using
      the new stack; 2.3 MB of source files in total:
          * iwlwifi driver for the Intel PRO/Wireless 3945ABG/BG Network
              Connection and Intel Wireless Wifi Link AGN (4965) adapters
          * rt2x00 driver for Ralink wireless hardware (rt2400 pci/pcmcia,
              rt2500 pci/pcmcia, rt61 pci/pcmcia, rt2500 usb, rt73 usb). Check
              the hardware matrix (commit)
          * adm8211 driver for the ADMtek ADM8211x based wireless cards. These
              are PCI/mini-PCI/Cardbus 802.11b chips found in cards such as:
              Xterasys Cardbus XN-2411b, Blitz Netwave Point PC, Trendnet 221pc,
              Belkin F5d6001, SMC 2635W, Linksys WPC11 v1, Fiberline FL-WL-200X,
              3com Office Connect (3CRSHPW796), Corega WLPCIB-11, SMC 2602W V2
              EU, D-Link DWL-520 Revision C (commit)
          * b43 driver for modern BCM43xx devices. This driver supports the
              new BCM43xx IEEE 802.11G devices, but not the old IEEE 802.11B
              devices - those are supported by the b43legacy driver. This driver
            uses V4 firmware, which must be installed separately using
              b43-fwcutter (commit)
          * b43legacy driver for legacy BCM43xx devices from Broadcom (BCM4301
              and BCM4303) and early model 802.11g chips (BCM4306 Ver. 2) used
              in the Linksys WPC54G V1 PCMCIA devices. Newer 802.11g and 802.11a
              devices need the b43 driver. This driver uses V3 firmware, which
              must be installed separately using b43-fwcutter (commit)
          * p54 driver for prism54 softmac pci/usb hardware (commit)
          * Driver for Marvell Libertas 8385 Compactflash 802.11b/g cards
          * Libertas sdio driver (commit)

      There're also a lot of network (non-wireless) drivers being merged,
      look at the section 2.14, "new drivers" ...

tuxonice? (1)

Lord Kano (13027) | more than 6 years ago | (#22180546)

Does anyone have an idea when tuxonice will be re-merged? I know that most of the heavy lifting is done is userspace, but it would be nice if we didn't have constantly track down patches.


Tickless kernel now supports high res timers (1, Informative)

Anonymous Coward | more than 6 years ago | (#22180634)

In previous non-realtime Linux kernels the calls to nanosleep() or usleep() that were less than one tick (10 milliseconds) were rounded up to 10 milliseconds. This can be very frustrating when writing embedded software that needs responsive timers. Now the resoultion is down into the microsecond range with current CPUs and will scale down even further with faster CPUs.

Next "stable" release? (0, Flamebait)

Spazmania (174582) | more than 6 years ago | (#22180740)

When is the next "stable" release, a la 2.6.16? I got fed up with the earlier 2.6 kernels and have been sticking with 2.6.16 until there is another release in which the devs make another serious attempt at stability.

Re:Next "stable" release? (1)

Hatta (162192) | more than 6 years ago | (#22182292)

It would be nice if you described the problems you've had with recent kernels. I haven't noticed any instability.

Re:Next "stable" release? (1)

Spazmania (174582) | more than 6 years ago | (#22187066)

Random kernel lockups with a 9-way IDE software RAID on a 1.2ghz Athlon under 2.6.17 and 2.6.18 is the first thing that jumps to mind. Massive interrupt error counts when using more than one channel on Promise IDE controllers on the same.

I haven't tried it on 2.6.>20 and I don't plan to until someone does like was done with 2.6.16 and declares a stable version that will continue to receive bug fixes but not destabilizing new features.

I understand that there are some folks who find it immensely entertaining to try out the latest, greatest kernel but I'm not one of them. I have better things to do with my time.

Re:Next "stable" release? (2, Informative)

Randle_Revar (229304) | more than 6 years ago | (#22184736)

I haven't seen stability problems in 2.6 for a long time. Lately I have been using the 2.6.24 (pre-release) kernel from Ubuntu Hardy (I'm on Debian Sid), and I haven't had any trouble with the kernel. and Mozilla nightly problems, sure. But no kernel problems.

Re:Next "stable" release? (1)

WK2 (1072560) | more than 6 years ago | (#22186150)

That partly depends on what you want to do. I'm just a regular guy, and the kernels in Debian Stable and Debian Testing work for me. I don't know what to say if you're trying to write a device driver or something. But one of the things that distros are for is a stable Linux kernel.

Re:Next "stable" release? (1)

Spazmania (174582) | more than 6 years ago | (#22190792)

Which is just a swell theory until you realize that most distros (I'm lookin' at you, Red Hat) do a lousy job of stabilizing the kernel for release. Even with one that does it well (debian) its still unhelpful if you happen to need to run several distros and several versions of each (as is not uncommon in larger deployments) and would like a single kernel that's reliable on all of them.

eCryptfs persistent files (3, Informative)

omnirealm (244599) | more than 6 years ago | (#22180926)

In 2.6.24, eCryptfs overhauled its I/O mechanism with the lower filesystem (check out fs/ecryptfs/read_write.c). It used to directly manipulate the lower inode address mappings, which caused problems with certain filesystems like NFS (they like to be the only filesystems directly locking, reading, and writing their own address mappings). Now it opens a persistent lower file for each and every stacked inode and uses that for all I/O with the lower filesystem. This significantly decreases the complexity of the execution path for reading and writing the lower data. Together with this patch [] , eCryptfs now works pretty well on networked filesystems like NFS and CIFS.

There is another patch to provide HMAC integrity enforcement [] , and the kernel GIT tree for eCryptfs has a branch indicating that filename encryption is being worked on.

Video drivers (0)

Anonymous Coward | more than 6 years ago | (#22181906)

This seems like fine news item to ask this in: the X windowing system is a user space system, right? How does it then communicate with video hardware directly (x drivers)? Or are the video drivers part of the kernel?

Re:Video drivers (1)

tamyrlin (51) | more than 6 years ago | (#22182220)

X usually opens /dev/mem and used mmap() on it to be able to read and write to the appropriate place. If you use a card with DRI support in Linux you will have some kernel support as well.

(Unless you use vesafb or some similar video driver.)

does Debian/Ubuntu make upgrading easy too? (0)

Anonymous Coward | more than 6 years ago | (#22182428)

I've been a Slackware user since 1994 and have recently switched to Ubuntu. I don't think I'll go back to Slackware; as much as using it has taught me everything I know about Linux, I'm just sick of manually doing everything. I love how easy it is to install software in Ubuntu (technically it's a Debian feature, yes?) compared to how I had to do it in Slackware.

Is there anything in my Ubuntu installation I don't know about that makes upgrading and installing the kernel without problems easy? It's not that I can't do it manually -- it's just that I expect convenience now; I think I earned it.

Re:does Debian/Ubuntu make upgrading easy too? (1)

Randle_Revar (229304) | more than 6 years ago | (#22184594)

You mean outside of waiting for an official package?
There is a package called kernel-package that makes thing a little easier and produces a .deb that you can install with "dpkg -i" [] []

or []

working great here... (2, Informative)

FudRucker (866063) | more than 6 years ago | (#22184612)

i build as much as possible the only required support for my hardware specifics as modules except for ext3 filesystem support (built in to the kernel itself) thus making an initrd unnecessary, my kernel is nice & light, highly responsive and boots in just about 10 seconds, and the kernel is only 1.1 megs in size & /lib/modules/2.6.24 is 11 megs...
Load More Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>