public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Stefan Seyfried <seife@suse.de>
Cc: linux-bluetooth@vger.kernel.org,
	Bastien Nocera <hadess@hadess.net>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: Packaging question
Date: Thu, 18 Sep 2008 19:16:20 +0200	[thread overview]
Message-ID: <1221758180.6782.22.camel@californication> (raw)
In-Reply-To: <48D22F30.1060301@suse.de>

Hi Marcel,

> Another question, also related to packaging:
> 
> How should the bluetoothd be started nowadays?
> 
> dbus-activation with a service-file like this one?
> root@stoetzler:~# cat /usr/share/dbus-1/system-services/org.bluez.service
> [D-BUS Service]
> Name=org.bluez
> Exec=/etc/init.d/bluetooth start
> User=root
> 
> But then, who will start it before XDM fires up? Has anybody already hacked up
> a nice way to just start it on adapter hotplug? Some HAL magic maybe?
> 
> I had that old udev rule hack that would call the init script at adapter
> plugin, but that's ugly and racy (because it typically starts before DBus is
> started).
> 
> Any innovative ideas?

we had the discussion for Fedora and we want to start it via udev,
however then we need D-Bus before udev runs and that is not an option
right now. So the current solution is to just do it via init.d, but in
the future we want udev. The D-Bus service activation is nice, but makes
problems when you wanna use the mouse and keyboard early.

Regards

Marcel



  reply	other threads:[~2008-09-18 17:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09 14:19 Packaging question Stefan Seyfried
2008-09-10 22:15 ` Marcel Holtmann
2008-09-11  8:40   ` Stefan Seyfried
2008-09-12 16:34     ` Marcel Holtmann
2008-09-18 10:36       ` Stefan Seyfried
2008-09-18 17:16         ` Marcel Holtmann [this message]
2008-09-18 17:40           ` Stefan Seyfried
2008-09-18 20:39             ` Marcel Holtmann
2008-09-23 18:46               ` Stefan Seyfried

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=1221758180.6782.22.camel@californication \
    --to=marcel@holtmann.org \
    --cc=dwmw2@infradead.org \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=seife@suse.de \
    /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