From: Fredrik Noring <noring@nocrew.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcid hotplug initialisation?
Date: Mon, 09 Feb 2004 13:35:14 +0100 [thread overview]
Message-ID: <1076330114.5263.85.camel@kalkyl.roxen.com> (raw)
In-Reply-To: <1076325635.6869.128.camel@pegasus>
Marcel,
mån 2004-02-09 klockan 12.20 skrev Marcel Holtmann:
> but you expect that the user has installed the Bluetooth specific
> software?
Yes, it could be installed by default. A few megs of harddisk space
is hardly an issue compared with having a handful of strange daemons
(hcid, stpd etc.) always running no matter if any Bluetooth devices
are actually available or not, is it?
> 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.
Starting these services on demand is more efficient and simpler for
the user. Perhaps 1 % of all users will try to use the Bluetooth stuff.
> 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.
This would require that hcid is compatible with that approach. That's
the issue here. :)
> 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.
The hotplug may not be the only way to start hcid. Other services
may require it to start too, of course.
> If you think the long way then after hcid comes sdpd. This daemon must
> be started first, before any PAN service can be started.
This kind of dependency needs to be tracked too.
Fredrik
next prev parent reply other threads:[~2004-02-09 12:35 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
2004-02-09 12:35 ` Fredrik Noring [this message]
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=1076330114.5263.85.camel@kalkyl.roxen.com \
--to=noring@nocrew.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.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