Slashdot Mirror

← Back to Stories (view on slashdot.org)

Configuring the 2.6 Linux Kernel

Posted by CowboyNeal on from the getting-one's-compile-on dept.

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.

2 of 279 comments (clear)

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

  2. 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?