Hi there
just wanted to know if there are any Distros Out featuring the new 2.6 Kernel..

Any news on slack version with kernel 2.6

i read on the Official Slack Site that 9.1 is KERNEL 2.6 READY!!
what does that mean can anyone Explain

With all the Slack references, I doubt you'll be too interested in it, but Fedora Core is working on their next release, which will feature 2.6, KDE 3.2, and GNOME 2.5. Test 1 release is out with 2.6.1. Test 2 should be out on the 8th. Final release is scheduled for mid-April.

heard mandrake is using the 2.6 kernel in there next version 10 as for slackware just compile the 2.6.2 yourself its not as hard as it sounds

Very true - compiling kernel 2.6.x was a breeze compared to previous kernels. Not that the others were hard...the only problem I had was finding the kernel headers for compilation issues. I had to install them as an rpm off of pbone's site. I'm sure Slackware will have a headers package after they do an official release of a 2.6 kernel.

Paul

i had no problems with headers went nice and smoothly

Maybe I did something completely wrong, but after installing the kernel, I couldn't compile anything until I installed the headers seperately. Maybe I did the install wrong? I did this:

make menuconfig (chose appropriate options)
make
make modules_install

I copied the kernel and system.map to /boot, edited my lilo.conf, made all of the appropriate changes to my init scripts, cdrom device, and it all worked great. Are the headers part of the source code you D/L from kernel.org?

Paul

i got the 2.6.2 kernel from kernel.org. I updated the kernel the day after I installed linux, and it was a breeze.

After you unarchive the file to your /usr/src/linux directory, edit the Makefile and uncomment the install_path line. then type:

make menuconfig (or make xconfig)
make
su -c "make modules_install"
make install

It'll put bzImage as vmlinuz in your /boot directory automatically (also system.map), modify /etc/lilo.conf for you, and run lilo. All you have to do at that point is reboot (unless you want to make vmlinuz and System.map symbolic links)

That's exactly what I did, except I did the kernel install in /boot manually. I prefer to do that step manually, along with the lilo installation. My problem was with the headers - they weren't installed and I had to find, download and install them seperately before I could compile anything. No biggy, it works fine now.