From owner-freebsd-bluetooth@FreeBSD.ORG Sat Dec 3 21:33:42 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B52916A420 for ; Sat, 3 Dec 2005 21:33:42 +0000 (GMT) (envelope-from shackan@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9DB643D7E for ; Sat, 3 Dec 2005 21:33:36 +0000 (GMT) (envelope-from shackan@gmail.com) Received: by wproxy.gmail.com with SMTP id i6so565166wra for ; Sat, 03 Dec 2005 13:33:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=diYLHKsNNpovnM5wWduN/Y7a/LGeV4o++Z+knAn/PCd3AAlqozxTEGUsCKDhInAzBBx7jXE9ZnKKOtZDycY9qY2t4du0rLzcYpirZ7wV4BdfSUJXyjBboQlG1JhJ33zgeHi2M4JHKAToctKnx1MLZkOOmEWU7oWkvFFTDspREo8= Received: by 10.64.91.2 with SMTP id o2mr2128909qbb; Sat, 03 Dec 2005 13:33:32 -0800 (PST) Received: by 10.65.196.7 with HTTP; Sat, 3 Dec 2005 13:33:32 -0800 (PST) Message-ID: <9307f5f20512031333x61e9d141u85ea578711740712@mail.gmail.com> Date: Sat, 3 Dec 2005 13:33:32 -0800 From: "P. Durante" To: Maksim Yevmenkin In-Reply-To: <4391E320.2090006@savvis.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <9307f5f20512030807x6eadc73cq9d9acc9dd5503a5b@mail.gmail.com> <4391E320.2090006@savvis.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: Automatic bluetooth device initialization X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Dec 2005 21:33:42 -0000 hi maksim, thanks for the quick answer > fine. if you could please tell us a little bit more and explain what is > wrong with the current way of doing things in linux and/or freebsd. don't get me wrong, there isn't anything wrong with the current state of bluetooth configuration utilities. If you've spent some time reading the freebsd handbook or some unofficial bluez tutorials and you're accustomed to the command line (like most of the people on this list, I assume) then you're just set.. ..but if you take into account the regular desktop user (like how linux and freebsd are trying to do right now) you see the need for something more intuitive and immediate than the 'current way of doing things', this basically involves some sort of user interface, at the very least. Even on this mailing list, little time ago, there was a request about porting the excellent kde bluetooth framework to freebsd, but, as you noted, in it's current form kdebluetooth has very deep roots in bluez, and it also has deep roots in KDE, so even adapting to another desktop manager would be difficult. To solve such (not uncommon) problems, the dbus system[=B9] is being developed, dbus is getting very popular (maybe too much) and it provides a simple and secure messaging system to let different programs talk to one another, in our example, let one program be the bluetooth daemon, it provides a well-known interface and hides platform-specific implementation details, on the other side we have the other programs, which are just frontends (with a Qt/Gtk/textual interface, it doesn't matter) and can run on every operating system where the aforementioned interface is available, I think something like this wouldn't hurt to any "desktop-unix" operating system. [=B9] http://www.freedesktop.org/wiki/Software_2fdbus > freebsd uses different approach. basically there is a devctl(4) driver > and devd(8) daemon. whenever a device is added to or removed from the > device tree, devd(8) will execute actions specified in its configuration > file. I'm looking at them right now, thanks again. regards, Paul