Date: Thu, 17 Apr 2008 10:39:16 -0700 From: "Maksim Yevmenkin" <maksim.yevmenkin@gmail.com> To: "Luigi Rizzo" <rizzo@iet.unipi.it> Cc: freebsd-bluetooth@freebsd.org Subject: Re: any reason to require -t dev in rfcomm_sppd -S ? Message-ID: <bb4a86c70804171039l2f85b360k3ae30e068fee5b83@mail.gmail.com> In-Reply-To: <20080417115631.GA72315@onelab2.iet.unipi.it> References: <20080417115631.GA72315@onelab2.iet.unipi.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Apr 17, 2008 at 4:56 AM, Luigi Rizzo <rizzo@iet.unipi.it> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb4a86c70804171039l2f85b360k3ae30e068fee5b83>