Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Mar 2012 11:32:53 +0100
From:      Dimitry Andric <dim@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:  <4F6DA2D5.1090301@FreeBSD.org>
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 2012-03-21 09:38, Ed Schouten wrote:
> Author: ed
> Date: Wed Mar 21 08:38:42 2012
> New Revision: 233271
> URL: http://svn.freebsd.org/changeset/base/233271
> 
> Log:
>   Remove pty(4) from our kernel configurations.
>   
>   As of FreeBSD 8, this driver should not be used. Applications that use
>   posix_openpt(2) and openpty(3) use the pts(4) that is built into the
>   kernel unconditionally. If it turns out high profile depend on the
>   pty(4) module anyway, I'd rather get those fixed. So please report any
>   issues to me.
>   
>   The pty(4) module is still available as a kernel module of course, so a
>   simple `kldload pty' can be used to run old-style pseudo-terminals.

Please put at least a note in UPDATING... :)  I just ran into an old
program (compiled for FreeBSD 6 I think), that suddenly started failing
with 'Cannot allocate master pty'.

Maybe the compat ports could be updated to also enable loading of the
pty module?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F6DA2D5.1090301>