From owner-freebsd-current@FreeBSD.ORG Tue Feb 17 19:21:54 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12DD01065672 for ; Tue, 17 Feb 2009 19:21:54 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id C4A0B8FC21 for ; Tue, 17 Feb 2009 19:21:53 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id BDBE51CC77; Tue, 17 Feb 2009 20:21:52 +0100 (CET) Date: Tue, 17 Feb 2009 20:21:52 +0100 From: Ed Schouten To: Maksim Yevmenkin Message-ID: <20090217192152.GI79178@hoeg.nl> References: <4999F7F9.4030204@elischer.org> <499A024A.60209@protected-networks.net> <20090217110524.GC79178@hoeg.nl> <499A9C9D.3000403@protected-networks.net> <20090217115651.GE79178@hoeg.nl> <20090217175512.GG79178@hoeg.nl> <20090217182128.GH79178@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WTEzZvM72OaERIi0" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Cc: Michael Butler , current@freebsd.org Subject: Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2009 19:21:54 -0000 --WTEzZvM72OaERIi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Maksim Yevmenkin 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 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--