Slashdot Mirror
Linux Kernel 2.2.10ac11 Released
Full details on this page at Linux Today, where Alan Cox says, "A lot of updates
here. I've not chased down the lockd bug reports yet, nor
the umount nfsd bug that is trapped by the SLAB debugging.
This mops up most of the stuff while I've been occupied
elsewhere. Chances are given the number of updates there
will be a few glitches in it. Have fun testing."
Jeren is a near-perfect sendup of the not-so-stereotypical monomaniacial computer programmer...
Umm... Did I miss something, or is there no 2.2.10 kernel available? If that is so, why is it being withheld (or does it exist)?
it's a good idea, I'd rather hear about linux kernel patches than more Micros~1 crap or legal nonesense!
This man needs to take longer vacations. Trying
to be unselfish here.
> then go read freshmeat
Yes. Some of us don't care at all about linux kernels. People that do should know where to find/how to get announcements about new releases.
I wonder when we start to post *BSD "daily CVS update output" or mails from the source changes mailinglist as news:
"This is great news for all you NetBSD guys out there: A new revision of src/sys/uvm/mmap/mmap.c has just been checked in. Sup your new kernel now - Yeah!"
That's why people with better things to do than download and compile kernels (most people, I'd imagine) use these things called "distributions". The distributor makes the decisions about which versions of software are stable. Makes sense to me...
Big deal. Linux has had gigabit for a while (but then, so has FreeBSD).
I build them on SMP boxes only occasionally, but
I normally get lots of mail if it breaks 8)
Send me a bug report, trace and config
Actually, Alan is running the 2.2 tree now. Linus is busy with 2.3.
Not anymore. Linus has said that whatever Alan says for the 2.2 kernels goes (not that Linus wouldn't point out if something is a bad idea, though ;-). So, basically, think of the ac stuff as being like Linus' pre-patches.
The big thing that might have been worth pointing out though, is that the file corruptions some people were seeing in 2.2.9, 2.2.10 was allegedly fixed in -ac10 or -ac11. I don't know the details ATM, I lost track of that thread on l-k a long time ago :(
I shouldn't be biting for such an obvious troll, but if you don't like roblimo you dont have to ever read a post by him again.
It's called log in and edit your prefs.
2^5
It was a newbie mistake on my part. Sorry. I let my personal interests creep in. What caught my eye was that radio modem support is included in the most recent AC patches, and my biggest current hardware desire, er, I mean need, is a Linux notebook equipped with a radio modem. ;-)
Also, only 2.2.10 has the fix for that latest Denial-of-Service bug in the networking code.
Given how few people has problems with 2.2.10, I would recommend that version - even though it might fail on a few, it has at least as good a chance of success as any previous version.
--
That's why I consider the current Linux release cycle to be a failure. You should not have to have a list of which kernels are stable or not, since 2.2.x is supposedly the stable tree. ALL kernels released in 2.2.x should be 99.9% stable. In other words, more ac prepatches would be nice, and delay the "official" kernel releases until you really have something worthy of the "stable" label.
When you have a stable tree with severe bugs, that doesn't make people confident in your product. I personally wouldn't recommend anybody use anything higher than 2.0.37 for any important applications, since the 2.2.x line is simply not stable enough.
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
Sure, I understand that there's some limit to the testing that can be done, but more than is currently done is possible. With companies like RedHat, Caldera, and VA having quite a bit of money, they could at least try out 10 or 15 different hardware configurations, not just what they happen to have on their personal boxes at the moment. Also, no new features should be added to 2.2.x. They should go into 2.3.x.
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
Then perhaps Linux and Alan Cox need to take some lessons from Red Hat. I'd rather run a stable 2.2.5 that has some of the 2.2.6+ features than run a 2.2.10 (with very few additional features) that's a lot less stable.
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
NOOOOOOOOO!!!!! DO NOT RUN WITH 2.2.8. Sorry to shout there, but 2.2.8 has _severe_ memory issues. So in that case, go back to 2.2.7 :) But, only sporadic people are having fs corruption in 2.2.9/10 so I'd recommend using 2.2.10 (or maybe this patch, haven't looked at it yet).
Yeah, Slashdot probably shouldn't make a habit out of announcing 'ac' releases, but it would be good to pound on this one a little. Given all the glitches with the 2.2.x tree, it's important that we get a rock solid 2.2.11. The best way to make that happen is to try 2.2.10ac11 and report any bugs.
It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
Has anyone else noticed that the 2.2.10-ac series kernels don't seem to like being built as SMP? I've tried 2.2.10-ac3, ac10 and ac11 on 2 different SMP systems (built as SMP) and it dies quickly (doesn't even finish the kernel-boot phase) with a NULL pointer dereference. Anyone else seen this?
Sam: "That was needlessly cryptic."
Max: "I'd be peeing my pants if I wore any!"
In a previous post I said
"in a post moderated down for other reasons bugg asked "Anyone know about the Intel Etherexpress 10mbit cards? I guess this is off topic, but i just got some and i wanna know if any of the latest kernels include it.
-bugg" "
As I said, the original post was moderated down for reasons unconnected to the question about NIC cards, but I felt that in a discussion of a new kernal a question about what hardware it supports was perfectly valid, so I reposted it under my name (minus the first post garbage that got it knocked down in the first place) in order to "promote" it so that someone who knew the answer might see it. As someone else observed, this thread seems to have attracted a record number of "off-topic" (to put it politely) posts, most of which had no content worth sifting out. Why someone felt it worthwhile to "burn-up" 20% of their moderation points to knock it back down when there were so many other more worthy targets I'm sure I don't know.
I see even classic Slashdot is now pretty much unusable on dial up anymore.
If you see a linux kernel numbered with an ac__ at the end, like "2.2.10ac11", it means that it's based on 2.2.10, patched with the eleventh patch written for that kernel by Alan Cox (ac). Since it's not an official "Linus-blessed" version of linux, he increments his own counter after the "ac". Usually, most or all of alan's patches get included in the following version of linux (in this case, that'd be 2.2.11).
For freedom,
kronos.
Here's a few that might interest you:
...
...
...
...
...
... Submitted by: Matthew Dillon <dillon@backplane.com>
From: Bill Paul
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Log:
This commit adds driver support for the SysKonnect SK-984x series
gigabit ethernet adapters. This includes two single port cards
(single mode and multimode fiber) and two dual port cards (also single
mode and multimode fiber). SysKonnect is currently the only
vendor with a dual port gigabit ethernet NIC.
From: Bill Paul
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Log:
Make the Winbond ethernet driver work on FreeBSD/alpha. Also added
bridging support while I was in the area.
From: Kirk McKusick
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Buffer flushing has been reorganized. Previously buffers were flushed
in the context of whatever process hit the conditions forcing buffer
flushing to occur. This resulted in processes blocking on conditions
unrelated to what they were doing. This also resulted in inappropriate
VFS stacking chains due to multiple processes getting stuck trying to
flush dirty buffers or due to a single process getting into a situation
where it might attempt to flush buffers recursively - a situation that
was only partially fixed in prior commits.
A small race condition was fixed in getpbuf() in vm/vm_pager.c.
Submitted by: Matthew Dillon
From: Kirk McKusick
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Log:
These changes appear to give us benefits with both small (32MB) and
large (1G) memory machine configurations. I was able to run 'dbench 32'
on a 32MB system without bring the machine to a grinding halt.
The revolution will be mocked
Anonymous Coward, obviously.
pooptruck
Thank god for the Compaq Smart2 array driver support. I've got a few "outdated" Proliants just looking for something to run.
--
Business. Numbers. Money. People. Computer World.
2.2.10 was released on June 13, based on the timestamps I see at my kernel.org mirror site. However, there are some obscure file corruption bugs in 2.2.9 and 2.2.10 that they've been working on finding, so I would consider 2.2.8 to be the latest stable version. That bug is the reason you haven't seen 2.2.11 in over a month.
Personally, I live on the edge with 2.3.11-pre5. So what if FAT file system support is broken? That's what development kernels are all about.
Alan may be mostly running the 2.2 tree. He certainly ran the 2.0 tree long after Linus had moved totally to 2.1. However, when it comes time to release the next official version, Alan still gets Linus's approval first.
In many cases, the AC patches include things that Linus has specifically said won't make it into his kernel, or at least not in the 2.2 kernel. I'm not sure if that is still the case, though, now that 2.3 is underway--most of those patches that Linus wasn't ready to accept into 2.2 are now in 2.3.
Anyway, we can expect to see Alan working on both 2.2 and 2.3 until 2.4 comes out.
> And (someone correct me if I'm wrong), eventually his modifications get merged in with Linus' work.
IIRC, his doc for 2.2.10-ac10 said that most of the changes had already been incorporated into the 2.3 tree.
Sheesh, evil *and* a jerk. -- Jade
The AC stands for Alan Cox, everyone's second favorite Linux kernel developer. He has his own patches to the kernel that he distributes. And (someone correct me if I'm wrong), eventually his modifications get merged in with Linus' work. Personally, I don't know why this kernel was posted as a story. AFAIK no other ac patches have been posted, regardless of how major the update was.
So what you want is something like Kernel Newsflash?
Phobos - Greek word for fear or flight
What does the ac11 in the version number stand for?
Does this mean that this patch fixes the 2 gig file limitation now? Where else can I find info about this?
I have not seen an Alan Cox enhancement patch posted here, well, never to my recollection... Is there something especially big about this one?
XML is like violence. If it doesn't solve the problem, use more.
Then turn off those stories in your preferences. Or just ignore them (like I do to most Linux stories).
-ElJefe
It looks like FreeBSD is doing some heavy stuff. Gigabit ethernet adapters sounds cool.
Very interesting and amusing.
//Pingo
--- Linux or FreeBSD, it's like blondes or brunettes. I like both. ---
I would like to see more of what the *BSD guys are doing. I know that they are also doing great stuff. Some is better than Linux and some isn't.
It would need an update to the slashdot site. Split slashdot into departments. One Techie department where Linux/*BSD can discuss things close to their hart. Stuff that is to heavy for the causal visitors to slashdot.
I guess the guys running slashdot pretty well knows what the other departments should be.
//Pingo
--- Linux or FreeBSD, it's like blondes or brunettes. I like both. ---