From: David Woodhouse <dwmw2@infradead.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] BlueZ GUI
Date: Sat, 18 Jun 2005 10:25:58 +0100 [thread overview]
Message-ID: <1119086759.24842.42.camel@localhost.localdomain> (raw)
In-Reply-To: <200505201554.12647.bluez-devel@schaettgen.de>
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 kdebluetooth
> doesn't include any tool to do that. It implements the client and server side
> of a some Bluetooth profiles, but it doesn't deal with the configuration.
> Except for the link key manager maybe. I don't really know the gnome
> bluetooth tools, but I guess it's the same there.
Only root can edit hcid.conf, and you shouldn't be using GUI
point-and-drool tools as root.
--
dwmw2
-------------------------------------------------------
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 9:25 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 [this message]
2005-06-18 13:00 ` Claudio Takahasi
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=1119086759.24842.42.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--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