On Sun 20 Dec 2015 at 16:19:34 +0800, Paul Goyette wrote: > I like to think that I run a kernel from a third class: > > HIGHLY-MODULAR > > These kernels include only a minimum amount of built-in code, > and any additional functionality is loaded as needed. I have > fewer than 20 built-in modules, and generally run with only > 40 modules total (the difference being loaded dynamically). How does one most easily create a kernel of this type (and know which parts are loadable and which are not)? I've been making my own kernels by starting with GENERIC and removing things from it that I don't have or need. Is there a simple way to see which of those things are also modules (so they can come back if I need them after all)? The names in /stand/modules don't always seem to match 100% with words from the config file. -Olaf. -- ___ Olaf 'Rhialto' Seibert -- The Doctor: No, 'eureka' is Greek for \X/ rhialto/at/xs4all.nl -- 'this bath is too hot.'
Attachment:
signature.asc
Description: PGP signature