Date: Tue, 17 Feb 2009 20:21:52 +0100 From: Ed Schouten <ed@80386.nl> To: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> Cc: Michael Butler <imb@protected-networks.net>, current@freebsd.org Subject: Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed Message-ID: <20090217192152.GI79178@hoeg.nl> In-Reply-To: <bb4a86c70902171107t1ff97a95h1bf67938dc675e8c@mail.gmail.com> References: <4999F7F9.4030204@elischer.org> <499A024A.60209@protected-networks.net> <20090217110524.GC79178@hoeg.nl> <499A9C9D.3000403@protected-networks.net> <20090217115651.GE79178@hoeg.nl> <bb4a86c70902170950u7ec9523fl4e39360b71b66d59@mail.gmail.com> <20090217175512.GG79178@hoeg.nl> <bb4a86c70902171003v1a85b077p923e4e0e3fa1436d@mail.gmail.com> <20090217182128.GH79178@hoeg.nl> <bb4a86c70902171107t1ff97a95h1bf67938dc675e8c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--WTEzZvM72OaERIi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Maksim Yevmenkin <maksim.yevmenkin@gmail.com> wrote: > anyway, i guess conversion to nmdm(4) is in order then. at least this > way users will have to change /dev/tty to /dev/nmdm which is possibly > less pain than other alternatives. while we are at it, we also could > implement your approach, i.e. auto-allocate and print /dev/nmdm node > if requested. But nmdm(4) is not really meant to be used for stuff like that, not that I think pts(4) should even be abused for this. The reason why pts(4) is used, is because the application tries to mimic a serial port of some sort on which data arrives that is normally handled by some kind of pppd. pts(4) doesn't have a lot of overhead in this setup. As you mentioned earlier, there is no need to use pts(4), because rfcomm_sppd also supports using stdout/stdin. This is a lot better, because our pipe implementation is probably a lot faster than pts(4). I'd rather see the handbook changed to not mention TTYs anywhere. --=20 Ed Schouten <ed@80386.nl> WWW: http://80386.nl/ --WTEzZvM72OaERIi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkmbDlAACgkQ52SDGA2eCwU2lQCeOVRHhDJe92KXaSqjTUOYi5jG SuQAniBRytJmBrHh0FutArlEOyUPh7ny =UA93 -----END PGP SIGNATURE----- --WTEzZvM72OaERIi0--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090217192152.GI79178>