Date: Wed, 21 Mar 2012 13:18:36 +0300 From: Sergey Kandaurov <pluknet@freebsd.org> To: Ed Schouten <ed@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r233271 - in head/sys: amd64/conf arm/conf i386/conf ia64/conf mips/conf pc98/conf powerpc/conf sparc64/conf Message-ID: <CAE-mSOKYO=6ib=pVQzy5iiZgB3Znu6gVr7P=sr6Rov-WXY9yNQ@mail.gmail.com> In-Reply-To: <201203210838.q2L8chUM062260@svn.freebsd.org> References: <201203210838.q2L8chUM062260@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 March 2012 12:38, Ed Schouten <ed@freebsd.org> wrote: > Author: ed > Date: Wed Mar 21 08:38:42 2012 > New Revision: 233271 > URL: http://svn.freebsd.org/changeset/base/233271 > > Log: > =A0Remove pty(4) from our kernel configurations. > > =A0As of FreeBSD 8, this driver should not be used. Applications that use > =A0posix_openpt(2) and openpty(3) use the pts(4) that is built into the > =A0kernel unconditionally. If it turns out high profile depend on the > =A0pty(4) module anyway, I'd rather get those fixed. So please report any > =A0issues to me. > > =A0The pty(4) module is still available as a kernel module of course, so = a > =A0simple `kldload pty' can be used to run old-style pseudo-terminals. Will this affect old binaries like misc/mc build for e.g. 6.x running on GE= NERIC w/o kldoaded pty(4), so that I will have to `kldload pty'? Currently executing old mc results in emitting the following kernel message= : pid 11948 (mc) is using legacy pty devices - not logging anymore --=20 wbr, pluknet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE-mSOKYO=6ib=pVQzy5iiZgB3Znu6gVr7P=sr6Rov-WXY9yNQ>