public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: openrc use flag
Date: Thu, 21 Apr 2011 14:05:05 -0500	[thread overview]
Message-ID: <20110421190505.GA12112@linux1> (raw)
In-Reply-To: <20110421043459.GA14245@linux1>

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]

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


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2011-04-21 19:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 17:24 [gentoo-dev] rfc: openrc use flag William Hubbs
2011-04-20 18:02 ` Peter Volkov
2011-04-20 18:20   ` Pacho Ramos
2011-04-21 19:30     ` William Hubbs
2011-04-21 20:03       ` Pacho Ramos
2011-04-21 20:52         ` William Hubbs
2011-04-22  9:50           ` Pacho Ramos
2011-04-22  8:26       ` Peter Volkov
2011-04-22  8:58         ` Michał Górny
2011-04-20 18:22   ` William Hubbs
2011-04-20 18:33     ` Michał Górny
2011-04-21  4:52       ` [gentoo-dev] " Duncan
2011-04-20 18:44     ` [gentoo-dev] " Fabian Groffen
2011-04-21  2:31   ` Jeroen Roovers
2011-04-21  4:34     ` William Hubbs
2011-04-21 19:05       ` William Hubbs [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110421190505.GA12112@linux1 \
    --to=williamh@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox