public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: udev rule bluetooth.rules
Date: Sun, 5 Jul 2009 13:32:59 +0200	[thread overview]
Message-ID: <20090705133259.1bb7bad7@stoetzler> (raw)
In-Reply-To: <6AC5A55546F64545AE996F8200E3AC4E06CCC1A4@NL0105EXC01V01.eur.slb.com>

On Sun, 5 Jul 2009 12:24:34 +0200
John Frankish <j-frankish@slb.com> wrote:

> Ref bluez-4.43 /etc/udev/bluetooth.rules:
> 
> # Run helper every time a Bluetooth device appears
> # On remove actions, bluetoothd should go away by itself
> ACTION=="add", SUBSYSTEM=="bluetooth", RUN+="/usr/sbin/bluetoothd
> --udev"
> 
> Shouldn't this be of the format /etc/udev/rules.d/xx-bluetooth.rules
> so that it starts in the correct order - i.e. after dbus?

That's taken care of - if dbus is not available, bluetoothd will exit
with return code 1. udev will notice that and later start it again in
the coldplug run.
-- 
Stefan Seyfried
R&D Preload Department             |              "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."

This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2009-07-05 11:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-05 10:24 udev rule bluetooth.rules John Frankish
2009-07-05 11:32 ` Stefan Seyfried [this message]
2009-07-05 13:30   ` John Frankish
2009-07-06  6:48     ` John Frankish
2009-07-06 17:31       ` Marcel Holtmann
2009-07-07 12:36         ` Bastien Nocera
2009-07-08 18:26           ` Marcel Holtmann
2009-07-05 16:24 ` Marcel Holtmann
2009-07-05 17:11   ` Bastien Nocera
2009-07-05 17:12     ` Marcel Holtmann
2009-07-06  6:52       ` John Frankish

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=20090705133259.1bb7bad7@stoetzler \
    --to=seife@suse.de \
    --cc=linux-bluetooth@vger.kernel.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