Slashdot Mirror

← Back to Stories (view on slashdot.org)

Linux 2.6.0-test9 Released

Posted by timothy on from the asymptotia dept.

keesh writes "Linux kernel 2.6.0-test9 is now out. Changes include SATA support and XFS and CIFS fixes. Because of the change freeze, this is a fairly minor update. In the announcement, Linus suggests that -test10 will be the final release before 2.6.0-final. Don't forget to use a mirror."

11 of 262 comments (clear)

  1. Hot damn by Limburgher · · Score: 3, Interesting

    I can't wait. I just hope RedHat 10 includes a 2.6 kernel, so I don't have to bother compiling it myself. I'd love to take advantage of the performance improvements, and I'd also like to use SATA drives in my new server.

    --

    You are not the customer.

    1. Re:Hot damn by mslinux · · Score: 1, Interesting

      I can't wait. I just hope RedHat 10 includes a 2.6 kernel..."

      There isn't going to be a RedHat 10. RH decided to fuck all of their loyal follwers and concentrate on their "corporate" customers. Go to redhat.com and read about Fedora. I miss Alan Cox, will he go back to work for the RH bastards after he finishes his Masters?

    2. Re:Hot damn by morgajel · · Score: 2, Interesting
      I moved from redhat to slackware to debian, and have just recently made the move to gentoo. As a former debian user, I don't want to come off as one of the gentoo jackasses, but I gotta say it is a pretty decent system. everything seems to be stable, no package conflicts (as of yet), and emerge and been pretty kick ass.

      On the downside, install takes forever, and emerging packages yourself can take forever(depending on the machine). I had a 2100+xp with 512 of ram and the install took a week before I got a comfortable system.

      Something that I've found helps soften the blow is Distcc- I've been converting my debian boxes to gentoo, and as I go, I add them to the distcc collective... now when my pentium 2 400 compiles, it takes less time than my 2100+ did (because it parallel compiling on the 2100+, an athlon 1200 and a duron 1200, a P3 900, and a P3 600).

      As you can imagine, that cuts down compilation time :)
      anyways, if you have the patience, give gentoo a try, but make sure you save it till you get a few days in a row where you're not busy.
      Few words of wisdon:
      • don't go crazy with optimization flags. name your processor line and that's it.
      • get familiar with emerge.
      • checkout the package ufed. it's a nice little listing of cool flags you can use.
      • install vim|emacs, openssh, and fluxbox right off the bat. it will help make the install a little less painless.
      • follow the install directions CLOSELY. you'll save a lot of pain.
      • emerge can install a program several different ways- by name (apache), by version (apache-1.28.3), by tar file (apache-2.0.37.tbz), or my meta package(kde installs many smaller packages)
      • get familiar with the system and world meta packages. they're your friends, so understand what they are.
      • even if it takes a lot of time, don't get frustrated. you probably won't get gentoo installed correctly on your first try anyways. It's just the way things are... it's a learning process.
      --
      Looking for Book Reviews? Check out Literary Escapism.
  2. Not ready for prime time by Anonymous Coward · · Score: 0, Interesting

    Despite what the zealots on LKML may have you believe, 2.6.0 is terribly unstable still. Yes they have made great strides but any time you triple (!) the size of the codebase and change most of the internal APIs you are going to break a lot of functionality. From the looks of it it may be another year or two before 2.6 is ready for use on production systems, so don't hold your breath.

    1. Re:Not ready for prime time by duffbeer703 · · Score: 2, Interesting

      Got a point there...

      linux-2.0.39.tar.bz2 - 5958KB
      linux-2.2.25.tar.bz2 - 15421KB
      linux-2.6.0-test0.tar.bz2 - 32448BK

      --
      Conformity is the jailer of freedom and enemy of growth. -JFK
    2. Re:Not ready for prime time by Prof.Phreak · · Score: 5, Interesting
      Hmm... try this:

      lex@particle theory $ uname -a
      Linux particle 2.6.0-test6 #3 Sun Sep 28 19:27:41 EDT 2003 i686 AMD Athlon(tm) Processor AuthenticAMD GNU/Linux

      alex@particle theory $ uptime
      01:03:46 up 27 days, 3:45, 4 users, load average: 0.16, 0.36, 0.30

      And this is my *primary* dev box that doubles as a server (web, mysql, etc.,) and pretty much anything else I use a computer for (play music, video, etc.,)

      How exactly is 27 days uptime not stable?

      --

      "If anything can go wrong, it will." - Murphy

  3. For a kernel compilation newbie... by mnemonic_ · · Score: 2, Interesting

    For someone like me who has never compiled a kernel before, what sort of troubles should I expect in a move to a new kernel version?

  4. I hope... by AltGrendel · · Score: 2, Interesting
    ...that 2.6 will be released before RedHat finally drops support for all the pre-9 releases

    Yes, I realize that I can roll my own kernel, I've done it many times. It's just that they work better when RH makes the RPM. Not that this is as it should be.

    --
    The simple truth is that interstellar distances will not fit into the human imagination

    - Douglas Adams

  5. Andrew Morton at Southern California Linux Expo by MrMorph · · Score: 3, Interesting

    Andrew Morton the heralded maintainer of Linux kernel 2.6 will be speaking at the Southern California Linux Expo on November 22nd at the Los Angeles Convention Center in Los Angeles, California. Andrew will be speaking on the Linux pagecache, VFS, filesystem and VM nexus. Regular priced and student priced tickets giving full access to the event are still available for this event. Free expo only tickets are also available using the "FREE" promotional code on the orders page. The Southern California Linux Expo is a non-profit event organized by LUG volunteers.

  6. SCO code by tuggy · · Score: 2, Interesting

    anyone knows if the supposed stollen code from $CO has been removed? :>

  7. 2.5.57 through 2.6.0-test8-mm1 still unusable by Anonymous Coward · · Score: 1, Interesting
    I'm still having HORRIBLE performance issues with 2.6.0-test8 and most-recently 2.6.0-test8-mm1. Most of it seems to be centered around timing and multimedia (audio and video) playback. The performance is HORRID (No, I'm not trolling). In 2.4.21, I can turn the mixer down with a keyboard shortcut (aumix -v -2) and it goes down immediately, in response to my keyboard shortcut. In anything after 2.5.57, up to current 2.6-testX releases, it takes about 40 seconds to fully bring the mixer down 12 clicks. Meanwhile I can't open any other windows, click on any other apps, or anything. It's completely blocking.

    I've tried using all three schedulers (as, cfq, deadline), all with the same results. 'deadline' is clearly the winner here though. It seems to give the most level performance.

    Also, the issues with opening windows in X have not been solved, which I've reported 1/2 dozen times.

    Why does it take 2.6.0-test8 (and every version of the kernel after 2.5.57, when this problem first appeared) over 3-4 seconds to open an xterm from a keyboard shortcut? In 2.4.21, again, it is instantaneous. In many cases, a keyboard request to open one xterm will either open none, 1, or several. The timing is COMPLETELY screwed up for this, and I can't figure out why.

    For me, 2.6.0-testX and anything after 2.5.57 is not even remotely usable for any server or desktop use. The performance is just not there. It's laggy, slow, and the timing is way off in some regard. I'm surprised nobody has caught this yet. How many times do I have to report it, before someone actually tries to test it? Who am I supposed to send my next volley of emails to?

    Oh, and lastly... orinoco_pci immediately hard-locks my Thinkpad T23 the moment I try to modprobe it.. forcing me to do a hold-power-down-for-7-seconds power-off. Not fun.

    Though I appreciate the work of the kernel authors and maintainers, I will definately not be moving any servers or desktops I deploy and administer (which is quite a few hundred at this point, and growing every day) to 2.6.x until these issues are found, fixed, and resolved. 2.4.21 is where they'll stay, until 2.6 outperforms it.