From owner-freebsd-bluetooth@FreeBSD.ORG Thu Apr 17 12:12:05 2008 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF1531065672 for ; Thu, 17 Apr 2008 12:12:05 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.9.129]) by mx1.freebsd.org (Postfix) with ESMTP id 99C308FC1E for ; Thu, 17 Apr 2008 12:12:05 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 49DF87318D; Thu, 17 Apr 2008 13:56:31 +0200 (CEST) Date: Thu, 17 Apr 2008 13:56:31 +0200 From: Luigi Rizzo To: freebsd-bluetooth@freebsd.org Message-ID: <20080417115631.GA72315@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: any reason to require -t dev in rfcomm_sppd -S ? 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: Thu, 17 Apr 2008 12:12:05 -0000 hi, is there any compelling reason to require the '-t device' option in rfcomm_sppd when used in server mode ? I tried to disable the one-line that checks it in the code, and things seem to work - and this makes the program very convenient to use in a pipeline, e.g. to receive data from a remote bluetooth device. cheers luigi