From owner-freebsd-bluetooth@FreeBSD.ORG Thu Apr 17 17:39:22 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 057C1106566B for ; Thu, 17 Apr 2008 17:39:22 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id 138F78FC14 for ; Thu, 17 Apr 2008 17:39:19 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so134572fgg.35 for ; Thu, 17 Apr 2008 10:39:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=n7+SAvqB3gGBp63VX8TfjeId/OBd/lxDb1EMH6EGCUk=; b=HlFSKRYrvkD3Akvzdh9+YVA4GGrEGi05Z8V9asRHaq/7mx/82i0Xzn+B13ICCVgN6F2MoHG8tOchLYIJtrAvatsODbdHXge+/v9eClxRjjuW/9RYqJUy2YioyRSMm/26NdA+59BkSEOGOIypa2nyAXhalwOCjyGqzfeksWbPYlg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Cdtb5ccpilbagiCY6CiVyG03bhx3cLWjgTN+nJaqnB4CGCHAeKORJgyn3aesFeDTq7ZgmvjURmfbG9B1FNAyclCmAoVAfMC2qWgTrpqZ5pBo0sdl/WiyT4SBpjtUvnQP2lTBCCTp+6FWZXLOkolDDGkfxgzPhU7+PXcBE9RtrHw= Received: by 10.86.59.2 with SMTP id h2mr3192288fga.19.1208453956377; Thu, 17 Apr 2008 10:39:16 -0700 (PDT) Received: by 10.86.71.15 with HTTP; Thu, 17 Apr 2008 10:39:16 -0700 (PDT) Message-ID: Date: Thu, 17 Apr 2008 10:39:16 -0700 From: "Maksim Yevmenkin" To: "Luigi Rizzo" In-Reply-To: <20080417115631.GA72315@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080417115631.GA72315@onelab2.iet.unipi.it> Cc: freebsd-bluetooth@freebsd.org Subject: Re: 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 17:39:22 -0000 On Thu, Apr 17, 2008 at 4:56 AM, Luigi Rizzo wrote: > hi, is there any compelling reason to require > the '-t device' option in rfcomm_sppd when used in server mode ? technically, no. just need to be careful who is going to setup tty properly, for example make it 'raw' as rfcomm_sppd(1) does with pty. rfcomm_sppd(1) already can be used inside ppp(8), i.e. one can do something like set device '!/usr/bin/rfcomm_sppd -a mobile -c sp' in /etc/ppp.conf and it will work just fine. rfcomm_sppd(1) does not do anything to tty when running using stdin/stdout in client mode. the assumption here is that whatever calls rfcomm_sppd(1) will setup tty/fd properly. > 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. right. can you please provide usage example? i certainly would not object to making the change you are requesting. thanks, max