Slashdot Mirror


Linux Kernel 2.4.21 Released

An anonymous reader writes "After > 6 months of waiting, 2.4.21 is here. Lots of cleanups, and a patch which gives a MAJOR boost to the 'feel' of the system under heavy disk IO, especially on IDE systems. As usual, available from your local kernel.org mirror or ftp.COUNTRYCODE.kernel.org/pub/linux/kernel/v2.4/! Tidbit: 'Current bandwidth utilization 131.72 Mbit/s '." See the Changelog for new stuff.

105 of 539 comments (clear)

  1. Looks good.. by NightWulf · · Score: 4, Funny

    Now to attempt to get it before it's slashdotted.

    1. Re:Looks good.. by Metasquares · · Score: 3, Insightful

      Perhaps if SCO would actually reveal the code to the public, a version could be made that is clean of "SCO's" code. Of course, they might just get laughed at if they reveal the code.

  2. Started to think 2.4.x was dead by phathead296 · · Score: 5, Interesting

    I was seriously starting to think the 2.4 series was dead in preparation for 2.6.0. The ChangeLog is impressive though.

    Phathead

    1. Re:Started to think 2.4.x was dead by mahdi13 · · Score: 5, Interesting

      Far from dead...hell, the 2.2 kernel is still being maintained and patched (mostly by Alan Cox, but still...it's active)

      --
      "Some things have to be believed to be seen." - Ralph Hodgson
    2. Re:Started to think 2.4.x was dead by gunpowder · · Score: 5, Informative

      I can't believe some still don't get this:

      As long as it's not available from ftp://ftp.kernel.org or http://www.kernel.org, there is no newer version of the linux kernel.

      The same applies to the ftp://gcc.gnu.org and GCC (not the website, they are always a little bit lame updating it).

      So if you say

      'Mandrake has already put the "2.4.21" kernel in their 9.1 release'

      your are wrong! They didn't. They lied to you. Or you are mistaken. Or they used a prerelease and renamed it 2.4.21.

      And no, 2.4.21 it's not 'too late'. Look at the Changelog and what huge amount of bugfixing has been done. And all those updates to the drivers!

      True, 2.6 will feature a log of nice extra stuff, but I guess 99.9% of all linux users are happy with just the features 2.4 has. They simply don't need support for NUMA, 64bit dev_t or Zero-copy NFS.

    3. Re:Started to think 2.4.x was dead by presroi · · Score: 4, Informative
      Far from dead...hell, the 2.2 kernel is still being maintained and patched (mostly by Alan Cox, but still...it's active)


      Even 2.0.X is still maintained. It currently stands at 2.0.40-rc6 (almost one year old).
    4. Re:Started to think 2.4.x was dead by gunpowder · · Score: 3, Funny

      Chill dude
      Thanks. I needed that!
      It's Friday, 13th, you know ...

    5. Re:Started to think 2.4.x was dead by mateub · · Score: 2, Funny

      >> The ChangeLog is impressive though. Sure, just removing all those SCO copyrights took days! :-) Matt

      --
      "And we're happy here, but we live in fear, we've seen a lot of temples crumble..." - Concrete Blonde
  3. BitTorrent by Dreadlord · · Score: 5, Interesting

    I wonder if they are planning on an official BitTorrent.

    --
    The IT section color scheme sucks.
    1. Re:BitTorrent by aliens · · Score: 4, Informative

      Bit torrent works best on large files. The source is only like 20megs. They could do it, but people should be only downloading the patch anyway.

      --
      -- taking over the world, we are.
    2. Re:BitTorrent by Tumbleweed · · Score: 4, Insightful

      > people should be only downloading the patch anyway

      Yeah, right, and people should be writing in Esperanto on their Dvorak layout keyboards, too, but that's about the same likelihood.

      If they _really_ want people to actually use the patches, they should release the patches first, wait about a week, THEN release the full kernels. Evil, I know. :)

    3. Re:BitTorrent by Xerithane · · Score: 4, Funny

      Yeah, right, and people should be writing in Esperanto on their Dvorak layout keyboards, too, but that's about the same likelihood.

      Est tajp jam nun, kun Dvorak... sed mi.

      --
      Dacels Jewelers can't be trusted.
    4. Re:BitTorrent by Wakkow · · Score: 4, Informative

      I've never done this before, but I thought I'd give it a shot:

      http://66.227.104.34/linux-2.4.21.tar.bz2.torren t

    5. Re:BitTorrent by greck · · Score: 2, Informative

      It's been six months! The only people who don't have 2.4.20 sources are people who don't compile kernels...

      ...or have uptimes >= 6 months.

    6. Re:BitTorrent by liverbugg · · Score: 2, Interesting

      Maxing out my cable at 250k/s...torrent finished downloading before the kernel.org web page loaded.

  4. Just to get these out of the way... by Drakonian · · Score: 5, Funny

    Oh man! My 286 just finished compiling 2.4.20!

    or

    Oh man! I was downloading at 4000 K/sec before this story showed up. Thanks a lot Slashdot!

    --
    Random is the New Order.
    1. Re:Just to get these out of the way... by shepd · · Score: 3, Informative

      Actually, it does.

      Sorry to burst your bubble... :)

      --
      If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
  5. Be gentle to the mirrors by Spock+the+Vulcan · · Score: 5, Informative

    Instead of downloading the entire kernel, download just the patch file if you are running the previous version. Then patch your source tree using:

    cd /usr/src/linux
    bzcat /blah/patch-2.4.21.bz2|patch -p1
    make oldconfig

    1. Re:Be gentle to the mirrors by Spock+the+Vulcan · · Score: 4, Funny

      When I can download the Windows kernel source code and compile it in less than 5 commands, give me a call.

    2. Re:Be gentle to the mirrors by narfbot · · Score: 3, Insightful

      cd /usr/src/linux
      bzcat /blah/patch-2.4.21.bz2|patch -p1
      make oldconfig
      blah blah blah

      And you people still wonder why so many people stick to Windows instead of trying Linux? When I can double-click an icon and click OK and have it install the updates give me a call.


      What do you expect? Vanilla kernel compiles/updates aren't for the average joe. They can wait for their easy distro update.

    3. Re:Be gentle to the mirrors by hendridm · · Score: 2, Insightful

      > When I can double-click an icon and click OK and have it install the updates give me a call.

      Should we let you know when it gets oppressive EULAs and DRM controlled by a single company too? I wouldn't hold your breath.

    4. Re:Be gentle to the mirrors by koreth · · Score: 2, Funny

      I bet you can get the Windows source code with one command:
      mail -s "My resume" jobs@microsoft.com

    5. Re:Be gentle to the mirrors by volkerdi · · Score: 3, Informative

      Instead of downloading the entire kernel, download just the patch file if you are running the previous version.

      But, is anyone actually running vanilla 2.4.20, or keeping it in /usr/src/linux? Odds are that most people are running vendor kernels (even in Slackware the usually virgin kernel has been slightly violated this time ;), or at least applied the ptrace hole fix. As that fix is implemented differently in 2.4.21 it would be enough to keep the patch from applying cleanly.

      Of course, you might still have the official linux-2.4.20.tar.bz2 tarball sitting around somewhere, and if you do you can use that and the patch-2.4.21.

    6. Re:Be gentle to the mirrors by Shagg · · Score: 4, Funny

      And you people still wonder why so many people stick to Windows instead of trying Linux? When I can double-click an icon and click OK and have it install the updates give me a call.

      Wow, what icon can I click on in Windows to compile a new version of the OS from source code?

      --
      Unix is user friendly, it's just selective about who its friends are.
    7. Re:Be gentle to the mirrors by kasperd · · Score: 2, Informative

      When I can double-click an icon and click OK and have it install the updates give me a call.

      Sorry I cannot help you there. RedHat has something very similar, but you only have to click once on the icon not doubleclick.

      --

      Do you care about the security of your wireless mouse?
  6. Admin Question by peripatetic_bum · · Score: 3, Funny

    Im in charge of keeping production servers up to date. Im using a 2.4.20-rc7.
    should I go up tp 2.4.21

    How often should I build the new kernels for production servers (should I even be using 2.4? ie, stick with 2.2)

    Thanks for the Help!

    --

    Sigs are dangerous coy things

    1. Re:Admin Question by Malc · · Score: 5, Insightful

      Why are you running a release candidate on a production server?

      If the server(s) is/are performing correctly, why bother upgrading? What will it buy you? Just apply security patches and don't tinker with anything else.

    2. Re:Admin Question by xanadu-xtroot.com · · Score: 3, Informative

      Im using a 2.4.20-rc7.

      Well, the 2.4.21 kernel was (in reality) the RC-8. Look at the changelog and see if any of that applies to you. If so then yes, it's would be wise to upgrade. If not, then it's your call. This is why the changlog exists...

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    3. Re:Admin Question by Malc · · Score: 2, Funny

      Doesn't the "rc" in "2.4.20-rc7" indicate it's a release candidate? If not, then I take back that part of my comment.

    4. Re:Admin Question by stefanlasiewski · · Score: 4, Informative

      Im in charge of keeping production servers up to date. Im using a 2.4.20-rc7.
      should I go up tp 2.4.21


      If stability is important to you, you should only use proven, stable kernels on a production server.

      Unless there is some new feature that you absolutely need RIGHT NOW and cannot wait, it is very bad to use 2.4.20-rc7 on a production server. The "rc" stands for "release candidate", which means that the kernel is almost ready to be used by the public, but needs people to test it first.

      If you care about system stability, you should not be testing the kernel on a production machine. If you do want to test the kernel, do so on a test machine that is not a mission critical machine.

      On several occasions in the past, a release-candidate kernel introduced new code which would crash or corrupt systems that used the kernel.

      However, if 2.4.20-rc7 is not crashing on you, you don't need to upgrade to 2.4.21 right away. Review the kernel changelog, and see if any of the changes apply to you. Wait a few days (or weeks), and upgrade to 2.4.21 when it's convenient to you.

      Personally, unless there is some urgent fix that I need in the new kernel, I always wait a few weeks or months before upgrading the kernel, just in case some wierd bug was introduced into the new kernel version. During those weeks or months, I usually test the new kernel on a test machine and see if anything wierd happens.

      --
      "Can of worms? The can is open... the worms are everywhere."
    5. Re:Admin Question by ChadN · · Score: 2, Informative

      Obviously "oohp" didn't read the post you responded to. That said, it is not inappropriate to use a release candidate on production servers, especially when the rate of rc releases was a slow as it was. If the RC fixes a specific problem you are having, or offers a specific improvement you could really use, it is worth investigating. There are also issues of security to be concerned about; the iperm and networking bugs that exist in 2.4.20.

      The main point is that one should do a small test deployment, and some heavy testing, before a wider deployment. There a probably few, if any, user mode level compatibility problems between 2.4.20 and 2.4.21, so reverting back to 2.4.20 should be fairly easy if there are problems. It all depends on the situation.

      --
      "It's overkill, of course. But you can never have too much overkill." - Anonymous Slashdot Coward
    6. Re:Admin Question by Some+Dumbass... · · Score: 2, Informative

      Why are you running a release candidate on a production server?

      Uh, because there were several vulnerabilities found in the 2.4.20 kernels which were only fixed in the -rc's? See this summary.

      Just apply security patches and don't tinker with anything else.

      Sometimes the kernel needs security patches too.

    7. Re:Admin Question by kelleher · · Score: 4, Funny
      Quiet! Leave the guy alone!

      I get paid good money to come in and clean shops up after sloppy Admins have created unstable messes... :)

  7. I take it... by Albanach · · Score: 3, Funny

    SCO won't be offering this new kernel for existing Caldera Linux users then?

  8. why not posting the http links instead of the ftp? by Anonymous Coward · · Score: 2, Informative

    http://www.de.kernel.org/pub/linux/kernel/v2.4/Cha ngeLog-2.4.21

    for example.

    ftp needs much more time and authentication stuff for login, commandos and so forth.

    fr

    jp

    and so on...

  9. Enjoy, losers! by Anonymous Coward · · Score: 5, Funny

    Ha, I'm glad I have a life, unlike you losers! Knock yourselves out compiling the newest kernel; I'll be out having a blast with my girlfriend in my Porsche.

    (Okay, okay; I'm sitting at home in my underpants reloading slashdot to see if new stories are posted. I'll go download it now.)

  10. Re:unstable 2.5 by Jayr · · Score: 2, Informative

    Actually, that was released May 27th.

  11. excellent, we can switch to this by mikeee · · Score: 5, Funny

    when our AIX licenses expire today.

  12. heres how to compile the kernel by net_bh · · Score: 3, Informative

    $ cd /path/to/kernel
    $ make menuconfig # Replace menuconfig with xconfig if you want
    -Select the options you need in your kernel and save it
    $ make dep bzImage
    -Look in arch//boot/ for the bzImage file
    -Install it for your favourite bootloader (grub/lilo) and reboot machine
    -gloat :)

    --
    There is no patch for stupidity

    Visit my blog

    1. Re:heres how to compile the kernel by Cable_Monkey · · Score: 2, Informative

      Whatever happened to "make modules" and "make modules_install"? ;)

    2. Re:heres how to compile the kernel by mahdi13 · · Score: 3, Funny

      You forgot some...

      make modules
      make modules_install

      Unless you are a masochistic...er, monolithic kernel builder =)

      --
      "Some things have to be believed to be seen." - Ralph Hodgson
    3. Re:heres how to compile the kernel by xanadu-xtroot.com · · Score: 2, Informative

      # cd /usr/src/linux
      # make menuconfig
      # make dep clean modules bzImage
      (assuming all's good)
      make modules_install install


      The scripts have been able to install the kernel itself by itself for quite a while and also detect lilo or grub or whatever. I have no idea why people keep telling the n00bs to cp ./arch/what/ever/

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    4. Re:heres how to compile the kernel by Minna+Kirai · · Score: 2, Interesting

      In the past, putting all the targets on one make invocation could fail mysteriously. I never tracked the problem to it's source (the workaround is easy enough), although presumably it involved the makefiles created in the "dep" stage not being read in time for the other targets to see them. (This might be dependent on the version of "make" you have)

  13. Disc IO Related Lockups? by Jerk+City+Troll · · Score: 2, Interesting

    I have two systems that receive heavy use. Both of them are often used for ripping and the dual processor system is used for encoding. Whenever either of these systems is under heavy load, and I rip a DVD or image a CD, weird things happen. I get IO timeouts and sometimes even lock ups. Under normal load, there is absolutely no trouble at all, except with the dual processor system. That machine does filesystem crypto and thus, it's processors are quite stressed by cryptoloop processes whenver the disks are active. Dumping a disc to a filesystem on that box sometimes produces annoying problems. I've had solid lock ups, inability to unmount and eject discs because processes won't release them, and sometimes even X just stops responding.

    Both systems are running 2.4.20. Now, question: are problems like these resolved in 2.4.21 with these IO fixes? Remember, the drives doing the reading are probably fine. The one machine has two, a DVD-ROM and a CD-RW, and the other has a DVD+-RW. All three drives cannot possibly be faulty, nor can both IDE controllers. The problem has got to be with software. I cannot think back to when this began, but it may have been for the life of 2.4.20.

    So is there been something screwy with the IDE-CD subsystem in Linux lately?

    1. Re:Disc IO Related Lockups? by Cnik70 · · Score: 2, Informative

      Did you mount your drives with defualt in the /etc/fstab file? If so, use noatime, notail instead. it will prevent those lockups.

      --
      -Cnik
    2. Re:Disc IO Related Lockups? by arjun · · Score: 2, Insightful

      Instead of whining here, why don't you test the rcX candidates and report your findings on lkml, like the rest of us. You have better chances of getting things fixed.

    3. Re:Disc IO Related Lockups? by bogie · · Score: 2, Insightful

      "Ssssh, dont tell anybody, it might burst there bubble, and distract them from sliming other OSes that solved this junk years ago"

      Then why does windows lock up tight whenever you need to delete a large file? Windows falls to pieces whenever your doing anything with high IO. Feel free to lower the priority of the high IO process because that's the only way you'll even be able to open Notepad once a high IO task starts in Windows 2k/XP. You really think explorer isn't a crippled piece of shit? Windows doesn't do anything that could be called multitaking once you have a process hogger. At least with linux there are patches which can make it useable under the most severe loads.

      Nice try though.

      --
      If you wanna get rich, you know that payback is a bitch
    4. Re:Disc IO Related Lockups? by Cnik70 · · Score: 2, Informative

      I don't see it exactly as a problem, more like a result of a setting that allows the system to constantly update the drive info with file access time and tail info (which can require loads of extra io's when loading a file). when you set the system to not update access time and tail info on a drive, it removes this extra io taskload.

      --
      -Cnik
    5. Re:Disc IO Related Lockups? by lmfr · · Score: 2, Informative
      I had a similar problem. Under heavy I/O, my system locked up for some seconds and complained about lost interrupts.

      The new kernel (well, 2.4.21-rc8) fixed that.

      One workaround mentioned in the LKML is to disable IO-APIC.

  14. Re:Quick Question by Neon+Spiral+Injector · · Score: 4, Informative

    $ cp linux-2.4.20/.config linux-2.4.21/
    $ cd linux-2.4.21
    $ make oldconfig

  15. Ah by HughJampton · · Score: 3, Funny

    But does it run linux?

    --
    In Soviet Russia, beowulf clusters imagine YOU!
  16. RedHat kernels by DreadSpoon · · Score: 4, Insightful

    Hoping RH pushes updated kernels for RH9. Piss-poor IDE disk performance is my one big gripe with my Linux boxen at the moment; whole machine feels like shit when something heavy is running the disk in the background. :(

    1. Re: RedHat kernels by Black+Parrot · · Score: 4, Interesting


      > Hoping RH pushes updated kernels for RH9. Piss-poor IDE disk performance is my one big gripe with my Linux boxen at the moment; whole machine feels like shit when something heavy is running the disk in the background. :(

      \AOL{meetoo}. Actually, even if I just had lots of windows open and not much CPU or disk traffic my UI felt like Windows 95, repeatedly coming to a screeching halt for several seconds at a time, usually when switching from one window or desktop to another.

      I finally failed back to an older kernel I still had around, and the problem went away. I don't know whether the problem was with the 2.4.20 series kernels (I tried three) or the rumored Red Hack kernel hack that they purportedly distribute for RH9 (all three I tried were from RH RPMs). I'm just glad I was able to make it go away.

      --
      Sheesh, evil *and* a jerk. -- Jade
    2. Re:RedHat kernels by mahdi13 · · Score: 4, Informative

      Red Hat 9 back-ported a disk scheduler which is a dog. either download this 2.4.21 vanilla kernel and compile it or recompile the default RH9 kerenl and remove the scheduler (I believe it is under General, been a while since I looked at this...the option right after the CPU info)

      --
      "Some things have to be believed to be seen." - Ralph Hodgson
    3. Re: RedHat kernels by IamTheRealMike · · Score: 2
      Ditto.

      In fact, I switched to a stock Linus 2.4.20 kernel just last night. So far, no problems. Before, my desktop felt like treacle.

      I think I might upgrade to 2.4.21, maybe even apply to pre-empt/low-latency patches. I'm feeling adventurous.

      My old SuSE 8.0 box, that used 2.4.18, worked just fine, so I think it's something that red hat screwed up. There's a bug in their bugzilla about some people experiencing swap storms so bad it takes 10 minutes for a newline in a shell!

    4. Re:RedHat kernels by bogie · · Score: 2, Informative

      So your saying the alternative Windows doesn't run like shit once a heavy disk task starts? That's sure not my experience. I just posted this in another thread, but once you start any heavy disk task under Windows you an forget about doing anything else with the OS as you get to watch everything slow to a crawl.

      Try out this newest kernel or the preempt patches. ALso like someone else said make sure you have the right hard drive flags set. After making sure your hdparm setting are correct tune ext3 as well.

      to change ext3

      add data=writeback to the mount points you want to be writeback not data=ordered in fstab
      mkinitrd /boot/initrd-kernalversion.img kernelversion (yes this is odd but its the way until you hard code ext3 into the kernel)
      update grub if you used a different name to point to correct .img, usually you don't have to do this though

      My experience with RH 8.0 after upgrading to 2.4.20, making sure hdparm was correct, and change the ext3 journal type improved dramitically.

      --
      If you wanna get rich, you know that payback is a bitch
  17. Uhh....what timing by Cable_Monkey · · Score: 5, Funny

    All joking aside, I was in the middle of compiling 2.4.20 when I saw this article...

    1. Re:Uhh....what timing by Lennie · · Score: 2, Informative

      Same here, well, downloaded the patch...
      Control-C, lftp ftp.xx.kernel.org/pub/linux/kernel/v2.4/
      cp -va .config ../
      bzcat ../patch-2.4.21.bz2 | patch -p1
      cp -va ../.config .
      make oldconfig
      make menuconfig
      make...

      --
      New things are always on the horizon
  18. Re:why not posting the http links instead of the f by Isaac-Lew · · Score: 2, Informative

    wget will work just as well for http and anonymous ftp transfers. even a little faster for ftp, since it's less letters :).

  19. Re:why not posting the http links instead of the f by SuperBanana · · Score: 3, Funny
    ftp needs much more time and authentication stuff for login, commandos and so forth.

    Man, can't a guy download a kernel via FTP without a bunch of armed dudes storming the place? Those SCO guys just don't know when to give it up.

  20. Re:Quick Question by Isaac-Lew · · Score: 2, Informative
    Did you try backing up your /usr/src/linux-2.4*/.config file and then run:

    make oldconfig

    That will only prompt you for new stuff, rather than go back through every single option.

  21. Re:Quick Question by Osty · · Score: 5, Interesting

    When is it worth upgrading kernel versions?

    When there's a compelling reason to upgrade. Those fall into two categories:

    • The kernel fixes a previous security problem, or
    • The kernel provides new features that you require for your product (not "want", but "need").

    Any other reason is superfluous, especially for a server machine.

    Is there a way I can easily use the old configuration?

    The kernel config writes a .config file in the source root. Use that. If you patch rather than grabbing completely new sources, you won't even need to worry about copying that file around (unless you do a make mrproper, which you probably don't need to do unless stuff starts breaking during compile).


    I must say I am very reluctant to upgrade the kernel.. especially when I don't have physical access to the machine. But I would of course love to the the fastest and most secure server as possible. Just curious what rules and procedures others use.

    Years ago, back when the kernel was being updated nearly every other week rather than once every few months (2.0/2.2 time frame), I would always download the very latest kernel and compile that. Coincidentally, I was also learning Linux at the time, so I didn't mind spending time on stuff like that, and I was in school which meant a lot more free time. These days, my only linux box is a server, so unless there's a security fix I'm inclined to just leave the box alone. It's certainly easer not to upgrade than it is to upgrade.

  22. GrSecurity update. by cyt0plas · · Score: 2, Informative

    Grsecurity has released a version for 2.4.21. I highly recommend it, especially for production environments with multiple users. I have found the ability to limit outgoing sockets by group invaluable.

    --
    Contact Me (got tired of viruses emailing me).
  23. Re:Quick Question by tka · · Score: 2, Informative

    When is it worth upgrading kernel versions?

    This seems to be frequent question. I'd say that you don't need to compile new kernel until the old one doesn't have the xyz feature that you need and/or you feel that the new kernel is far more reliable and faster.

    In other words: some still use 2.2 series because there is no reason (for them) to upgrade.

    Remember that you can use modules to get that xyz feature..

  24. 13th? by jmays · · Score: 5, Funny

    Wait, recompile my kernel on Friday the 13th? I think not ....

    --
    KARMA TAG! You're it.
    1. Re:13th? by cperciva · · Score: 4, Funny

      Friday the 13th means nothing to Linux. The day you want to avoid upgrading to a new kernel is thanksgiving.

    2. Re:13th? by NanoGator · · Score: 2

      "Friday the 13th means nothing to Linux. The day you want to avoid upgrading to a new kernel is thanksgiving. "

      I'm not familiar enough with Linux to understand this joke. Somebody please explain it?

      (sorry to be a spoilsport!)

      --
      "Derp de derp."
    3. Re:13th? by cperciva · · Score: 3, Informative

      What happened on thanksgiving?

      Thanksgiving 2002 saw the 2.4.20 data corruption on umount kernel released; thanksgiving 2001 saw the famous 2.4.15 "greased turkey" data corruption on umount kernel released.

      There have been other kernels with problems, but it seems that the data corruption bugs tend to arrive with thanksgiving.

    4. Re:13th? by cperciva · · Score: 4, Informative

      The past two thanksgivings have seen kernels released (2.4.15 and 2.4.20) with serious data-corruption-on-umount bugs.

  25. Make mine unixfree, please by yukster · · Score: 4, Funny

    Um, can I get mine without the SCO code, please? That Darrell McBride is a scary man:

    The Linux business model was bound to change, and some people are having a hard time accepting this, McBride says. "The whole concept of getting something for nothing just doesn't hold up," he says. "The notion that you're going to run a Fortune 1,000 company on something that in the end could be more like Napster than an enterprise software system, it's a big question mark."
    InformationWeek, today
  26. Agree, noticed odd CPU load when burning by SuperBanana · · Score: 2
    So is there been something screwy with the IDE-CD subsystem in Linux lately?

    I'll second that. I noticed after going to 2.4.20 that whenever I burn a CD(and this is on an 8x writer, not exactly 'fast'), the CPU(Athlon 1.5ghz) goes to 30%, all of it system time-and the system slows to a crawl, cursor jumping and everything-which is new- and I've got 32bit IO and unmasked IRQs set on all my IDE devices....

  27. Re:Quick Question by bourne · · Score: 2, Informative

    Is there a way I can easily use the old configuration? Any HOW-TO on this?

    Copy the old arch/$(ARCH)/config.in file to the new tree and 'make oldconfig'

  28. Linux Tech. Support by TrollBridge · · Score: 2, Insightful
    The parent post is a perfect example of what Linux tech support usually looks like.

    Sure, running an RC on a production box isn't really bright, but instead of explaining that (and yes, it really shouldn't have to be explained), the typical response to any such Linux-related questions usually is something to the effect of "You're a fucking moron, RTFM".

    Not a good way to establish the Linux community as a helpful technical resource, my friends.

    --
    There's a Mercedes gap too. I want one and can't afford one, but it's not government's job to do anything about it.
    1. Re:Linux Tech. Support by ichimunki · · Score: 4, Insightful

      Sounded more like laziness than cluelessness/newbie-ism to me. If the person was smart enough to get a release candidate kernel onto his server, he's either smart enough to figure out if he wants/needs to update to the actual release or he's using a distro and should ask them for an updated package that is known to work with their other packages.

      --
      I do not have a signature
  29. Re:why not posting the http links instead of the f by tomhudson · · Score: 3, Informative
    1. because of the extra overhead in http transfers (the server's overloaded already - why put extra load on it)
    2. because of the ability to resume ftp transfers (w/o browser add-ins)
    3. because the people who are actually going to comile it are at ease with ftp (prevents wannabes from uselessly sucking up bandwidth and/or hosing their systems doing a fucked-up compile/install :-)
  30. how ironic... by Imoen1337 · · Score: 3, Funny

    That a new kernel comes out on Friday the 13th.

  31. Re:excellent, we can switch to this (SCO) by Anonymous Coward · · Score: 5, Funny

    From the Release notes:

    > o [Bluetooth] Use very short disconnect timeout for SCO connections.
    > o [Bluetooth] Kill incoming SCO connection when SCO socket is closed.
    > o [Bluetooth] Support for SCO (voice) over HCI USB

    Are these the lines SCO's bitching about?

  32. Re:why not posting the http links instead of the f by QuMa · · Score: 4, Insightful
    1. HTTP has no more overhead than FTP, and in most cases less.
    2. So get a better browser (opera comes to mind) or don't use your browser. Just because it's http doesn't mean you have to use your browser.
    3. which they can do anyway
  33. This is a known problem, if: by WD · · Score: 4, Informative

    If the following are true, then the high CPU usage is expected:
    -You have an IDE CD burner
    -You are using IDE-SCSI emulation
    -You are burning a CD with a blocksize other than 2048 (such as redbook audio, or (S)VCD, etc..)

    If the above are all true, the ide-scsi emulation reverts to PIO mode. Supposedly this will be fixed for 2.6

  34. Re:excellent, we can switch to this (SCO) by nchip · · Score: 3, Informative

    From the Release notes:

    > o [Bluetooth] Use very short disconnect timeout for SCO connections.
    > o [Bluetooth] Kill incoming SCO connection when SCO socket is closed.
    > o [Bluetooth] Support for SCO (voice) over HCI USB

    Are these the lines SCO's bitching about?

    Nope. SCO in the bluetooth world means Synchronous Connection Oriented link.
    Used mostly with bluetooth wireless handsfree devices.

    --
    signatures pending - ansa@kos.to - (dont mail there)
  35. Re:Excelent by PipoDeClown · · Score: 3, Funny

    Your writing on a Linux machine now?

  36. 2.4.21 by JWSmythe · · Score: 4, Informative

    Yippie! 2.4.21 is finally here! :) (I got it about an hour before the /. story showed up.)

    They now have Opteron support in there.. I knew it was in the pre, I was just wondering if the new kernel or the rest of my hardware would show up first. I have everything for a dual Opteron system, except the processors and case. I'm so anxious, I'm going to burst. :)

    ( ) 386
    ( ) 486
    ( ) 586/K5/5x86/6x86/6x86MX
    ( ) Pentium-Classic
    ( ) Pentium-MMX
    ( ) Pentium-Pro/Celeron/Pentium-II
    ( ) Pentium-III/Celeron(Coppermine)
    ( ) Pentium-4
    ( ) K6/K6-II/K6-III
    ( ) Athlon/Duron/K7
    (X) Opteron/Athlon64/Hammer/K8
    ( ) Elan
    ( ) Crusoe
    ( ) Winchip-C6
    ( ) Winchip-2
    ( ) Winchip-2A/Winchip-3
    ( ) CyrixIII/VIA-C3
    ( ) VIA-C3-2

    I'm going to be a compiling fool when the rest of the parts show up. :) I'm going to try to get Slackware running on it. :)

    --
    Serious? Seriousness is well above my pay grade.
  37. Obligatory SCO comment... by sahonen · · Score: 2, Funny

    Hopefully, by 2.6 SCO will actually TELL US what code got copied, so we can change the comments and variable names so it doesn't match anymore...

    --
    Make me a friend and I'll mod you up
  38. BitTorrent Link by redhat421 · · Score: 2, Informative
  39. Re:Impressive! by KewlPC · · Score: 3, Funny

    He could be running a 386 emulator on his 286.

    Or maybe he's cross-compiling.

    Or...

    Shut up ;)

  40. ccache for the compulsive kernel compiler by Corporate+Gadfly · · Score: 2, Interesting
    For the compulsive kernel compilers amongst us, ccache is a lot of help.

    From their page:
    ccache is a compiler cache. It acts as a caching pre-processor to C/C++ compilers, using the -E compiler switch and a hash to detect when a compilation can be satisfied from cache. This often results in a 5 to 10 times speedup in common compilations.
    So, if your normal kernel build command is:
    make dep clean && make bzImage modules modules_install
    then, your ccache version of that command would be:
    make dep clean && make CC="ccache gcc" bzImage modules modules_install
    Trust me, it will save you a lot of time, especially if you are constantly tweaking your config settings and recompiling all the time.

    If you compile as root, usually the cache directory will be /root/.cache
    You can tell ccache to only reserve so much disk space for itself by issuing a
    ccache -M 100M
    command to reserve 100M.
    --
    Corporate Gadfly
    Jonathan Archer: the most beaten up Enterprise captain in Star Trek history
    1. Re:ccache for the compulsive kernel compiler by caluml · · Score: 2, Informative
      Something better than that is a distributed C compiler.

      distcc.samba.org. It's another fine piece of coding from the Samba team. It uses your standard gcc, and does parallel builds on other machines. Really speeds things up.

  41. Re:Broadcom support by wazlaf · · Score: 2, Informative

    Just apply the Host AP patch and your Prism cards will work just fine.

  42. Omitted From Changelog by Anonymous Coward · · Score: 5, Funny

    - Removed offending SCO source code.
    - Replaced offending SCO source code with ASCII art of a middle finger.

  43. Re:oops! My bad.... by Minna+Kirai · · Score: 4, Insightful

    Why would anyone download multiple Debian CDs before installing? That just doesn't make sense. The most you should download is a 150 meg bootable CDROM image, then let the rest of the packages you want come over HTTP when you choose to install them.

    Debian prides itself on an enormous amount of packages... nearly twice as many, counting bytes, as RedHat provides. To attempt to download "a copy of Debian" is wrong and wasteful. The fun of Debian comes in when you decide, on the spur of the moment, to try some exotic free software program and can apt-get it in a much less time that it would take to even figure out the name of the RPM you'd need to install on a "normal" Linux system.

    Even if the desired install computer doesn't have fast internet access, burning 7 CDs is excessive. There probabably won't even be 2 CDs worth of packages you really want to install. Of the top ten largest packages in Debian, six of them are only desirable for hardcore software developers.

  44. Wow, lotsa changes! by mj01nir · · Score: 5, Funny

    Just finished reviewing the ChangeLog. Did anything not get touched this time? Good lord, there are arcnet patches in here.

    Also, when does Alan Cox sleep? Prehaps he's a new form of undead with an affinity for coding? Maybe he has cloned himself a few times? Alan, however you're doing it, we appreciate all of your hard work. Now go take a nice, long nap.

    --
    the no .sig .sig
    1. Re:Wow, lotsa changes! by rtscts · · Score: 5, Funny

      I think Slashdot reported that Alan had been merged directly into the kernel a few years back. He no longer has any need for his physical body.

      I believe there was even an X-File about it.. some shack in the middle of nowhere with a T1.

  45. Re:oops! My bad.... by Penguin+Follower · · Score: 2, Interesting
    Why would anyone download multiple Debian CDs before installing? That just doesn't make sense. The most you should download is a 150 meg bootable CDROM image, then let the rest of the packages you want come over HTTP when you choose to install them.
    1. Because I've never used Debian before, I may fsck it up and wanna reinstall (I'm not a guru by any stretch of the imagination -- the Unix shell scripting course I just finished last quarter still gives me nightmares...)
    2. I like hard copies. I have a shelf full of downloaded and paid-for CD's of Linux software... probably about 100 discs of Linux software altogether.
    3. And last but not least, because I can!
    Debian prides itself on an enormous amount of packages... nearly twice as many, counting bytes, as RedHat provides. To attempt to download "a copy of Debian" is wrong and wasteful.

    Lots of packages = Choice. I like choice ;) Wrong and Wasteful? In the sense of bandwidth (for the server), yes. Although, I am spending $50/mo for cablemodem, so I got my money's worth this month! Can't say so for kernel.org :( However, if I really like Debian, I will probably buy a copy from now on. As I said, I like hard copies.

    The fun of Debian comes in when you decide, on the spur of the moment, to try some exotic free software program and can apt-get it in a much less time that it would take to even figure out the name of the RPM you'd need to install on a "normal" Linux system.

    Yes, I have heard of the great "apt-get" and will definitely exercise it a bit. I don't know why you have a problem with the naming of RPMs. I find that it is usually the same as the program or package name. Then again, I've been dealing with RPMs almost entirely since '97, when I started out on RH 5.2 Matter of fact, RPMs are a nice idea, just implemented somewhat wrong, IMHO.

    Even if the desired install computer doesn't have fast internet access, burning 7 CDs is excessive. There probabably won't even be 2 CDs worth of packages you really want to install. Of the top ten largest packages in Debian, six of them are only desirable for hardcore software developers.

    I'm used to swapping 3 discs around during an install... I started out with RedHat & Mandrake...

    Anywho, it's pointless, as the downloads are already finished. I've already started burning the images to disc.
  46. Re:Is it worth upgrading for old Red Hat Linux 7.x by bazmonkey · · Score: 2, Interesting

    Well, I didn't look too hard into it (sorry, I'm at work and it's not exactly priority), but the Changelog doesn't mention emu10k1 or anything about soundblasters. Do you know if you can make the problem happen on other video players, xine, aviplay, xanim, etc.?

    Also, you might want to give the ALSA drivers a chance. The new kernels are pushing it as the new sound architecture for Linux, and sometimes they make a big difference. Besides, having everything set up for ALSA and running properly will make it easier to move on to 2.6 kernels.

    Like I said in my first post, compiling a kernel for a computer of your computer's stature is a matter of copying the old config, checking to see if there's anything else you need to change, and then waiting for a couple minutes. Work a little Grub/Lilo magic, and shzaam!, new kernel. You could be telling me if the new kernel helps within a half hour if you started soon.

    If nothing else, IDE I/O is always a good thing to work on. My lowly laptop is definitely getting a 2.4.21, if not a 2.5. It takes me a tad longer; I use the cryptoapi modules and that always seems to take extra time.

  47. What sort of a slashdotting is this? by meringuoid · · Score: 2, Funny

    Downloading from kernel.org at 57.12 K/s... which is just about as fast as my ADSL link can gulp it down. People, you're not doing your duty! Melt that server!... as soon as my download finishes, that is.

    --
    Real Daleks don't climb stairs - they level the building.
  48. as a side note....for LP Patch users by Lumpy · · Score: 2, Informative

    The Linux Progress Patch for 2.4.20 still works with this IF you do the following....

    Use 2.4.20 source
    patch for LPP
    patch to 2.4.21

    Voila... that nice Purdy linux boot screen is still there for your relatives that ball up on the floor crying when the boot messages start flying...

    --
    Do not look at laser with remaining good eye.
  49. Re:oops! My bad.... by Dachannien · · Score: 2, Interesting

    The fun of Debian comes in when you decide, on the spur of the moment, to try some exotic free software program and can apt-get it in a much less time that it would take to even figure out the name of the RPM you'd need to install on a "normal" Linux system.

    As in, "Tank, I need a pilot program for a V-212 helicopter."

    I always forget to install wget until I type it in and realize I haven't installed it. Five seconds and one apt-get later, I can just hit up twice and enter once. ;)

  50. Re:oops! My bad.... by Minna+Kirai · · Score: 4, Insightful

    Yes, I have heard of the great "apt-get" and will definitely exercise it a bit.

    Even if you install packages from CD-Rom, you'll use the same interface as if you were getting it live from HTTP. The only difference is that it'll prompt you to insert the right disc first... and since most packages are small, it'll often take more time for you to find the disc than to just get it from the server.

    You didn't mention if you had downloaded the stable or testing Debian... testing is generally prefered, because it's not as painfully obselete. If you value stability, "stable" is good of course. But if you want to have fun and experiment, then newer is better. And if you're using "testing", then you'll probably want to keep up with changes made after the CDs were burnt. Debian "testing" CD-Roms go obselete really fast.

    I don't know why you have a problem with the naming of RPMs. I find that it is usually the same as the program or package name.

    RPM names also contain at least the version string, and often an indication of which architecture the software will run on. Sometimes supported OS versions are mixed in too. For example, when I tried to install a package on a Red Hat system, I had to download that RPM. Then go to install it, and find out I needed multiple other RPMs first, which need even more RPMs to work.

    The point of apt-get is you, the installing user, never even see the *.deb file that the package actually comes in. The hunt for dependencies is completely hidden from you.

    Of course, RedHat users can optionally run apt-get themselves, but that's not formally supported by the distribution developer.

    I won't go into the whole problem of not getting *.deb files for new, bleeding edge software. It's an accepted fact that Debian users who wish to try something brand-new will be compiling it themselves.

  51. Re:Intel SATA Support by Alan+Cox · · Score: 3, Informative

    If you do then you should also get Jeff Garzik's new sata as scsi stack patch and use that.

  52. Re:2.4.21? by Kourino · · Score: 2, Informative

    The module-init-tools link is valid, but you really should read this if you want to try 2.5 and haven't been following the development.

  53. kernel.org is inappropriate by rossz · · Score: 2, Interesting
    When I tried to read the changelog, I got this:
    You have attempted to access an Internet site that has been judged inappropriate. This is a violation of the companyâ(TM)s Internet policy. This attempt has been logged. Repeated attempts will be reported to your manager and may result in disciplinary action.
    Not doubt because the changelog is terrorist related.
    --
    -- Will program for bandwidth
  54. Re:Vendor Kernels by kasperd · · Score: 2, Informative

    Having said that, I agree that it's highly unlikely that the patch will cleanly install against a vendor kernel, since they usually have lots of little mods in them.

    If you install the .src.rpm for the RedHat kernel, you will actually get the original .tar.bz2 file and all the individual patches. So it would be no problem to patch against that.

    --

    Do you care about the security of your wireless mouse?
  55. OT: 2.5.x and nvidia drivers by havardi · · Score: 2, Informative
    Slightly OT; I was using 2.4 kernel mostly because of nvidias drivers not compiling for 2.5.x. Then I found this site that provides up-to-date nvidia driver patches for 2.5.x including 2.5.70. (I had found patches before but they were always not-so-fresh)

    One can download the nvidia driver from ftp://download.nvidia.com (the website only seems to link an "installer" version, which was irritating)

    Now I'm happily runny mozilla-xft without those buggy artifacts the nv driver has-- and GL is always nice...

  56. Re:why not posting the http links instead of the f by JDWTopGuy · · Score: 2

    1. just get over it already and download the stupid patch version
    2. ????????
    3. PROFIT!!!!!

    Dang, I need a beowulf cluster to compile this new kernel! I oughta get a soviet russian to do it for me. All your base are belong to slashdotted kernel.org!

    Ahhh, feel the karma burnin'...

    --
    Ron Paul 2012