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.
Just some quick questions relating to compiling using modules as opposed to compiling within kernel.
Take usb support for example. Compiling usb into modules makes for a smaller kernel.
Should this translate to a faster booting system or do the extra modules for usb balance things out? Would one setup generally use more resources or memory? And do loaded modules listed in lsmod use system resources? (I would think so) More or less than when compiled into the kernel?
Tried it both ways. With usb as modules and with usb compiled into kernel. Kernel was about 6% smaller with usb as modules.
Checked system memory usage after restart using top and both were virtually the same after 1 minute as were load averages. Certain items such as dhcp and ntp had different pids, I guess by loading a little earlier or later with each setup, but all in all most things were very similar.
Am I correct that the general rule, if everything seems to be functioning, is to keep the kernel as small as possible, using modules when possible, or in these days of high memory & fast hard drives, it doesn't matter much anymore?!!
The advantage of compiling some drivers as modules is that
they can be loaded with some parameters
Example for a NIC card module, you can load the module
with a speed parameter or turn autonegociation on or off
For the bttv module (driver for tv card), you can select
which tuner you want to use, if you want radio capability...
(all are parameters for bttv module)
The other advantage is that you could unload them or
modprobe just the drivers you need
Example, you compile the Apple file system as module and
modprobe it only when you insert an Apple CD...