[klibc] klibc and udev

Aaron Griffin aaronmgriffin at gmail.com
Mon Aug 14 09:58:48 PDT 2006

On 8/14/06, Greg KH <greg at kroah.com> wrote:
> The big issue with udev not using klibc is that you don't want a long
> running daemon to use klibc because of the memory management usage of
> klibc.

Yeah, I get that, but running udev in early userspace for a few
seconds is the use-case I'm referring to.  It's far more ideal to run
udev for needed devices and module loading then to try to generate
them manually.

Whenever I bring up the klibc+udev thing, someone always says "don't
use klibc for long running daemons".  I don't really understand where
this comes from.  I would not use klibc compiled applications in
normal userspace where a full C library is available.

For my usage, a klibc compiled udev is *only* used in early-userspace,
for a period of maybe 10  seconds max (assuming a long disk controller
load time).

More information about the klibc mailing list