From: Marcel Holtmann <marcel@holtmann.org>
To: Fredrik Noring <noring@nocrew.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcid hotplug initialisation?
Date: Mon, 09 Feb 2004 12:20:35 +0100 [thread overview]
Message-ID: <1076325635.6869.128.camel@pegasus> (raw)
In-Reply-To: <1076324203.5263.47.camel@kalkyl.roxen.com>
Hi Fredrik,
> > no. The bluetooth.agent is only for device specific configuration and
> > not for starting a deamon. However hcid watches all interfaces and
> > bluetooth.agent would be called for every device.
>
> Having hcid actively running on a system that never will use a
> Bluetooth device is waste of resources. But when a user inserts
> a Bluetooth device, it would be excellent to have it all work
> automtically. What do you suggest then?
but you expect that the user has installed the Bluetooth specific
software? If the software is installed we start all needed parts of the
Bluetooth subsystem. If they don't want them they shouldn't install
their software.
To make everything work perfect on the first use of a Bluetooth dongle
is not the job of the Bluetooth subsystem. If the USB or PCMCIA subsytem
detects a Bluetooth device it has to install, start or run whatever
other action is needed to make it work.
> > Multiple running hcid's will mess up the security manager.
>
> Yes, but only one hcid instance would run. The hotplug script and/or
> hcid can check this.
If hcid is not running, because no device is attached. How would you
manage you pairings through D-Bus for example? For some stuff an
attached device is not needed.
If you think the long way then after hcid comes sdpd. This daemon must
be started first, before any PAN service can be started. Starting all
daemons from bluetooth.agent is stupid, because none of them actually
are bound to a specific device. And people also reported that starting
daemons from bluetooth.agent causes troubles.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-02-09 11:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 10:40 [Bluez-devel] hcid hotplug initialisation? Fredrik Noring
2004-02-09 10:47 ` Marcel Holtmann
2004-02-09 10:56 ` Fredrik Noring
2004-02-09 11:20 ` Marcel Holtmann [this message]
2004-02-09 12:35 ` Fredrik Noring
2004-02-09 12:50 ` Marcel Holtmann
2004-02-09 13:06 ` Fredrik Noring
2004-02-09 15:34 ` 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=1076325635.6869.128.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=noring@nocrew.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.