From owner-freebsd-current@FreeBSD.ORG Tue Feb 17 18:21:29 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 32106106570B for ; Tue, 17 Feb 2009 18:21:29 +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 E32718FC1B for ; Tue, 17 Feb 2009 18:21:28 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 462A41CC77; Tue, 17 Feb 2009 19:21:28 +0100 (CET) Date: Tue, 17 Feb 2009 19:21:28 +0100 From: Ed Schouten To: Maksim Yevmenkin Message-ID: <20090217182128.GH79178@hoeg.nl> References: <20080526110543.J26343@fledge.watson.org> <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> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="l4IMblsHEWQg+b+m" 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 18:21:29 -0000 --l4IMblsHEWQg+b+m Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Maksim, * Maksim Yevmenkin wrote: > On Tue, Feb 17, 2009 at 9:55 AM, Ed Schouten wrote: > > * Maksim Yevmenkin wrote: > >> so, for now, i think we should keep rfcomm_sppd(1) as it is. if this > >> is not an option (with new tty subsystem) then we should convert it to > >> use nmdm(4) or something similar. > > > > Well, the problem with the current approach is that if you remove > > "device pty" from your kernel config, it won't work. With MPSAFE TTY we > > switched to Unix98-style pseudo-terminals, so the preferred mechanism is > > to call posix_openpt() (or open /dev/ptmx) and use ptsname() to > > determine which character device to use. >=20 > is there a way allocate tty with a given name under "new world order"? No, there isn't. I have been thinking about this. Allowing pseudo-terminals to be allocated with a certain name would allow us to do things like implementing device drivers as a daemon in userspace. > > I won't change anything now, but will keep my patch at the before > > mentioned URL. >=20 > like i said, the only problem i have here is that any rfcomm_sppd > callers will have to do extra work to figure which tty was allocated. > that is the biggest difference from user's point of view. Well, we already have existing tools that use such an approach as well, like mdmconfig. They print a name of the md device to stdout. I'm not saying I'm 100% happy with this approach, but it's more correct than just reserving a certain pseudo-terminal device name. --=20 Ed Schouten WWW: http://80386.nl/ --l4IMblsHEWQg+b+m Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkmbACgACgkQ52SDGA2eCwWTTACfXyZ95/Y4f84feVDt96jZlivr BUQAn3l+NJ4CGRD1La8q35CdhqUG0+at =8dvc -----END PGP SIGNATURE----- --l4IMblsHEWQg+b+m--