From owner-freebsd-current@FreeBSD.ORG Thu Feb 19 07:29:38 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 8BFB2106566B for ; Thu, 19 Feb 2009 07:29:38 +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 4B8598FC13 for ; Thu, 19 Feb 2009 07:29:38 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id A47731D2C2; Thu, 19 Feb 2009 08:29:37 +0100 (CET) Date: Thu, 19 Feb 2009 08:29:37 +0100 From: Ed Schouten To: Bruce Simpson Message-ID: <20090219072937.GB19161@hoeg.nl> References: <20090217110524.GC79178@hoeg.nl> <499A9C9D.3000403@protected-networks.net> <20090217115651.GE79178@hoeg.nl> <20090217175512.GG79178@hoeg.nl> <20090217182128.GH79178@hoeg.nl> <20090217192152.GI79178@hoeg.nl> <499C7992.7000705@incunabulum.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XOIedfhf+7KOe/yw" Content-Disposition: inline In-Reply-To: <499C7992.7000705@incunabulum.net> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: Michael Butler , current@freebsd.org, Maksim Yevmenkin 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: Thu, 19 Feb 2009 07:29:38 -0000 --XOIedfhf+7KOe/yw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Bruce, * Bruce Simpson wrote: > Maksim seems to be talking about the use case where folk are actually= =20 > doing straight serial over RFCOMM and need to tie it down to a known tty,= =20 > though. Ah, that's indeed something I didn't know. Well, in that case we still need pseudo-terminals. > Surely there must be a way to tie rfcomm_sppd down to a specific pts = =20 > number, or failing that, teach it to report the pts which it got=20 > allocated? Well, with MPSAFE TTY the only way pseudo-terminals should be allocated, is by calling posix_openpt(). The device name is determined by a simple unrhdr (alloc_unr(9)). There is no actual way to influence the naming, so I guess we should make rfcomm_sppd just use a random device name. We could maybe solve this by creating a symlink to the TTY? --=20 Ed Schouten WWW: http://80386.nl/ --XOIedfhf+7KOe/yw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkmdCmEACgkQ52SDGA2eCwVpKgCfQ2W+Ob+vFdeJZB7jPhfjldU3 H8UAn3J8/WFrsvQTeBuB6PhquuIYKJsd =vh40 -----END PGP SIGNATURE----- --XOIedfhf+7KOe/yw--