From owner-freebsd-current@FreeBSD.ORG Thu Jun 15 21:04:47 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FF1516A4C1; Thu, 15 Jun 2006 21:04:47 +0000 (UTC) (envelope-from freebsd@alaskaparadise.com) Received: from stargate.alaskaparadise.com (114-103-74-65.gci.net [65.74.103.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F85943D5D; Thu, 15 Jun 2006 21:04:45 +0000 (GMT) (envelope-from freebsd@alaskaparadise.com) Received: by stargate.alaskaparadise.com (Postfix, from userid 0) id 9A24240D0; Thu, 15 Jun 2006 13:04:44 -0800 (AKDT) From: Beech Rintoul Organization: Alaska Paradise To: freebsd-current@freebsd.org User-Agent: KMail/1.9.1 References: <3223.1150403817@critter.freebsd.dk> In-Reply-To: <3223.1150403817@critter.freebsd.dk> MIME-Version: 1.0 Date: Thu, 15 Jun 2006 13:04:22 -0800 Content-Type: multipart/signed; boundary="nextPart3152729.fiyboQAPv3"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200606151304.42724.freebsd@alaskaparadise.com> Cc: Mike Jakubik , Poul-Henning Kamp , current@freebsd.org, Alexander Leidinger Subject: Re: HEADS-UP: removed COMPAT_43 from GENERIC (and other configs) 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: Thu, 15 Jun 2006 21:04:47 -0000 --nextPart3152729.fiyboQAPv3 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 15 June 2006 12:36, Poul-Henning Kamp wrote: > In message <4491C2F0.6000007@rogers.com>, Mike Jakubik writes: > >What about COMPAT_43TTY? Is this still needed, how exactly does it > >affect the system? > > It adds a bunch of ancient-compatible ioctls to the kernel. > > It is, as a principle, not needed, but thanks to the many variants > of "sh configure" employed in usr/ports, a quite large number of > ports go "Ohh, this is BSD, I'd better use the old ioctls" and > break if you don't offer them. Is there a way to easily identify these ports? I've had both lines commente= d=20 out of my kernel configs for some time and haven't seen any port breakage o= n=20 either 6.x or -current. Beech =2D-=20 =2D------------------------------------------------------------------------= =2D------------- Beech Rintoul - Sys. Administrator - beech@alaskaparadise.com /"\ ASCII Ribbon Campaign | Alaska Paradise \ / - NO HTML/RTF in e-mail | 201 East 9Th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://www.alaskaparadise.com =2D------------------------------------------------------------------------= =2D------------- =2D-=20 =2D------------------------------------------------------------------------= =2D------------- Beech Rintoul - Sys. Administrator - beech@alaskaparadise.com /"\ ASCII Ribbon Campaign | Alaska Paradise \ / - NO HTML/RTF in e-mail | 201 East 9Th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://www.alaskaparadise.com =2D------------------------------------------------------------------------= =2D------------- --nextPart3152729.fiyboQAPv3 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEkctqR5sEeCt9j00RApGmAKCLcysKEirUOLFL0yytwfH3wlhdxQCeKe7u lt+xZL1+MCLoIu9qRRImRmA= =iOrn -----END PGP SIGNATURE----- --nextPart3152729.fiyboQAPv3--