[lkml]   [2002]   [Apr]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Re: Re: faster boots?
Someone pointed out that I may have to much stuff built into the kernel and that I should try modularizing it.  Only builing in what I need to boot and the rest as modules. 

This may be true.

It is easier IMHO to configure a NetBSD kernel or FreeBSD kernel with just what you need in the system because dmesg is more helpful IHMO on those systems.

dmesg for netbsd prints stuff like

pckbc0: using irq 12 for aux slot

and in its kernel config file there will be a line something like

pckbc* irq*

or something. Thus someone wrote a nifty little perl script that can go through dmesg and comment out of the config what is not found by the generic kernel (or the kernel installed at that time). This helped reduce my netbsd kernel from 3.6M to about 2.1M and speed up the machine some.

FreeBSD is very similar to this. Only I think it tends to have more modules in the default generic kernel.

Linux on the other hand prints out all this other stuff which makes it harder IMHO to determine weather or not you need driver foo built into the kernel. Thus I know that when I build a Linux kernel there is stuff that is in it that I don't need but don't know what it is.

Also the bsd's run 'config' against the config file which actually checks to see if the config file that was edited is actually going to build and it also updates some other stuff. Although that is not 100% accurate, but a big help.

So what is the best way in Linux to figure out what you can remove from the kernel to make it smaller and boot hopefully faster on low end machines?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:25    [W:0.039 / U:11.012 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site