Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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'm using Slackware 10.0 with the Linux 2.4.26 kernel, since it has the Linux 2.6.7 as an alternate choice in /testing folder... is it worth upgrading to this? If so... how do you go about updating it... this would be my first kernel upgrade. If not, why?
You can load the 2.6.7 kernel even though it is in testing.But on different systems,this can behave differently,rather erratic at times.So better go for the stable release.Download the kernel from www.kernel.org or from .Better read the documentation that accompanies the package.
Upgrading the kernel is easy on Slackware 10.0. I'm running an Acer Aspire 3230 with an AMD K6 and 32 mB of memory, and I upgraded to the 2.6.7 kernel. It seems much faster. Type "more /boot/README.initrd" in the console for instructions on how to install the kernel binaries. You should only need to install the first two packages (installpkg kernel-generic[...] and installpkg kernel-modules[...]) as mkinitrd should already be installed. Then, make an initrd based on the instructions. I've had one problem. When my computer starts up, it takes forever to update kernel modules. I fixed this by realizing that each time, the kernel didn't realize there was a modules.dep in my /lib/modules/2.6.7 directory. I'm trying to remember the file that I edited to speed it up, but it doesn't come to memory. You may or may not have this problem. Good luck.
Originally posted by javamdk ... and see if I can compile it myself... *eeps* Wish me the best of luck on that lol
This won't compile a kernel. You should have two packages: kernel-generic-2.6.7.tgz and kernel-modules-2.6.7.tgz. You will basically be installing the generic binaries. To actually compile a kernel for your machine, you have to have the source. Try installing these binaries first. If they work, you might want to compile your own kernel later on. If you don't have these packages, look on the Slackware site. I forget where I found mine, but they didn't come with the CDs.
On my Slackware 10.0 Disc 2, there is a directory called /testing/packages and in there is the kernel-module & kernel-generic -- this is for 2.6.7. I installed the packages in my /tmp folder under root... then I installed kernel-module and kernel-generic by invoking installpkg. Afterwards, since I do have Initial RamDisk installed, I created the initrd in /boot... then changed my /etc/lilo.conf to the new kernel image and lastly added the initrd after the image. Saved and exited *I did backup * then ran lilo for it to take affect... and voila.. booted back the computer and it's now using 2.6.7 as it's kernel.
I did have a problem just a second ago with Alsa sound... but in that same CD it (disc 2), it had the new Alsa driver; I believe Kernel 2.6.7 is only using Alsa now... anyways I installed the new Alsa driver, ran alsaconf - Voila, I got sound!! Everything else seems to be running great, but I noticed that my /dev/cdrom is now my second bay cd-rw instead of my cd-rom. Also noticed it cleaned up a lot in the /dev area!
I did do this right, didn't I? I think I did, if not please tell me if there are extra steps. Anyways, another question: Since I installed the kernel 2.6.7 to take over what I had before, would it be a good idea to clean out the old 2.4.? version? Or did it do that automatically? If not, how do I go about to clean all that junk out OR is it just not worth bothering with? PS: Does it take a lot of space on my HDD?
You installed it the same way I did, so you should be all set. It should be running fine. Congratulations on running 2.6.7 kernel.
As for cleaning the old kernel out, I didn't. When you install the new kernel, it won't clean out the old 2.4.xx kernel. I don't think that makes much of a difference. I don't know how large the files are. I doubt it's over 50mB... I'll have to check that out. I am not going to clean out my old kernel files just in case something totally strange happens (I'm sort of paranoid about that).
If you did want to clean out some files if your hard drive is very small, you could delete the directory /usr/lib/modules/2.4.26 or something like that. Just cd to /usr/lib/modules and ls. There will be two things for modules. Just delete the 2.4.xx folder. If you cd to /boot, there will be many files with 2.4 in it. I guess you could delete all of those. I'm not sure about what exactly to delete, as I don't plan on deleting the old stuff.
I'm not very good with files in /dev, but I thought that /dev/cdrom was a link to another file in /dev. For example, my CD-ROM drive is /dev/hdd and I think that /dev/cdrom links to that. I'm not sure about this, so I hope someone else can answer that question.
It looks as though you have a great new kernel installed properly. I can't imagine why it cleaned up /dev and switched /dev/cdrom. Oh, and by the way, I didn't know that the kernel files were in the second CD-ROM. I downloaded them myself. I'm glad the CD-R that I burned the kernel to was a multi-session disk so I didn't waste it completely. Good luck!
Okay, I checked the files in /boot and /lib/modules/2.4.26 and I found that they totaled about 15 mB. Unless you have a really tiny hard drive, they shouldn't be in the way much. You might want to delete the 2.4.26 kernel source if you have it, however (/usr/src/linux-2.4.26); it takes up quite some space. Anyways, I hope I've helped. Good luck with your new kernel.
Yeah that definitely does help... I'll probably keep the files in /lib/modules/2.4.26 but might remove the source file which is like 115MB. Later I'll replace it with the new 2.6.7 Kernel Source and tweak things up manually.
Thank you a bunch... you have been a big help in my linux journey. -JoeY