Date: Thu, 15 May 2008 06:57:59 -0700 From: "Maksim Yevmenkin" <maksim.yevmenkin@gmail.com> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org> Subject: Re: cvs commit: src/usr.bin/bluetooth/rfcomm_sppd rfcomm_sppd.1 rfcomm_sppd.c Message-ID: <bb4a86c70805150657m23d90dcdp681f454b45c72ea@mail.gmail.com> In-Reply-To: <200805151814.14386.doconnor@gsoft.com.au> References: <200805141647.m4EGlUP1021019@repoman.freebsd.org> <200805151814.14386.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
[moving to freebsd-bluetooth@] On 5/15/08, Daniel O'Connor <doconnor@gsoft.com.au> wrote: > On Thu, 15 May 2008, Maksim Yevmenkin wrote: > > Modified files: > > usr.bin/bluetooth/rfcomm_sppd rfcomm_sppd.1 rfcomm_sppd.c > > Log: > > Make -t <tty> optional in server mode. If not specified use > > stdin/stdout. Document this. Do not require channel number in server > > mode. If not specified - bind to ''wildcard'' channel zero. Real > > channel number will be obtained automatically and registered with > > local sdpd(8). While I'm here fix serial port service registration. > > How hard would it be to have a '-t auto' and have it print out the pty > it just allocated? It would make it much easier for scripts to work if > that was possible. > > (Maybe just call openpty()?) not hard at all. however, how would rfcomm_sppd(1) print tty name if, say, it was asked to run in background? perhaps it would be better to teach rfcomm_sppd(1) to work with nmdm(4)? thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb4a86c70805150657m23d90dcdp681f454b45c72ea>