Date: Tue, 17 Feb 2009 19:21:28 +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: <20090217182128.GH79178@hoeg.nl> In-Reply-To: <bb4a86c70902171003v1a85b077p923e4e0e3fa1436d@mail.gmail.com> References: <20080526110543.J26343@fledge.watson.org> <alpine.BSF.2.00.0902161233440.5806@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> <bb4a86c70902170950u7ec9523fl4e39360b71b66d59@mail.gmail.com> <20090217175512.GG79178@hoeg.nl> <bb4a86c70902171003v1a85b077p923e4e0e3fa1436d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--l4IMblsHEWQg+b+m Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Maksim, * Maksim Yevmenkin <maksim.yevmenkin@gmail.com> wrote: > On Tue, Feb 17, 2009 at 9:55 AM, Ed Schouten <ed@80386.nl> wrote: > > * Maksim Yevmenkin <maksim.yevmenkin@gmail.com> 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 <ed@80386.nl> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090217182128.GH79178>