On Wed, Apr 20, 2011 at 11:34:59PM -0500, William Hubbs wrote: > On Thu, Apr 21, 2011 at 04:31:46AM +0200, Jeroen Roovers wrote: > > How should the udev rules be changed to match /any/ init system? > > For an example of the problem, take a look on your system at > /lib/udev/rules.d/90-network.rules. This is part of openrc's hotplug > functionality. Basically it tries to run > /etc/init.d/net.$INTERFACE start when a network interface is added to > the system and rc_hotplug allows it. > > In net-wireless/bluez, you will see similar integration between openrc > and udev. Once bluez is installed, /lib/udev/rules.d/70-bluetooth.rules > runs bluetooth.sh which tries to run a service in /etc/init.d. > > To make things work with /any/ init system, the best way to go would be > to make it a practice not to run services from within udev rules or > external run scripts like net.sh and bluetooth.sh in /lib/udev.
Another option for this would be to include this level of udev integration in the openrc package itself instead of spreading it through the other packages. If I do that, when you install openrc, you would optionally get those pieces that integrate it with udev instead of those pieces coming from the individual packages. Comments? William
pgpTgyLblWyvb.pgp
Description: PGP signature
