just upgraded slackware from kernel 2.4.22 to 2.6.6
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
This is the first I had seen about upgrades of anything on slack to use the 2.6.# kernels.
I had assumed since the docs stated that 9.1 was "kernel 2.6 ready" that it was updated for the kernel.
Better fine print is needed...
I would assume now that this has come to light that this may be why we see so many post in the forum about kernel 2.6.# compile and running issues.
Also noted during an investigation of this I saw that even slack current was only using kernel version 2.4.26. That would indicate to me slack is "not" 2.6.# stable nor ready. Which could explain the problems encountered using 2.6.# and the number of off slack upgrades needed.
I have seen within the forum a mention of a 2.6.# kernel by Pat out there somewhere though I have not seen the src myself...
As I have stated elsewhere in the forum "I would use kernels above 2.4.26 with slack with caution" If you desire a totally stable system and/or running a secure server you should NOT use slack-current nor kernels outside the slack levels (2.4.26).
The newer version of module-init-tools must only be required by 2.6.6, (and maybe later).
I've been running 2.6.5 for a while now and all I had to modify was my fstab, (no longer needed umask), and I'm still running version 0.9.14 of module-init-tools.
Last edited by pave_spectre; 05-31-2004 at 08:52 AM.