May I ask why you want to compile a 2.6.x kernel? Here's a good quote from Kwan Lowe
The main reason was once to optimize the kernel to your environment (hardware and usage patterns). With modern hardware there is rarely a need to recompile unless there is a particular feature of a new kernel that you must have. The performance gains are probably not noticeable unless specific benchmarks are being run.
Okay, there is NO directory "/testing/linux-2.6.x" on CD2. In Linux you need to be very specific, because typos will cause your system to execute an incorrect command -- which could hose it!
This directory "/testing/packages/linux-2.6.10/" contains:
each with a corresponding .txt (text) file which explains their purpose and function. It also contains:
which is the complete and unmodified source code for the Linux kernel that you can install with pkgtool.
The directory "/testing/source/linux-2.6.x" which is probably the one to which you refer contains:
-rw-r--r-- 1 root root 50545 2005-02-03 10:32 config-2.6.10
which is the config file for this kernel, and two sub-directories:
which contain a general purpose Linux kernel and modules put together by Pat V., creator and maintainer of Slackware.
Secondly, since you're new to Linux, you should read every README.TXT file on the Slackware CDs. That way you'll learn some of this stuff and get a good head start!
Particularly, you should FIRST read the README.TXT file and the Slackware-HOWTO on CD1. In that second file you'll read this from Patrick Volkerding, the creator of Slackware
That is probably what you want to do...
The installer utilizes the 2.4.29 kernel (this still provides the best
performance on my own machines, and is also safer for partitioning
hard drives). If you want to upgrade to the 2.6.10 kernel it is also
included and the system will fully support it. See the README.initrd
file in the testing/packages/linux-2.6.10/ directory for directions on
upgrading the system to use 2.6.10 (or better yet, make it an alternate
If after reading that stuff, you STILL want to recompile your kernel, then you should really (IMO) learn some basic shell commands first
before starting. Additionally, you'll need to know your hardware intimately, and so I'd recommend you read
Kwan Lowe's Kernel Build HOWTO
in it's entirety before you start -- paying particular attention to the section titled Preparation
Hope this isn't too much for you to handle at one time, but if I may, this is how I see it.
With Windoze you have a system "made for everyone" that is unsecure and poorly designed -- much like buying the cheapest little car made just because "it's easy to use and will get me down the road."
With a properly designed Linux distribution (Slackware, for example), you have a system that is quite secure from a basic install, and more powerful than Windoze even without much tweaking. Sort of like buying a sportscar -- say a stock Corvette -- out of the box but capable of being tweaked and tuned into a very fine, high-performance street machine.
If you're just into Linux for a "check it out and kick the tires," then just do the basic install in a dual boot situation with Windoze and slowly check out Linux. Use it first for nothing more than email, web browsing, and basic office documents. Then (one app at a time) check out what else it offers. And somewhere along the line, learn the "command line" so that you can experience the raw power of Linux.
At first you might be comfortable with KDE because it looks similar to Windoze, and you can click on an icon on the desktop to get something done. But if you run a light-weight window manager such as Fluxbox, and learn some command line functions, you'll begin to experience that "sportscar performance" that's hidden from the GUI users...