Slashdot Mirror


Configuring the 2.6 Linux Kernel

An anonymous reader writes "This article is the first in a series by William von Hagen on using the new Linux 2.6 kernel, with a special emphasis on the primary issues in migrating existing drivers, applications, and embedded Linux deployments to a Linux distribution based on the 2.6 kernel. Bill is the author of Linux Filesystems, Hacking the TiVo, SGML for Dummies, Installing Red Hat Linux 7, and is the coauthor of The Definitive Guide to GCC (with Kurt Wall) and The Mac OS X Power Users Guide (with Brian Profitt)." This looks to be a good series for anyone planning to migrate to Linux 2.6, and having done just that myself, I'll attest to wanting more documentation along the way.

6 of 279 comments (clear)

  1. Dissolving the 2.6 Linux Kernel in Cheese by Doomrat · · Score: -1, Troll

    be using fresh cheddarz, yo.

  2. PIMP IT UP BOY by Anonymous Coward · · Score: -1, Troll

    Anyone count how many times 'TimeSys' just happens to crop up in his article ? Clearly a goat fan.

  3. Mod parent down (-1, zealot) by Anonymous Coward · · Score: -1, Troll

    Last time I checked Debian wan't "major". I don't see Debian boxes at PC WORLD, I dont see Debian Certified Engineers, I dont see Debian with a flashy glizty easy to install installer (AND DO NOT GIVE ME THAT BULLSHIT ABOUT ARCHITECTURES, if contiki can provide a graphical operating system on machines with just 32Kibs of RAM, so should debian). Anyway, by the time it makes it to "stable" Linux 3.0 will be out.

    Debian Zealots should be shot. If they dont want to be shot, then make something worth using. BTW, urpmi kicks apt-gets ass so hard that it becomes wider than goatse!

  4. Disapointing Linux Benchmarks. by Anonymous Coward · · Score: -1, Troll

    After hearing how much the improvements in Linux performance was, I decided to do some benchmarks.

    Here are the Machines I used.
    Intel Xeon 3.2Ghz HT Server with UltraSCSI320 Hard disks
    XServe G5
    386SX with MFM hard disks

    Copying a 17 Mebibyte file from one hard drive to another.
    SCO UnixWare : 7.3 Seconds
    Windows Longhorn Server beta : 7.5 Seconds.
    Windows Server 2003 : 9 Seconds
    Mac OS X Server 2004 : 9.5 Seconds
    Windows 2000 Server : 11 Seconds
    Linux 2.7 Server : 16 Seconds.
    Linux 2.6 Server : 18 Seconds
    MSDOS on a 386DX : 20 Seconds.
    Linux 2.4 Server : 30 Seconds
    Linux 2.2 Server : 48 Seconds
    Linux 2.0 Server : 75 Seconds.

    As you can See, Linux dosent come CLOSE to beating enterprise systems at high performance servers. EVEN Msdos from a 386SX smokes Linux!
    Don't mod me down unless you can justify these speeds. It is pretty obvious by now why SCO is suing Linux, because they are stealing their code to gain speed. And yes, DMA WAS ENABLED.

  5. Re:2.6 breaks KVM support by Xyde · · Score: 0, Troll
    I've used a KVM w/ both 2.6.0 and 2.6.1 and have had no problems. The trick was to use "IMPS/2" as the mouse protocol instead of "Auto". That, along with your ZAxisMapping option should be all you need to get it to work. Assuming of course your KVM is ps/2.

    ...and they say Linux is ready for the masses...

    Yes, flame me to hell, you know you want to.

  6. Works in 2.4. Doesn't in 2.6. Irritating.(Really.) by imbaczek · · Score: 0, Troll

    Linux hda=remap63.

    Neither exists, nor is needed on 2.4.24. On 2.6.0 it's supposed to do what has been done automagically up until now (well, until 2.5.30.) Not to mention, it fails at it.

    Don't these guys know the 'Ain't broke? Don't fix' maxim? Props to Alan for his opposition to changes that made 2.6 impossible to use (boot!) for me (yes, I have to use OnTrack DM so I can get 100% out of my 40GB Seagate.)

    Yeah. Mod me down as troll, redundant and flamebait at the same time. Go on. But please answer this question first: how to make it work?