Slashdot Mirror
linux 2.2.9 Released
rohirrim was the first
to let us know that the hit hot single 2.2.9 has made its
debut on the usual FTP sites. So if you're the type
that desires a newer stable kernel, get to it.
← Back to Stories (view on slashdot.org)
There once was a man from nantucket
who thought "one more compile won't muck it"
He said with sadistic gaul,
as he typed "make install"
"If this breaks an inode, just fsck it".
There were some changer to buffer write back .
( fs/buffer.c ) in the 2.2.8 , which were
reverted back in 2.2.9
I believe there was a good reason for that.
I suggest staying with 2.2.7 or upgrading to 2.2.9.
Just to be on the safe side
stein
Yes, Don't run 2.2.8 or 2.3.0!! Or at least,
don't do any heavy disk IO while running them.
Hopefully 2.2.9 is a fix for the bug in the
disk buffering code.
A kernel a year
Would be too much, I fear
All hail to the core
Whose black box we adore
Let's promote Free-BS-dee
without Linus envy
Both plans do the job
you fscking snob!
Lots of people download the kernel. It's much more efficient to just have tarballs for people to download. :)
Yup. I grabbed both of them, for different machines. There were already three pre-patches out towards 2.3.1, anyway... the 2.3.1 final patch presumably would contain all of that stuff, plus the vital bit that rushed 2.2.9 out.
I suppose I could diff the two patches and see how much overlap there really is, but I'm too lazy to figure out the switches that would give me some useful information...
But my kernel's done cooking... reboot time...
According to "finger @linux.kernel.org", 2.3.1 is out as well. I suspect that whatever problem (I heard something about filesystem corruption?) that caused the quick release of 2.2.9 encouraged a similar release on the 2.3 tree... 2.2.8 and 2.3.0 are identical, after all...
And anyone who's got a problem with letting people know that there's a new dev kernel out can flame away. I've got a thick skin.
Posted by Myrdraal:
Kind of unlikely. The only change was one variable for char to signed char... Actually, I probably shouldn't have even noted that change because I believe chars default to being signed.
-Myrdraal
I hope not. The last thing we need is Microsoft driving the development of Linux. Since there are no shareholders involved, Linus has the option of just ignoring them, and working on things that are the most important, instead of putting out fires in the press.
TedC
I have no clue abt coding, but would the recent release of the quake3 test have anything to do with this? yummy...
-----
If Bill Gates had a nickel for every time Windows crashed...
I'm completely confused by the negative comments here. What is the problem? If you're not interested in a particular revision of the kernel, avoid downloading it.
Unless you're completely anal retentive, it shouldn't matter if you miss a kernel revision. Just wait until you see something worth upgrading to, and be happy that those who had problems (Oracle, hd buffer stuff) had it fixed before they even had time to complain.
----------------- "I have a bone to pick, and a few to break." - Refused -------------------
This release may fix the filesystem corruption problem that some people had with 2.2.8. It may be worthwhile looking at it if you installed the previous version.
Consider the whole Mindcraft deal. Now consider that, according to ESR's CandB paper that part of the motivation for creating open source software is satisfaction of ego. Now imagine you're kernel hacker and MS has, either by design or accident, thrown down the gauntlet. Note to large, Redmond based software companies: Mindcraft is a loss even if it's a win. Let it lay....all you're going to do is make it worse.
Many thanks to all the kernel hackers out there!
Keep up the great work and don't let all this bickering
about version numbers and too frequent releases get you down!
Just because there's a new kernel is no reason to upgrade.
;) for it...
I'd agree for production boxen, but the whole idea of new kernels is to throw them over the fence and see what your users throw back.. it's a feedback loop, which helps the development process, as no single developer (not even MS, apparently) can test under as many different configurations as we can.
If you can run the new kernel, you probably should, but don't sacrifice your production server uptime (or your job
Hey Rob & Hemos,
:-)
How about posting the Linux Kernel news under a different heading than "Linux" (perhaps "Linux Kernel")? That way anyone who feels that kernel updates are not newsworthy can filter them out and not bother complaining about it to those of us who find it interesting.
My own opinion: I happen to enjoy seeing the new Kernels posted here. It often prompts some good discussion, even though there are quite a few "who cares about new kernels" threads. Also, frequent kernel updates are one of the beauties of Linux. Quick features and bugfixes...gotta love it! Besides, nobody says you MUST download newer versions anyway. If it works for you, stick with it unless you really want to try it out.
Cheers,
Vic
It seems to me like there are often interesting discussions regarding the changes in the newly released kernels, here on slashdot.
In that sense, I think Slashdot as a forum works well. As long as there are people who post with interesting content, there is obviously some interest in the event.
Use /sbin/ipfwadm-wrapper and you don't have to change a thing. No, you won't get the fancy IP chains, but everything will work at least and you can have a life instead of reading more documentation...
-Mike
Contrary to popular belief, upgrading to each minor kernel revision is not required by law!
The Kernel Gestapo is not going to bust down your door and demand to see your papers and ask why have you not upgraded to zee newest release?
Just goes to show that when there is a fix for something, or something new to add, it's out there as soon as possible. Not like Microsoft, who waits until they feel good and ready to release something, if at all. Remember the y2k fix for Win95 they held? That won't happen with linux.
And like upgrading a kernel is all that big of a deal? Grab the source patch, recompile, and reboot. Compile the option to use different module versions, and you don't even have to re-compile those. How easy is that?
The patch is teeny. As someone else already
posted, it should have been a pre-patch.
Most of it's m68k and arm updates... there's a
few other tiny patchlets for tcp.h, fs/buffer.c,
aha152x.c, ide.c, ide-dma.c, and ip_masq_quake.c
inside. That's about it.
Unless you're having trouble with 2.2.8, triggered
by anything listed above, don't bother downloading
it. Wait for the next one.
- Preferences: Solaris 10 (servers), Ubuntu (desktops), Solaris 11 (personal servers) -
Agreed.
I think the Mindcraft (and other tests showing relativly poor linux performance) is really great for pushing development ahead.
Among the FUD on the MS page in response to the Mindcraft (and other) benchmarks there are some valid points that I hope can be addressed with the newer kernels like filesystem and memory shortcommings.
------ Live free or Die!
(licks the finger and touches the kernel with it) Hshhhh! Piping hot! Not surprising, considering the speed it arrived at... At this rate, the kernels will soon start burning through the bottom of my hardrive!
Seriously , though: Could it be that the kernel folks are trying to fix some issues in time for the 3rd Mindcraft test?.. Is that why the upgrades are coming at such speed?
--
--
Victor Danilchenko
Uh, what does the GPL have to do with anything?
;-)
XFree86, among a ton of other common programs, are not GPL either. Quick! You better delete them before anybody finds out you're using non-GPL'd programs!
Hang on a minute, your computer hardware was not released under the GPL either! Better put it back in the box, take it back to where you bought it, and tell the salesperson that you're too stupid to own a computer.
Matt
What is everyone complaining about? I think this simply has to do with the fact that the 2.2 series added a whole slew of stuff that was in the dev series. This means that now all of the sudden a bunch more people are using all of this previously devel code, and most likely finding bugs and other issues.
I would much rather have 10 kernel updates come out in 3 1/2 months, then say three come out in 10 months. If you don't need the new stuff or don't like screwing around with rebuilding your kernel, then don't worry about the new release unless you know you need it. Enough said.
I think I would be in heaven if only I could find a Linux job.
I doubt this would be the case, unless the kernel folks didn't read
Mindcraft's publication on the matter.. (which is also doubtful, as
you'd think that if they were releasing the patches for it, they'd at
least have found out what the nitty gritty details..) (hmm, nice
circular piece of logic on my part there, but I hope you catch my
drift...)
Specifically, the Mindcraft paper stated that the Linux team would be
unable to use any patches not publicly available before April 20.
On http://www.dyer.vanderbilt.edu/server/udma/ you can find the same patch for 2.2.8 (expect 2.2.9 soon). I use it and it works fine.
I don't understand it. There are a lot of new kernel releases coming out lately, one might say that they are being released one after another in rapid-fire succession, however, wouldn't it be much easier to use CVS (GNU), perhaps along with CVSup (which is essentially 'cvs update' on steroids - including an optional X UI and protocol compression) to keep its users up-to-date on the kernel sources? I believe I understand the Linus-final-word structure, but a one-man CVS operation would still be worth it if one can download only the latest updated sources from the tree.
This is, as some of you may know, the way FreeBSD keeps its whole OS tree (since it is, after all, one integrated operating system), as well as splitting the source tree (kernel and userland) into CURRENT, STABLE, and RELEASE (essentially a frozen -STABLE from a specific time), and I think it would be very valuble for Linux to do the same thing.
Comments? Flames?
Interesting note: FreeBSD mirrors use CVSup to update a CVS tree, so that users may use those mirrors which have mirrored the entire CVS tree on their system, to download either just the latest sources, or to download the actual CVS tree, on which one can make the usual CVS operations (useful for extensive work on things, such as the FAQ or Handbook, which I happen to work on)
Some people have had problems with Oracle on Linux after upgrading to 2.2.9. Matthew (mattshouse.com, an Oracle / Linux) emailed Alan Cox with some details, and received this response, which seems germain to this discussion ...
(Matthew wrote)
>I just received this e-mail from Alan Cox:
>>2.2.8 has an fs deadlock and an exploitable remote network crash problem.
>>2.2.9 will be appearing rather shortly
(end quoted email)
Oracle users should definitely avoid 2.2.8, and it would seem that the problems Alan notes could affect non-Oracle things as well, hmmm?
Best Regards,
BillyG.