From: Luca Capello <luca@pca.it>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Should hcid wait for dbus daemon?
Date: Tue, 09 Jan 2007 00:31:12 +0100 [thread overview]
Message-ID: <878xgd3xkv.fsf@tora.pca.it> (raw)
In-Reply-To: 20070108184701.GA12689@jh-mbp
[-- Attachment #1.1: Type: text/plain, Size: 1380 bytes --]
Hello!
NB, I'm not deeply involved in bluetooth neither dbus development,
just a "power user". If my thoughts are wrong, just discard them.
On Mon, 08 Jan 2007 19:47:01 +0100, Johan Hedberg wrote:
> On Mon, Jan 08, 2007, Daniel Gollub wrote:
>> If the hcid would wait for the dbus daemon this wouldn't be a
>> problem. At least hcid can handle a dbus daemon restart, maybe we
>> can enhance this.
>
> Sounds like a useful feature.
Shouldn't be the contrary? I mean, on a clean Debian etch, every
dbus-dependent service is started by dbus:
=====
root@gismo:/home/luca# ls -l /etc/dbus-1/eventd.d/
total 16
-rwxr-xr-x 1 root root 1901 2006-11-11 15:38 20hal
-rwxr-xr-x 1 root root 1091 2006-10-24 15:22 24dhcdbd
lrwxrwxrwx 1 root root 25 2007-01-07 21:53 25avahi-daemon -> \
../../init.d/avahi-daemon
-rwxr-xr-x 1 root root 1766 2006-11-30 22:22 25NetworkManager
-rwxr-xr-x 1 root root 1684 2006-11-30 22:22 26NetworkManagerDispatcher
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#
=====
Just my 0.02€...
Thx, bye,
Gismo / Luca
[-- Attachment #1.2: Type: application/pgp-signature, Size: 188 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
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=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
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-08 23:31 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 [this message]
2007-01-09 0:01 ` Daniel Gollub
2007-01-09 8:27 ` Stefan Seyfried
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=878xgd3xkv.fsf@tora.pca.it \
--to=luca@pca.it \
--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