From owner-freebsd-bluetooth@FreeBSD.ORG Sun Mar 12 21:18:16 2006 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 A86FC16A400 for ; Sun, 12 Mar 2006 21:18:14 +0000 (GMT) (envelope-from plunky@rya-online.net) Received: from mail10.svc.cra.dublin.eircom.net (mail10.svc.cra.dublin.eircom.net [159.134.118.26]) by mx1.FreeBSD.org (Postfix) with SMTP id 0A77143D46 for ; Sun, 12 Mar 2006 21:18:13 +0000 (GMT) (envelope-from plunky@rya-online.net) Received: (qmail 75621 messnum 6681062 invoked from network[159.134.177.180/159-134-177-180.as1.cra.dublin.eircom.net]); 12 Mar 2006 21:18:08 -0000 Received: from 159-134-177-180.as1.cra.dublin.eircom.net (HELO rya-online.net) (159.134.177.180) by mail10.svc.cra.dublin.eircom.net (qp 75621) with SMTP; 12 Mar 2006 21:18:08 -0000 Received: (nullmailer pid 6752 invoked by uid 1000); Sun, 12 Mar 2006 20:29:25 -0000 Date: Sun, 12 Mar 2006 20:29:25 +0000 (GMT) To: Maksim Yevmenkin In-Reply-To: <44107678.1080206@savvis.net> References: <1141918855.418446.1437.nullmailer@galant.ukfsn.org> <44107678.1080206@savvis.net> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-893933849-1142195365=:6674" Message-Id: <1142195365.759631.5369.nullmailer@galant.ukfsn.org> From: Iain Hibbert Cc: freebsd-bluetooth@freebsd.org Subject: Re: config files 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: Sun, 12 Mar 2006 21:18:16 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-893933849-1142195365=:6674 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 9 Mar 2006, Maksim Yevmenkin wrote: > i do not like this idea. having one huge config file for every possible > bluetooth application seems like a bad thing to me. i agree, parser code can > be moved in libbluetooth (or whatever), but config files should stay separate. well, yes - one massive file could be bad though not sure how many remote bluetooth devices would be in it anyway? Its just that to add a mouse to the system, I needed to enter details in 3 files (and, details are held in two more) which could be considered a bit much just for a mouse :) vaguely related to this, would the attached patch work to reload bthidd.conf on SIGHUP? It seems that it should, though I'm not sure if the fact that the new_device field is set would be an issue (maybe not, if the session already exists?) iain --0-893933849-1142195365=:6674 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=xx Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: bthidd.c reload config file patch Content-Disposition: attachment; filename=xx LS0tIGJ0aGlkZC5jLm9yaWcJMjAwNC0xMS0xOCAxODowNToxNS4wMDAwMDAw MDAgKzAwMDANCisrKyBidGhpZGQuYwkyMDA2LTAzLTEyIDIwOjEwOjAyLjAw MDAwMDAwMCArMDAwMA0KQEAgLTU1LDcgKzU1LDggQEANCiAgKiBidGhpZGQN CiAgKi8NCiANCi1zdGF0aWMgaW50CWRvbmUgPSAwOyAvKiBhcmUgd2UgZG9u ZT8gKi8NCitzdGF0aWMgaW50CWRvbmUgPSAwOwkvKiBhcmUgd2UgZG9uZT8g Ki8NCitzdGF0aWMgaW50CXJlbG9hZCA9IDA7CS8qIHJlbG9hZCBjb25maWcg ZmlsZSAqLw0KIA0KIGludA0KIG1haW4oaW50IGFyZ2MsIGNoYXIgKmFyZ3Zb XSkNCkBAIC0xNjksNiArMTcwLDExIEBADQogDQogCQlpZiAoc2VydmVyX2Rv KCZzcnYpIDwgMCkNCiAJCQlicmVhazsNCisNCisJCWlmIChyZWxvYWQgJiYg cmVhZF9jb25maWdfZmlsZSgpIDwgMCkNCisJCQlicmVhazsNCisNCisJCXJl bG9hZCA9IDA7DQogCX0NCiANCiAJc2VydmVyX3NodXRkb3duKCZzcnYpOw0K QEAgLTI0OSw2ICsyNTUsOSBAQA0KIHsNCiAJc3lzbG9nKExPR19OT1RJQ0Us ICJHb3Qgc2lnbmFsICVkLCB0b3RhbCBudW1iZXIgb2Ygc2lnbmFscyAlZCIs DQogCQlzLCArKyBkb25lKTsNCisNCisJaWYgKHMgPT0gU0lHSFVQKQ0KKwkJ cmVsb2FkID0gMTsNCiB9DQogDQogLyoNCg== --0-893933849-1142195365=:6674--