Linux 2.6 Turns 1 Year Old
Paul Kucher writes "On December 17th, 2003, Linux 2.6 was released by Linus Torvalds, saying 'The beaver is out of detox.' This was a reference to the last pre-release of the 2.6 kernel, which was called Beaver in Detox. Although a stable release, the 2.6 kernel has added many new features in the past year due to the new development model. It will be interesting to see what else is in store for this kernel, and I imagine it will be years before it is in maintenance mode."
Happy Birthday
Sorry, teleporters just kill you and then make a copy. A perfect, soul-less copy.
RoTK also was released in theaters on the same day. It was a great day all round.
Check out Mon and Mon.cgi
My USB doesn't work in 2.6, which is a shame as not only would I like to update my desktop system but it also means that I can't use any live CDs (like the Ubuntu ones I sent for) since my keyboard and mouse are USB, and so is my printer. :-(
Linux mu 2.6.0-gentoo-r1 #2 SMP Sat Jul 17 14:53:56 CDT 2004 i686 Intel(R) Pentium(R) M processor 1200MHz GenuineIntel GNU/Linux
12:16:12 up 365 days, 6 users, load average: 2.07, 2.17, 2.03
/me buys a lovely gift for the kernel that finally let him burn on IDE burners. That ide-scsi trick on 2.4 and earlier confounded (and continues to confound) me...
Great, wonderful, blah, blah, blah...
Now let's get a kernel fix for recent 2.6.9 series kernels that allows you to boot off of SATA drives hanging off of a NFORCE2 or NFORCE3 chipset's SATA ports. Nothing more annoying than having to take out your 10K RPM Raptor for a 7.2K RPM IDE plow horse...
..birthdays are always positive!
I have el cheapo Promise Fasttrak 133 (PDC20276) with two other el cheapo 30GB harddrives in a raid. It works fine with 2.4, but I still see no way of upgrading to 2.6. Will there eventually be an ATARAID workaround, or do I need to change my system setup to get on 2.6
I really hate Dan Patrick.
Now I hope that the linux kernel people learned their lesson and that the project's next stable release is really stable, which wasn't by far the 2.6 case.
Don't get me wrong. I love linux and I'm very gratefull for the work that group of people invests into the project. Still, 2.6 wasn't by far near the stable status it got and that misslabelling can be very counterproductive. After all, the common idea is that linux is difficult, not ready for serious work and incredibly buggy and a buggy release just helps to perpetuate those ideas.
Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
That's bullshit since the output shows that your kernel was compiled in July 2004, not in December last year.