this was my experience as well -- I don't have numbers on hand, but I
definitely reduced the size of my kernel by moving unused goodies from
'modular' to 'no.'
--
Jack Coates
Monkeynoodle: It's what's for dinner!
On Sat, 21 Apr 2001, David Douthitt wrote:
> Charles Steinkuehler wrote:
>
> > Well, I generall think almost EVERYTHING should be modules. You can regain
> > IDE support for booting by adding the modules to the initial ramdisk (the
> > linuxrc mods I posted a while ago for my SCSI-RAID support do this).
>
> When I first compiled kernels for LRP, I used the EigerStein kernel as
> my base. I later found that by NOT compiling modules, I could save
> space.... let me explain.
>
> If there is an item in the kernel configuration which is undesired,
> but generates only modules: it still takes up space even though all of
> the underlying items are modules. By removing the support altogether,
> a great deal of space can be regained. QoS comes to mind, and Linux
> Telephony.
>
> If you leave in QoS support, even though everything is modules, it
> still takes up space. If you disable QoS support, you gain a lot of
> space. You can always shift kernels around and make multiple
> configurations.
>
> Anyway, the best thing for a router would be to create your own kernel
> and remove kernel module support altogether - no more attacks from
> things like knark.o....
>
> _______________________________________________
> Leaf-devel mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/leaf-devel
>
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
