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.
The best advice I can offer for kernel compiling is to just dive in and do it. Follow one of the many kernel tutorials available to get the basics in mind, and then try it out. Almost all of the compile options are nicely documented (if you use 'make menuconfig' or 'make xconfig'); read through each option and determine whether it's something you need or not. Compilation itself doesn't take all that long - on my Athlon XP 1600, about 10-15 minutes with a reasonable number of things enabled. On your 300mhz box it probably won't take more than an hour or two.
Yeah the only optimization you could achieve are on the menus by selecting your specific processor type (i guess that's not covered by the tutorials since it's pretty obvious) and of course, not compiling what you don't need (this is the harder part if you don't know too much about hardware and compiling the kernel, leave this one for some time later when you have more experience).
Before compiling the kernel navigate in the make menuconfig or make xconfig menus to see how it's organized, what's there, it's a very good learning experience.
Hope that helps.
The only real reason to worry about compiling the 2.6 kernel would be because of new hardware unsupported by 2.4.... that is unlikely a need in your case :-)
I would use the stock kernel that comes with slackware and use it until you learn more about linux generally and Slackware in particular. Learn about file navigation, text editing, use of the tools that are included, learn to compile and install programs. After that you can then try your hand at compiling a kernel. I would start out taking the included sources, using the existing configure file and do a make oldconfig. Then just start pruning out items that you are sure are not needed. After you build a couple of kernels that way and get it running, then you will have the confidence and knowledge to jump to a 2.6 kernel where it is not really recommended to just blindly use the old configure file from the 2.4 kernel.
In my opinion the best way to start is to keep the same kernel content that you have in your current 2.4.x kernel.
You can download the config file (which holds the kernel content) from the slackware cd and put in the 2.6.7 sources directory.
Don't forget to keep a fallback option to your original kernel in your lilo configuration.