From owner-freebsd-arch@FreeBSD.ORG Mon Dec 6 10:15:22 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 B7D3516A4CE for ; Mon, 6 Dec 2004 10:15:22 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46A1D43D66 for ; Mon, 6 Dec 2004 10:15:22 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iB6AJTrh098138; Mon, 6 Dec 2004 03:19:29 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41B43140.802@freebsd.org> Date: Mon, 06 Dec 2004 03:15:28 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <79552.1102327805@critter.freebsd.dk> In-Reply-To: <79552.1102327805@critter.freebsd.dk> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: arch@freebsd.org Subject: Re: [HEADSUP] IPX and NWFS to be killed in -current. 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: Mon, 06 Dec 2004 10:15:23 -0000 Poul-Henning Kamp wrote: > We are aiming 6.X at production readiness around start of 2006. > > By that time IPX and NWFS are not really interesting and nobody > seems to be interested in doing the SMPng work on them. > > I propose we remove them from -current before the 6.x freeze starts > next spring. > Are these getting in the way of current work? We have shims in place to make at least IPX operate correctly without explicit locking. Saying that they are old and not used by people who read arch@ isn't a compelling argument to remove them. If they are getting in the way of current work, then it would be much friendlier to ask for help rather than summarily announcing their doom. Scott