[systemd-devel] Communicating need

[Lennart Poettering]

On Mon, 09.05.11 19:27, Gustavo Sverzut Barbieri (barbieri at profusion.mobi) wrote:

> > So I was curious how these problems would be solved in the systemd world?
> > Reading through the documentation I came up with the following:
> >
> > The Kernel Driver is still going to get loaded regardless, because udevd
> > runs modprobe, not systemd.
> >
> 
> you can blacklist it if there is no userspace tools to handle it. That would
> require some packaging changes to cope, but it is doable.
> 
> If it's desirable to load it if there is some user space using it, one you'd
> need to add some udev rule to listen for module, check for userspace (dbus
> name? but where? all user session bus? or with the user in current seat?),
> then rmmod if there is nothing using it.  OTOH, when user starts, it would
> be needed to ask some new tool if there is such device and load a module for
> it. It's troublesome, but I guess it is doable. But is it worth?

No no, please don't think of things like this.

I think the system service should be started if a process requests it,
we never should block that. If you fear that that means that the system
service is always started that way, even though it isn't strictly
necessary, than fix the problem properly: and don't even autostart the
agent which might trigger the system service to start.

i.e. as suggested in my other mail: pull the agent in from the hw device
popping up, too.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.