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