Date: Thu, 15 Jun 2006 21:03:54 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Beech Rintoul <beech@alaskaparadise.com> Cc: Mike Jakubik <mikej@rogers.com>, freebsd-current@freebsd.org, current@freebsd.org, Alexander Leidinger <Alexander@leidinger.net> Subject: Re: HEADS-UP: removed COMPAT_43 from GENERIC (and other configs) Message-ID: <36905.1150405434@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 15 Jun 2006 12:59:38 PST." <200606151259.57929.beech@alaskaparadise.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200606151259.57929.beech@alaskaparadise.com>, Beech Rintoul writes: >--nextPart6195424.2x6DgSG1L7 >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. I think the trick is to remove those from your kernel and remove the <sgtty.h> #include file and then build all the ports :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36905.1150405434>