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've noticed there's a lot of stuff in the kernel that I don't particular need, like any architecture other than x86/i386. Could I safely delete these directories from the kernel source and compile a new kernel, or would this be considered a bad idea?
If it's safe, where else could I possibly save some space?
If it's disk space, the 2.6.7 kernel that ships with Slack 10.0 is 1.4 MB on disk. The kernel source tree is unecessary as long as you don't need to comple anything, so you could remove the kernel source package. You can clean things up a bit by running `make mrproper` from /usr/src/linux, but that won't save enough space to make it worth the time to even type the command, especially considering that it removes all your kernel config files.
You could save a little RAM by removing support for hardware you don't need. Just use `make menuconfig` and remove the stuff you think you don't need. However, if you don't absolutely know what you're doing, you can remove too much and end up with a kernel that doesn't work as well as the supplied kernel. Again, not worth is IMO given the small amount of RAM the kernel occupies and the relatively huge amounts of RAM in modern systems. Also, most hardware support is in modules that are not loaded into RAM until they are needed.
Recompiling the kernel can speed up your system a bit, but it's always been a marginal improvement for me, so I stopped doing it. I only compile new kernels now when I want to use newer versions that aren't with slack-current. For instance, 2.6.10 isn't part of slack-current, but I decided to run it anyway.
Give us a bit more information on what you're trying to accomplish, please.