any reason to require -t dev in rfcomm_sppd -S ?

[Maksim Yevmenkin]

On Thu, Apr 17, 2008 at 4:56 AM, Luigi Rizzo <rizzo at 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