Slashdot Mirror


Linux 2.6.0-test9 Released

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."

43 of 262 comments (clear)

  1. Whoa... by Sp4c3+C4d3t · · Score: 2, Funny

    So it's finally almost here. Is the framebuffer fixed yet?

    --
    Happy New Year, it's 1984!
  2. torrent link by Wakkow · · Score: 3, Informative

    Although mirrors will probably be faster, if anyone wants the torrent, I set one up:

    http://69.56.172.70/linux-2.6.0-test9.tar.bz2.torr ent

    1. Re:torrent link by Anonymous Coward · · Score: 4, Funny

      Wow, really helpful! :)
      I'll just take your word for it and you just saved me the effort of actually checking the hash.
      Your ideas on hash-check-optimizing might even revolutionize the whole industry.
      Plus imaginary authentication feels so much safer!

    2. Re:torrent link by Wakkow · · Score: 2, Informative

      I should have thought to include a link to the pgp sig.. It's true no one should blindly trust unofficial sources. Thanks DD.

  3. 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 Squeebee · · Score: 3, Informative

      RedHat 10 (aka Fedora Linux, has a 2.6 kernel on their roadmap. Essentially they say that if 2.6 is officially released before they officially release RH10, and the switch will not cause delays, then they will ship 10 with 2.6, otherwise they will ship an updated version ASAP after the release of 2.6.

    2. Re:Hot damn by gweihir · · Score: 2, Informative

      Can I put a 2.6 kernel in a 2.4 distro?

      Should not be a problem. I have a debian/testing installation with a self-compiled stock 2.6.0-test1 from www.kernel.org. It has been running crash free since end of July now.

      For a complete list of minimal requirements, look into the Documentation/Changes file in the kernel sources. At least 2.6.0-test1 has no extreme requirements, as far as I can tell.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    3. Re:Hot damn by Darmox · · Score: 3, Informative

      Just to clear up a little thing about Debian, yea, stable is some pretty old packages/versions, but it is very well tested, and rock solid.

      Debian unstable, however, is fairly close to bleeding edge... I mean, Mozilla 1.5 hit a day or two after it was released, Gnome 2.4 took oh, probably a few weeks... And really, the packages are quite stable, sometimes the upgrading/installing of them isn't, however. (but that's what happens when you're using bleeding edge stuff)

      And, if you don't want to deal with uninstallable packages occasionally(haven't seen that in months) or your compiler being upgraded at weird times, testing is right between the two.

      --
      If I was that drunk, I would have remembered it -- H. Simpson
    4. Re:Hot damn by Neon+Spiral+Injector · · Score: 3, Informative

      The most "extreme" change is the modutils to module-init-tools. But the module-init-tools provide wrapper support and call the old modutils when booting back to a 2.4 kernel.

    5. Re:Hot damn by yorgasor · · Score: 4, Informative

      Um, I think you misread that. The Fedora Core 1 that is coming out in a couple weeks has no plans whatsoever for supporting kernel 2.6. The following Fedora Core (what you would call RH11) will come with kernel 2.6 if it's ready. If it seem stable enough, they'll hurry up and get the new release out there, but if not, they won't delay the release just to get the new kernel in.

      No matter what, they won't be shipping a kernel unless they've been able to test it thoroughly. And it'll probably take several kernel releases before it's ready to be shipped with a distro.

      --
      Looking for a computer support specialist for your small business? Check out
    6. Re:Hot damn by minion · · Score: 2, Informative

      Um, I think you misread that. The Fedora Core 1 that is coming out in a couple weeks has no plans whatsoever for supporting kernel 2.6.

      Which is a good reason to try Slackware again. 9.1 was just released, with 2.4.22, and support for 2.6. Which means they already did the dirty work of making sure mod-init-tools was on the machine, along with other necessities. Not to mention it comes with Gnome 2.4 and KDE 3.1.4

      I've tried 2.6.0-test4 on Slackware 9, and it made a difference in desktop usability and responsiveness.

      --

      -- If we don't stand up for our rights, now, there will be no right to stand up for them later.
    7. 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.
    8. Re:Hot damn by lgftsa · · Score: 2, Informative

      The "latest RPM" is, by definition, not stable. It has not had the testing period that a "stable" package has.

      If you want a more recent version than is available in stable, pin your machine at stable and install the "testing" package(which satisfies dependancies), or run testing itself.

      You can also find a third-party debian source(eg http://marillat.free.fr), or compile it yourself, though that also defeats the testing period.

      Check out http://www.apt-get.org/ for all your unofficial debian source needs.

    9. Re:Hot damn by golgotha007 · · Score: 2, Informative

      Just to clear up a little thing about Debian, yea, stable is some pretty old packages/versions, but it is very well tested, and rock solid.

      i keep hearing this about Debian, and indeed it's true. however, i run redhat 9 on all my production servers using the latest packages from the apt-get repository from freshrpms. i have zero stability problems and my servers run rock solid as well.

      even though i run redhat systems, i still use vi for every configuration; that's one of the things i like about redhat is you can configure the machine with gui tools or you can do it the old fashioned way (i prefer the old way myself).

      besides my redhat experience, i am also the sysadmin for 5 debian (latest stable) boxes at another company. just about every package on there are full point releases behind that latest release (some are 2 year old packages, look at the old clunky vi for an example).

      the debian machines are rock solid and i don't have any problems with them at all. of course, the redhat machines are problem free as well.

      with my experience, my distro of choice for a production platform? redhat. it has all the great features of debian, plus.

      i geuss my point is that debian folks are always saying how stable debian is, but i find that other distros are just as rock solid.

  4. Re:Whaa by BJH · · Score: 4, Informative

    SATA = Serial ATA, a replacement for the old Parallel ATA.
    XFS = SGI's high-performance filesystem.
    CIFS = Common Internet File System, otherwise known as SMB. The Microsoft networked filesystem emulated by Samba. A misnomer in that it isn't generally used over the Internet (except for worms, ha ha).

  5. Taunting the LG users? by wrinkledshirt · · Score: 5, Funny

    I see one of the icons for this story is a compact disc. That's just plain mean.

    --

    --------
    Bleah! Heh heh heh... BLEAH BLEAH!!! Ha ha ha ha...

  6. Still a bit to do. by Neon+Spiral+Injector · · Score: 3, Informative

    It doesn't build for the x86-64 platform, and doesn't boot on "white box" Alphas (ones only intended to run NT). So my 64-bit machines are feeling a bit left out.

    At least patches for both problems are available, but need to be merged.

    1. Re:Still a bit to do. by phantomlord · · Score: 3, Informative

      wait for 2.6.1... Linus has repeatedly stated that all he cares about being buildable and stable for 2.6.0 is x86. He's been pretty irked by the people maintaining trees for other architectures which have gone ages without merging suddenly wanting to get the patches in at the last minute, especially if it means changing more than just the arch specific files.

      --
      Don't leave your mind so open that your brain falls out. Don't close it so much that you cut off the blood.
    2. Re:Still a bit to do. by Neon+Spiral+Injector · · Score: 2, Informative

      The Alpha patch is just to the arch specific setup.c file, adds one conditional, and three lines of varible twidling. That should probably go in.

      But yes, the x86-64 stuff is a pretty big patch.

  7. Still the same error, propagated from kernel 2.2 by Anonymous Coward · · Score: 5, Funny

    I submitted several bugs to the bug tracker, I e-mailed Alan Cox and Lunis Torvalds, and I still get the same error when trying to run it:

    kernel-2.6.0-test9.tar.bz2 is not a valid Win32 application

    and then the error message with Ok and Cancel.

    Anyone has any howto on whether this bug will ever be fixed? Or is there a service pack or a patch I missed?

  8. Hooray by Anonymous Coward · · Score: 2, Funny

    Can't wait to install this one on my new LG computer!

  9. try this ftp by Anonymous Coward · · Score: 4, Funny

    if you have problem downloading, try this one.

    ftp.sco.com/pub/linux/source/beta/kernel/hey_bil ly-/we_need_to_check_da_code/need_cash/buy_mo_shar e/2.6.0-test9.src.rpm

    Good luck everyone!!

  10. 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
  11. 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?

    1. Re:For a kernel compilation newbie... by Muvlo+Redond · · Score: 3, Informative

      As a fairly new GNU/Linux user myself, I've found compiling and running new kernels to be quite easy. I should mention, though, that my early efforts failed completely. This was when I was running Red Hat 9. I guess RH needs something special; at any rate I never got 2.6.0-testX to run on it. I am now using Gentoo, and everything seems to be working extremely well, and I'm currently running test8-mm1. I recommend you read this tutorial written for the 2.6 kernel: http://kerneltrap.org/node/view/799. Good luck. :) -M

    2. Re:For a kernel compilation newbie... by GigsVT · · Score: 2, Insightful

      You both probably know this, but unless you have a specific need to run 2.6, or you want to get involved in reporting bugs and such (or you just feel a compelling need to live on the edge), it's probably best to stay with 2.4 for now.

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    3. Re:For a kernel compilation newbie... by digitalhermit · · Score: 4, Informative

      Things to watch:
      Build your root fs models statically into the kernel.

      Your /etc/modules.conf file will likely need to be updated because of differences in the module names.

      Some init scripts will need to be modified.

      None of these are fatal errors but will cause some failure messages as the system comes up. This can be a little disconcerting but shouldn't do any harm.

      If you're running things like NVidia binary drives, VMWare, or any applications that build kernel modules specific to the running kernel you will need to rebuild those hooks.

      Some USB devices may magically start working!

      Your /dev layout may look different, possibly breaking some scripts.

      Some parts of /proc may not be the same, so things that rely on cat'ing files in /proc might break. For these use applications like lspci instead of reading proc directly.

  12. Running 2.6-test9 now by Azar · · Score: 2, Informative

    I downloaded and was compiling the sources when the story broke on Slashdot.

    When Pat said that Slackware 9.1 was 2.6 ready, he wasn't kidding. So far, so good. Not a glitch during the compile or boot-up. I plan to stress test it as much as possible to see if I can tell the difference between 2.4.22.

    I can't wait until Linux 2.6 final is out.

  13. Re:So what's the difference? by gid · · Score: 5, Informative

    Alsa sound drivers are built right in. So now I don't need to copile them separately. The oss support for my sound card was very half ass, it didn't even support full duplex and hardware mixing.

    Also, i2c and the lm sensors interface is built right in as well. So now I don't have to compile i2c and lm sensors to know how hot my mobo and cpu are running. They have saved my computer at least once. My cpu fan died on me, I wouldn't have known if I didn't have it graphed.

    Also there's pre-emptible kernel option. It makes X more responsive, especially noticeable under heavy load and on slower computers. Supposedly better memory management as well, but as I have 768 megs of ram, I probably won't ever notice that.

    There's also USB 2.0 support, and support for USB type removeable drivers. I think both of those are new.

    There's probalby more, but those are the ones I know off hand.

  14. Re:They still don't support my platform :-( by Waffle+Iron · · Score: 2, Funny
    Why does Linux dev-community reluctantly ignore Commodore 64s???

    Because they are bloated, overly complicated, overpriced kludge boxes. People in the know stick with the clean, elegant VIC-20.

  15. Re:Not ready for prime time by aardvarkjoe · · Score: 2, Insightful

    Don't forget that the vast majority of increased code size is in new drivers. You won't be running a kernel that incorporates more than a fraction of that code. In fact, IIRC, the size of the base code actually decreased between 2.2 and 2.4.

    --

    How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
  16. ACPI and USB by PeterClark · · Score: 2, Informative

    Does anyone know if the conflicts between ACPI and USB have been fixed yet? Basically, if ACPI is enabled in the kernel, it will mess with USB--for instance, my USB mouse will suddenly stop working (no errors in /var/log/messages or syslog) and won't work again until I 'rmmod ohci_hcd' and modprobe it back again. My laptop (which is currently running -test8) has this problem, and it is very annoying (although at least APM works).

  17. 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

  18. 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

  19. Re:So what's the difference? by rgmoore · · Score: 3, Informative

    One big improvement in 2.6 will be with handling of CD and CD-RW drives. CD audio extraction will be able to use DMA, which should speed it up a lot. Also, CD writing will be possible using the regular IDE driver, so it won't be necessary to use SCSI emulation anymore.

    For a really comprehensive description of the changes with 2.6, you might want to look at The Wonderful World of Linux 2.6, which goes into much more detail than anyone on /. is likely to be able to.

    --

    There's no point in questioning authority if you aren't going to listen to the answers.

  20. 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.

  21. Re:Still the same error, propagated from kernel 2. by Captain+Large+Face · · Score: 2, Funny

    Here's the last MS service pack you'll ever need:

    format c:

  22. Re:acpi? by Kourino · · Score: 2, Informative

    The mailing list post that is linked to in the headline, if you'd read it, mentions that Linus doesn't want to do anything major before release. I'd consider "bug changes" critical, personally. Linus is only taking bug fixes for major issues. Witness:

    "So guys, let's work on this even more for test10. I'm going to _totally_ ignore patches that aren't for major bugs. Don't send me anything that _others_ wouldn't consider horribly critical."

  23. RedHat 2.6 Kernels by Oronwe · · Score: 2, Informative

    Take a look at http://people.redhat.com/~arjanv/2.5/ they have unofficial, precompiled 2.6 kernels there, last one is test8. Kernel is working just fine on my T23, minor bootup issues with USB, otherwise no problems. Only other thing is, you have to update your modutils and initscripts.

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

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

  25. Performance by pasi · · Score: 3, Informative

    Ok, before you read any further remember that this is NOT accurate, tested or anyhow valid information. Some of this is purely psychological and has got NOTHING to do with real benchmarks.

    I've been running 2.4 series with CK [1] patches. I'm unfortunately using somewhat low-end hardware (P200MHz) and hence I really appreciate performance. I switched to linux-2.6.0-test8 only a week ago, so again this isn't really the best source of information.

    Anyhow, I'm so far REALLY happy with performance of 2.6.0-test8. Before the switch, I was using 2.4.22-ck1 which was a lot worse performance-wise than my previous kernel, .20-ck6. Didn't switch back just yet because I had compiled in some stuff I needed and it takes a while to compile a new kernel with this hardware.

    Linux-2.6.0-test8 has done A LOT better than .22-ck1, and it has seemed even more responsive in normal use (IRC, web surfing, MP3s etc) than .20-ck6 which I was already happy with. Responsiveness shows in switching desktops when browser is doing things, starting things and playing MP3s at the same time.

    And yes, as I said in the beginning, most of this is purely psychological and inaccurate. Slower hardware of course benefits more even from smallest performance gains. Then again, I don't believe that 2.6 will be The Thing for serious production enviroments for a while, it's not mature enough yet. But for me -- for desktop use -- great!

    [1] http://members.optusnet.com.au/ckolivas/kernel/ (Con Kolivas' kernel patches that aim to a more responsive system)

  26. Re:torrent link - VALID NON-GOAT LINK by alsutton · · Score: 2, Informative

    Theres a valid torrent link at http://www.distributedbandwidth.info/torrentmap/ex plorer.jsp?cat=Lin260.

    It's got the patch & the full kernel.

  27. About your problems opening windows in X by sterwill · · Score: 2, Informative

    You're using sawfish, right? I am, and I tracked down the problem to a line in librep. I mailed John Harper just now about it. If you're not using sawfish, you can ignore the rest of this message.

    It all has to do with the following lines from unix_processes.c:

    timeout.tv_sec = 1;
    timeout.tv_usec = 0;
    rep_sig_restart (SIGCHLD, rep_FALSE);
    select (FD_SETSIZE, NULL, NULL, NULL, &timeout);
    rep_sig_restart (SIGCHLD, rep_TRUE);

    The call to select() on kernel 2.6 causes the timeout to be fully expired every time. This code is in the parent branch after the fork() (right before it starts waitpid() on the child), so everything freezes for at least 1 full second. Dropping this timeout to 1 usec causes the problem to go away.