Udev and systemd to merge [LWN.net]

Udev and systemd to merge

Posted Apr 3, 2012 17:30 UTC (Tue) by mezcalero (subscriber, #45103)
In reply to: Udev and systemd to merge by JEFFREY
Parent article: Udev and systemd to merge

Note that this doesn't mean that udevd is merged into PID 1. udevd and systemd stay two separate binaries, which are just built from the same tree.

The net result will be less lines of code, simply because we can reduce duplicate code (i.e. code which exists in both projects will now be replaced by the same implementation)

(Log in to post comments)

Make it a library?

Posted Apr 3, 2012 17:44 UTC (Tue) by Pc5Y9sbv (guest, #41328) [Link]

Hopefully, this effort will include thinking about how to factor that common part out into library form? Or perhaps a core event service and client bindings for interop? It would seem unfortunate if it was just internally shared code between two monolithic daemons.

I have never dug into the Android side of things, but wonder if there is a common ground that could serve the needs of server, desktop, laptop, mobile, router, and embedded environments. I realize that is asking a lot, particularly in terms of flexibility/performance/efficiency tradeoffs, but this feels like the kind of thing that could help keep Linux from branching off indefinitely into different niche platforms... I'm not even sure if it needs kernel side effort, given the latency and efficiency issues on mobile or embedded?

Make it a library?

Posted Apr 4, 2012 14:58 UTC (Wed) by RCL (guest, #63264) [Link]

When you start to reuse code it becomes unmaintainable. Everyone is afraid of touching the common part lest they break some functionality they cannot test for themselves (or even know about).

So unless the common part is really simple and plain and will *never* need any refactor/improvement, don't do that. The world is built upon redundancy, which helps parallelization of efforts.