It's good to be cautious, but as a cautious person I still use the 2.6test9-11 for the last couple of months and it's stable and much faster than 2.4.22+preemption I had just before it. I keep a 2.4 kernel image around of course.
What I'd recommend people to do:
1. Make sure your tools are updated to 2.6 (e.g. use debian "unstable", not debian "stable"). 2. Keep an extra boot media and a 2.4 kernel within a reach (I rely on the August Penguin mini-disc for this, been carrying it in my wallet since I got it :-).
Since I tested the kernel, at least one or two bug reports of mine were fixed in the final release (the "Missing initialization of /proc/net/tcp seq_file" is a bug I reported and tested the fix)
So being cautious is a good advice, but not to the point of not giving it a try at all.
One drawback I am worried about is the mentioning of a few dozens(?) of security-related bugs which have to be forward-ported. Can anyone comment about these?
--Amos
guy keren wrote:
On Thu, 18 Dec 2003, Nadav Har'El wrote:
On Thu, Dec 18, 2003, Muli Ben-Yehuda wrote about "Fwd: Linux 2.6.0":
Haven't seen this mentioned here yet, so, without further ado...
Does anybody know of a good summary of the differences between the latest Linux 2.4 versions, and 2.6?
hold your horses... "remember the dragons, mike" (and kernel 2.4.0). according to the bug-fix list, the kernel is not realy stable yet. fixing races that can cause oops of various sorts? give it a few versions before you really try to use it.
it took 2.4 more then half a year, from the 'stable' kernel, until a kernel that was actually stable (perhaps it was closer to a year? my memory is getting too short for this). based on past experience, it'll take a few more month before 2.6 will get to a stage where you'll dare put it on a production system that needs to work under some kind of stress..
this is not a prediction - just a catious look at the past.
================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
