Kernel for a server, modules or builtin?

petrjanda

On a server kernel, should most stuff be compiled as Module or into the kernel? Also what stuff should be built-in within the kernel in all cases and at all costs, thus, not as module.
_________________
There is, a not-born, a not-become, a not-made, a not-compounded. If that unborn, not-become, not-made, not-compounded were not, there would be no escape from this here that is born, become, made and compounded. - Gautama Siddharta

jkt · Posted: Wed Nov 17, 2004 1:10 pm Post subject:

you'll have to built in all stuff needed for boot such as root filesystem, IDE/SCSI disks, your ATA/SCSI controller,...

everything else could be compiled as modules.

but there are also some security-related issues...

jkt · Posted: Wed Nov 17, 2004 1:22 pm Post subject:

and of course you can use initrd if you want to have your modules available during boot.

mayday147 · Posted: Wed Nov 17, 2004 1:50 pm Post subject:

I would choose to have (almost) everything compiled as built-in, because modules can be a security risk , as jkt said. It's supposed that you aren't changing your hardware too often and you know exactly what you need for your system to have everything built-in the kernel.
_________________
gentoo.ro

hecatomb · Guru Joined: 02 Sep 2004 Posts: 525

Even when module loading support is disabled in the kernel config it is possible to manipulate system calls like LKM rootkits do.
But this is really hard work!

Putting all the needed things into the kernel and disable module loading support will stop script kiddies simply using others rootkits.

I agree to mayday147. A server normally doesn't change in hardware very often!
What else should trigger you to use modules?

jkt · Posted: Wed Nov 17, 2004 2:38 pm Post subject:

pjp · Administrator Joined: 16 Apr 2002 Posts: 20582

Moved from Other Things Gentoo.
_________________
Quis separabit? Quo animo?

petrjanda · Posted: Wed Nov 17, 2004 9:18 pm Post subject:

jkt · Posted: Thu Nov 18, 2004 5:07 pm Post subject: