From: Stefan Seyfried <seife@suse.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Should hcid wait for dbus daemon?
Date: Tue, 9 Jan 2007 09:27:09 +0100 [thread overview]
Message-ID: <20070109082709.GB5956@suse.de> (raw)
In-Reply-To: <878xgd3xkv.fsf@tora.pca.it>
Hi Luca,
On Tue, Jan 09, 2007 at 12:31:12AM +0100, Luca Capello wrote:
> NB, I'm not deeply involved in bluetooth neither dbus development,
> just a "power user". If my thoughts are wrong, just discard them.
They are not wrong, it is just a different use case :-)
> Shouldn't be the contrary? I mean, on a clean Debian etch, every
> dbus-dependent service is started by dbus:
=
> root@gismo:/home/luca# invoke-rc.d dbus start
> Starting system message bus: dbus.
> Starting Hardware abstraction layer: hald.
> Starting DHCP D-Bus daemon: dhcdbd.
> Starting network connection manager: NetworkManager.
> Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
> Starting network events dispatcher: NetworkManagerDispatcher.
> =
> root@gismo:/home/luca#
This is about the same if i statically enable the bluetooth service
on a SUSE machine. But i would like to avoid that (no need to run
hcid on a machine that will never see a BT device). At the same time,
i like to have it "just work", without the user needing to configure
it. So i start the bluetooth services via udev, when a BT device
is connected.
This works very well once the machine is up and running. If the device
is connected during boot, it is different, because the udev "coldplug"
happens before most of the services are started.
I hope this clears up my (and Daniels) intentions :-)
Have fun
-- =
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-01-09 8:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 17:37 [Bluez-devel] Should hcid wait for dbus daemon? Daniel Gollub
2007-01-08 18:47 ` Johan Hedberg
2007-01-08 23:31 ` Luca Capello
2007-01-09 0:01 ` Daniel Gollub
2007-01-09 8:27 ` Stefan Seyfried [this message]
2007-01-08 23:41 ` Daniel Gollub
2007-01-12 15:25 ` Stefan Seyfried
2007-01-13 17:39 ` Andrey Rahmatullin
2007-01-15 13:30 ` Marcel Holtmann
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=20070109082709.GB5956@suse.de \
--to=seife@suse.de \
--cc=bluez-devel@lists.sourceforge.net \
/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