From owner-freebsd-arch@FreeBSD.ORG Fri Jun 25 10:23:16 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5047516A4CE; Fri, 25 Jun 2004 10:23:16 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9890643D1F; Fri, 25 Jun 2004 10:23:15 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.12.11/8.12.11) with ESMTP id i5PAM1fn012550; Fri, 25 Jun 2004 12:22:01 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 24 Jun 2004 18:59:54 PDT." <200406241859.54810.peter@wemm.org> Date: Fri, 25 Jun 2004 12:22:01 +0200 Message-ID: <12549.1088158921@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: arch@freebsd.org cc: David Schultz cc: marcel@xcllnt.net cc: freebsd-arch@freebsd.org Subject: Re: COMPAT_43 tty processing ? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jun 2004 10:23:16 -0000 In message <200406241859.54810.peter@wemm.org>, Peter Wemm writes: >On Wednesday 23 June 2004 04:27 pm, David Schultz wrote: >> On Mon, Jun 21, 2004, Poul-Henning Kamp wrote: >> > Do we need the COMPAT_43 tty processing in 5-STABLE ? >> >> FWIW, I used to run with COMPAT_43 disabled entirely. I think the >> only breakage I noticed was that the Linuxolator didn't work >> anymore because of a number of `#ifdef COMPAT_43's in the socket >> code that linux.ko depends on. > >These should probably be broken out as COMPAT_OLDSOCK, whih is implied >by the linuxulator or COMPAT_43 or the like. Or better yet: made unncessary in the linuxolator ? >These days we could probably just kill it entirely and replace it with a >short recipe for converting code. eg: list what the new names for >the flags and modes are. Most programs do little more than either run >in the default line processing mode, or drop into raw mode via >cfmakeraw() and friends, possibly with a couple of tweaks to the >generated termios settings. > >No, I'm not volunteering to extract this code of a QIC 6150 tape that I >have with it on. I'd sooner help delete it from src/sys than revive >that monster. :-) I've asked our ports-meister to run a build without the COMPAT_43 tty code and the ports crew to get rid of -lcompat in the ports to the extent possible and I fully expect COMPAT_43 tty processing to not be in 5-STABLE. -- 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.