[Gllug] Module vs compiled in...

[Doug Winter]

On Fri 18 Jul Dylan wrote:
> I'm currently tinkering with LinuxFromScratch to get a good handle on
> how the system hangs together. Now, on a box with onboard devices
> (which will necessarily not be swapped out, therefore) such as NIC and
> graphics card, what are the opinions on the swings and roundabouts of
> compiling the drivers as modules or compiling them into the kernel?

As far as I can tell, the only reason to build something as a module is
because you haven't bought the device in question yet.

If you already own the thing, there's no earthly reason to put the
driver in a module where you have to dick about with it.

Obviously for distros it makes sense, because they can build a
one-size-fits-all kernel to distribute as a binary, but if you are going
to the hassle of rolling your own kernel, i don't see any advantage in
modules for know hardware.

I must admit though, I am becoming more and more sick of recompiling
kernels, and I'm planning on sticking with debian binary kernel packages
from now on.

doug.

-- 
6973E2CF print 2C95 66AD 1596 37D2 41FC  609F 76C0 A4EC 6973 E2CF
"The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself.  Therefore all
progress depends on the unreasonable man." -- George Bernard Shaw
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 240 bytes
Desc: not available
URL: <http://mailman.lug.org.uk/pipermail/gllug/attachments/20030718/a4cdc8e5/attachment.pgp>
-------------- next part --------------
-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug