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.
I think you have got kernel sources from slackware sites not from kernel.org. Then you have to installpkg kernel-sources[TAB][Enter] in the dir where your source file is. Or if you have problems with unpacking files, then go to this page: http://debianguiden.dk/dists/stable/html/tar.html
True. But since he stated that he had Volkerding's release (i.e. a prepatched source in the Slackware package format), I figured it would be a better idea to install as intended. That would automagically take care of placing everything in the correct directories, as well as creating a symlink. Simplicity is bliss.
I had untared kernel-source-2.4.21-noarch-1.tgz in /usr/src. when I do
'ls' this is the print out
Then i do cd install and then 'ls' and i have two filies: doinst.sh and slack-desc
in doinst.sh i found the following command
(cd usr/src : rm -rf linux)
( cd usr/src : ln -sf linux-2.4.21 linux )
(cd usr/src/linux-2.4.21/include : rm -rf asm)
(cd usr/src/linux-2.4.21/include : ln -sf asm-i386 asm)
Let me tell you that i had upgrade my kernel 2.4.20 to 2.4.21. but I do not remember how i did it. (one night i found it in google a site and followed the instructions, but i forgot to take notes. Now I am taking notes), Right now my system is workingvery well but i would like to have my own kernel. At the same time, I do not want to mess up my system if something goes wrong.
Pllease share your experience and knowledge with me.
Well, when compiling your new kernel, you could load the config for the old one. Usually the config resides in your kernel source directory, but if you haven't got the kernel source installed I believe the config can be retrieved from /boot (the file's called simply "config", the one in the kernel source dir is hidden, so it's ".config"). If you've been using one of the standard kernels (say, bare.i), you might be able to find the config in some other place as well, perhaps the CD - I don't know. :P
Anyway, when you're about to compile (more correctly, when you're about to prepare for compilation), you can just load the old config into, say, xconfig or menuconfig, and go with that, although I recommend you to go through the various options before you go on. You could probably do a "make oldconfig" as well, and just be prompted for options that has changed or been added. However, it's never wrong to poke around a bit in xconfig/menuconfig and get a bit more aquainted with your particular configuration and the available options.