On Wed, Jun 25, 2014 at 01:49:58PM +0530, Weldon Goree wrote: > On 06/24/2014 11:58 AM, Markus Teich wrote: > > I've built me a hardware tailored kernel, containing only the drivers, my > > laptop > > needs and mostly statically linked. Only a few drivers (UMTS modem, wifi, > > audio) > > are built as modules for convenience reasons, so I don't have to reboot if > > one > > of them fails, but can just reload the module. > > That said, even for a live system as long as you don't mind loading an > immense kernel (Slackware's "huge" is 6.4M, for instance; twice the size > of "generic", and "huge" still has some modules) I don't think there's > ever a situation where you would _need_ a modular kernel. The > "run-anywhere" kernel I've been working on has basically every possible > hardware selection built-in, and modules for behavior or features. A > modular kernel in principle seems to suck less than a big static one, > but in practice it ties you down to whatever daemon out there in > userland is telling the kernel what to do with hardware (mdev, > fortunately, sucks less than udev, but I'd still rather just have the > kernel deal with stuff; if we could get rid of people's obsession with > hotplugging hardware we wouldn't even need that...)
There's also smdev[0] if you are interested. [0] http://git.2f30.org/smdev
