Slashdot Mirror
Linux 2.6.0-test3 Released
xepsilon writes "Linux 2.6.0-test3 has been released. Grab your copy off your local kernel.org mirror and report those bugs! Remember, any bug you find that you don't report is likely to not be fixed in the next release if you don't report it. See the ChangeLog for more details."
Remember, any bug you find that you don't report is likely to not be fixed in the next release if you don't report it.
:P slashdot is replacing fark for the laugh factor
Time for some homebrew babelfish
Translation: Any bug you don't report (But hundreds of others will) might not be fixed, that is, if you don't report it!
geeze
Excuse me, I don't mean to impose, but I am the ocean
Great!
But before I download this, where do I pay my SCO licensing fee?
This is the correct link to http://kernel.org
What support tools need to be upgraded? I assume modutils. Which version of GCC is needed? What about stuff like ip_tables, are any changes needed? Maybe someone could post a quick summary of the "gotchas".
"Remember, any bug you find that you don't report is likely to not be fixed in the next release if you don't report it."
If I don't report it, it won't be fixed if I don't report it?
Just making sure I need to submit all bug reports twice.
If found a bug, by you it is, report it you must, or fixed not it will be. This I sense in the Force. Chances you must take not, that reported by others it is, such a bug. Vigilant always, a kernel tester must be.
(For those of you who report "Jedi" as your faith on the Census).
SCO employee? Check out the bounty
But what if I do find a bug that I do report, is it then fixed if I do report it after I've reported it? Or something.
My head hurts, I think I'll go and lie down now.
There are 10 kinds of people; those who know ternary, those who don't, and those now hunting for a dictionary.
You won't see an official rpm from redhat on an experimental kernel. typically, redhat released kernels lag a couple months anyway. You might find 3rd party RPMs, but your mileage will REALLY vary.
You really don't want to install an rpm of an experimental kernel anyway, you should build it yourself. If you are not familiar with building your own kernel (not trivial, but not that difficult) then you should probably stick with stock kernels, since experimental and/or release candidates tend to have bugs that can break things. Also, anytime to upgrade from 2.4x to 2.6x you can expect potential to break things anyway.
The best thing is to install the source on a spare box, and compile it yourself, or learn how to if you don't know how. Its not THAT hard, but expect to screw it up a few times at first. Just be sure to update GRUB or LILO (and run lilo).
I use pretty much stock kernels now, although I will build them on my test boxes, to get a better understanding of changes. The stock kernels from RedHat are pretty good and functional from my experience, unless you need UberOptimized kernels.
It will likely be a few months AFTER 2.6 is released officially before RH issues and official version. Keep in mind that any 2.x.0 kernel is going to have the MOST bugs anyway. Most production boxes should wait for 2.x.2 releases anyway, unless they absolutely NEED the new features, or you love living on the edge (which if that is the case, you would be building your own kernel anyway).
Tequila: It's not just for breakfast anymore!
Remember, any story posted to slashdot that isn't edited is likely to have errors if it isn't edited.
Thank you.
RedHat's Arjan van de Ven has RPM's here.
But: Half the fun of Linux is hand-tweaking your own kernel setup and compiling your own. Why not just do that? =)
Also, remember that you need to upgrade other pieces as well when going from 2.4 to 2.6 - the module utilities in particular. They are now known as "module-init-tools"
My opinions may have changed, but not the fact that I am right! =)
Remember, any text that you send using the HyperText Transfer Text Protocol, if you send it in text, is send in text.
Have Linux installed at your place in Amsterdam, for cheap
And in case it's fixed later, it is broken right now. What's "htttp"? "hyper text texting protocol"? :)
/. decided to find out ;)
It's the new web protocol. It seems that a company named SCO has claimed IP rights to the http protocol, and is demanding $3 in licence fees per connection. Some speculate they will even claim any other protocol providing weblike functions to be a derivative work, but that's yet to be confirmed. So
Kjella
Live today, because you never know what tomorrow brings
Remember, any bug you find that you don't report is likely to not be fixed in the next release if you don't report it.
I found a bug that I didn't report. Now that I have reported finding a bug that I did not report, that means that the bug will be fixed, right?
However, if you do want an rpm, there are people at Redhat who do build them ;)
You can download from here.
"Backups are for wimps. Real men upload their data to an FTP site and have everyone else mirror it." -- Linus Torvalds
Then link to /mirrors/ instead of the top of kernel.org. (Some time in the past I was unable to contact kernel.org for days, so I started mirroring the list of mirrors near my country.)
Do you care about the security of your wireless mouse?
if you ever unpicked a RH 2.4.x kernel in RH8 or 9, you'd notice more similarities to the 2.5.x tree than 2.4.x
They have picked several pieces of 2.5 to put in their 2.4, but I see this as a good thing, not a bad. This allows them to go to market on the cutting edge, but still tested and stable. Technically, EVERY Linux kernel is experimental to a degree, since they are still developing it. But from my experience, RedHat kernels are pretty stable, and easily upgraded with an RPM. Not perfect, but neither is any kernel you don't roll on your own. Frankly, they are probably more stable than 90% of the home rolled kernels, too.
I have been using stock RH kernels on one 7.2 server for several years (and on other servers for less) and have never had a problem with them. I install with the RPM and reboot remotely, and haven't had one fail to boot correctly (I DO have someone nearby to call on the phone if it did crap out). Not perfect, but worth the $60 a year per box I shell out for RHN, and even better for the average home hacker downloading for free.
I'm not smart enough to be a kernel snob, I'm too busy using Linux in the business to actually earn money. Personally, I like Redhat even tho they are not perfect.
Tequila: It's not just for breakfast anymore!
0.5) Make sure I'm running ext3 or reiserfs
.config, and any messages that you can maybe extract from dmesg (if it left any there).
6. Send an email to linux-kernel@vger.kernel.org
describing the problem - so maybe it can get fixed.
Developers don't have time to test every piece of hardware.
If you do send an email I recommend listing exactly what airo card you have, including your
If you want to try it again, I assume you get a big OOPS screen with a bunch of stuff like Stack Trace on it.
Copying this down and sending it is very valuable information to debugging.
Make sure to activate CONFIG_INPUT, CONFIG_VT, CONFIG_VGA_CONSOLE and CONFIG_VT_CONSOLE in the configuration. You can find out if you did that by looking into your .config file.
/dev/pts. The devfs in kernel 2.4 used to have it's own devpts, but this is no longer the case.
Do you use devfs? Than you will want to compile devpts, too, and mount it to
Being a LKML lurker, here are a few of the new features.
A kernel-based trollkit eh? As if user-space trolling were not enough..! ;-)
Brand spankn' new asyncronous "Deadline I/O scheduler, which will sort requests more agressivly/efficiently
phat new scheduler that constantly makes decisions no matter how many processes are running on the current machine. Gets rid of the problem of bouncing processes on smp machines that pleagues the current scheduler.
NAPI keeps kernel from being overridden with device interupts from high speed adapters. TCP offloading an asyncronous I/O help the network stack as well.
Neet VFS improvements
The inclusion of ALSA, along with support for many new devices (of course).
New Device Model (coherant registry of sorts).
many more, check it out. I have seen some very promising benchmarks.
You should also be aware the Linus gets to release a new kernel whenever he wants. He does this when he thinks its the right time, for reasons that don't always involve reliability. He posts a new kernel release when he feels its ready, often without testing it particularly rigorously, and it has happened quite a few times that Linus has released a new "stable" kernel that turns out to be quite broken. It is actually quite common for the stable releases of the non-86 architectures to be quite buggy.
Finally, Linus announced on linux-kernel that the reason he released the first 2.4 stable kernel (2.4.0) was because he wanted more widespread testing, not because he felt it was ready to use. I wouldn't be surprised if he does this with 2.6. Both 2.2 and 2.4 went through several releases before they were really stabilized, and 2.4 has never been as reliable as the later 2.2 versions.
That's why I ask you to read:
-
Why We Should Test the New Linux Kernel
-
Using Test Suites to Validate the Linux Kernel
The Open Source Development Lab's Japan development center used to have japanese translations of them but they don't seem to be online anymore. I'll track them down and post them here when I can find them.I am actively seeking further translations of these and the other articles that are at The Linux Quality Database. The articles are all under the GNU Free Documentation License so you can just grab them and translate away.
Thank you for your attention.
Request your free CD of my piano music.
http://people.redhat.com/arjanv/2.5
I have been using Arjan's 2.6 kernel RPMS from here. test1 was working fine, but test2 and test3 have this mysterious hard lockup problem after a few hours of uptime and moderate CPU load. Has anyone seen this problem? Already known reported bug?