[lkml]   [1996]   [Apr]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: dropping kerneld...
In, article <>,
"Lauri Tischler" <> writes:
> Yup, I'm missing a lot of pain and useless complications by not
> using kerneld and modules. Quite useless contraptions both.
Ah, come on...

Here, we have a heap of server machines, different hardware (start with
wildly differrent SCSI adapters), different software requirements (one
serves Appletalk, the rest quite frankly can't be bothered).

Before modules and initrd, I've had to build a kernel for each of these
beasts. Ugh. Now, I build the kerneld 100% modularized (OK, OK, binfmt_elf
and ext2 aren't, but they're used on every system anyway). Initrd then just
loads one SCSO adapter after the other until one is found, then kicks the
real boot process which loads the network card and protocol drivers, and
that's it. (I'm not loading the protocol stacks with kerneld because it
doesn't work yet -- every call to ifconfig would load the whole code, only
to find that there aren't any Appletalk or IPX addresses. The appropriate
kernel code should not bother to ask kerneld if SIOCG* calls are made,
IMHO, but I haven't had the time to actually do something about this.)

> Any lurking need to use kerneld is easily cured by getting enough
> memory.
That is not an option for many people out there, and if given the choice to
let heaps of dead code lie around in the kernel, or to spend a little bit
of time and one additional page of memory when I do need the code, I'll
happily take the latter route.

Life, liberty and the happiness of pursuit!
Matthias Urlichs \ Noris Network GmbH i.Gr/ Xlink-POP Nürnberg
Schleiermacherstraße 12 \ Linux+Internet / EMail:
90491 Nürnberg (Germany) \ Consulting+Programming+Networking+etc'ing
PGP: 1B 89 E2 1C 43 EA 80 44 15 D2 29 CF C6 C7 E0 DE
Click <A HREF="">here</A>. 42

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