[klibc] klibc and udev

[Greg KH]

On Mon, Aug 14, 2006 at 11:58:48AM -0500, Aaron Griffin wrote:
> 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).

Ok, you should be fine then, but please realize that you need to kill
the running instance of udevd that was created by the init version of
udev, without having any events be missed during the transition.

Not exactly the simplest thing to do :)

thanks,

greg k-h