From owner-freebsd-current@FreeBSD.ORG Tue Dec 2 18:57:20 2008 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 0DA1D1065678 for ; Tue, 2 Dec 2008 18:57:20 +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 A0AB48FC12 for ; Tue, 2 Dec 2008 18:57:19 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 0DBEA1CE1F; Tue, 2 Dec 2008 19:57:19 +0100 (CET) Date: Tue, 2 Dec 2008 19:57:19 +0100 From: Ed Schouten To: Olivier SMEDTS Message-ID: <20081202185719.GR64969@hoeg.nl> References: <367b2c980812021023s3c9f005dwf8092cb56d56db2c@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bn6XL8m8Y51x7rzV" Content-Disposition: inline In-Reply-To: <367b2c980812021023s3c9f005dwf8092cb56d56db2c@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: current@freebsd.org Subject: Re: COMPAT_43TTY and MPSAFE tty 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, 02 Dec 2008 18:57:20 -0000 --bn6XL8m8Y51x7rzV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello Olivier, * Olivier SMEDTS wrote: > Is it safe to run a kernel without options COMPAT_43TTY since the new > MPSAFE tty layer was introduced ? > I removed it from my kernel config file since few days and didn't > notice any change... > I use nearly latest -CURRENT on amd64 and never tried removing this > option before because of the big "KEEP THIS!". Now I don't use any > COMPAT_* option. If you compiled your applications after June 14, everything should just work (not taking binary-only applications into account). Even if you did not, there is a slim chance your application depends on COMPAT_43TTY. COMPAT_43TTY only introduces some binary-only compatibility interfaces (ioctls) for applications that used . I already removed before I imported MPSAFE TTY: http://www.freebsd.org/cgi/cvsweb.cgi/src/include/Attic/sgtty.h I guess we'd better keep COMPAT_43TTY in our stock kernel configuration files for another couple of years, but maybe we should already remove the "[KEEP THIS!]" message. It's also possible to remove "device pty" from your kernel configuration file. If you remove this line, you can only allocate pts(4)-style pseudo-terminals (/dev/pts/...). This means you cannot allocate any pseudo-terminals inside a FreeBSD 4/5/6/7 jail. I guess we should keep "device pty" a little longer than COMPAT_43TTY, because recompiling applications won't migrate the offending ones to pts(4). --=20 Ed Schouten WWW: http://80386.nl/ --bn6XL8m8Y51x7rzV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkk1hQ4ACgkQ52SDGA2eCwUjSgCeIHzCPWipUzsN8UZm/mAV9oKH UykAniXr5OtgQI/Ej5dDvXAqiWrkJ9zX =dKLo -----END PGP SIGNATURE----- --bn6XL8m8Y51x7rzV--