From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] BlueZ GUI
Date: Sat, 18 Jun 2005 06:00:23 -0700 [thread overview]
Message-ID: <e1effdeb05061806001b5d8a3a@mail.gmail.com> (raw)
In-Reply-To: <1119086759.24842.42.camel@localhost.localdomain>
I folks,
I am working with D-Bus services for BlueZ and I had an
approach to suggest. Using D-Bus it is possible start
an application and define message rules and handle
security issues.
An important comment, D-Bus can address concurrent
requests(connection, inquiry, service search), signals can be
sent to notify disconnection, new devices, ...
Currently, some patchs for PAN Daemon(pand) D-Bus service
were submited to the community. I don't know when it will be
available, probably in the next release.
Another approach is develop an library/functions to export
the daemons functionality: connect, disconnect, search, ...
Regards,
Claudio
On 6/18/05, David Woodhouse <dwmw2@infradead.org> wrote:
> On Fri, 2005-05-20 at 15:54 +0200, Fred Schaettgen wrote:
> > I guess he's talking about a GUI to edit hcid.conf. At least kdebluetoo=
th
> > doesn't include any tool to do that. It implements the client and serve=
r side
> > of a some Bluetooth profiles, but it doesn't deal with the configuratio=
n.
> > Except for the link key manager maybe. I don't really know the gnome
> > bluetooth tools, but I guess it's the same there.
>=20
> Only root can edit hcid.conf, and you shouldn't be using GUI
> point-and-drool tools as root.
>=20
> --
> dwmw2
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclic=
k
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-06-18 13:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 8:20 [Bluez-devel] BlueZ GUI Mayank Batra
2005-05-20 8:25 ` Marcel Holtmann
2005-05-20 10:05 ` blookk -
2005-05-20 13:54 ` Fred Schaettgen
2005-06-18 9:25 ` David Woodhouse
2005-06-18 13:00 ` Claudio Takahasi [this message]
2005-05-23 9:41 ` blookk -
-- strict thread matches above, loose matches on Subject: below --
2005-05-23 11:41 Mayank Batra
2005-05-23 12:20 ` blookk -
2005-05-15 12:29 Mayank Batra
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=e1effdeb05061806001b5d8a3a@mail.gmail.com \
--to=cktakahasi@gmail.com \
--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