From: Marcel Holtmann <marcel@holtmann.org>
To: Bastien Nocera <hadess@hadess.net>
Cc: John Frankish <j-frankish@slb.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: udev rule bluetooth.rules
Date: Sun, 05 Jul 2009 10:12:59 -0700 [thread overview]
Message-ID: <1246813979.12994.220.camel@localhost.localdomain> (raw)
In-Reply-To: <1246813882.2156.0.camel@snoogens.fab.redhat.com>
Hi Bastien,
> > > 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?
> > >
> > > Is it possible to have a udev rule check that dbus is running before executing?
> >
> > you are right. I should have fixed this. Just forgot about it. What
> > number prefix do we want for Bluetooth.
>
> You don't need the prefix. D-Bus isn't started through udev...
we don't need it, but we should be nice and add it anyway. I pushed a
fix for that. BlueZ being the only project not following conventions
here is a bad idea.
Regards
Marcel
next prev parent reply other threads:[~2009-07-05 17:12 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
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 [this message]
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=1246813979.12994.220.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=hadess@hadess.net \
--cc=j-frankish@slb.com \
--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