From owner-freebsd-arch@FreeBSD.ORG Thu Dec 9 14:19:34 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 606B316A4CE; Thu, 9 Dec 2004 14:19:34 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02E0B43D54; Thu, 9 Dec 2004 14:19:34 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.1.102] (CPE000625f86c85-CM000e5c22aba0.cpe.net.cable.rogers.com [69.193.110.163] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iB9ELhK3021057; Thu, 9 Dec 2004 07:21:45 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41B85EF6.5090008@freebsd.org> Date: Thu, 09 Dec 2004 07:19:34 -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: Boris Popov References: <79552.1102327805@critter.freebsd.dk> <20041209091932.GA14988@vertex.kz> In-Reply-To: <20041209091932.GA14988@vertex.kz> 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 cc: Poul-Henning Kamp cc: Robert Watson 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: Thu, 09 Dec 2004 14:19:34 -0000 Boris Popov wrote: > On Mon, Dec 06, 2004 at 04:56:21PM +0000, Robert Watson wrote: > >> >>FYI, I have a substantial work in progress in the netperf branch to bring >>fine-grained locking to IPX/SPX, as well as to clean up a number of >>elements of its implementions (for example, moving the the queue(9) >>macros. While I'm currently a bit stalled on it due to being overwhelmed >>at work (etc), my hope was to get the Giant-free IPX pieces working early >>next year. I think there's a reference to this on the SMPng page showing > > > These are perfect news. As the former active maintainer of IPX > protocol stack and the author of NWFS I'm receive notable amount of complains > about IPX support in 5.X as people upgrade boxes from 4.X. For some > people it works but nwfs doesn't and vise versa. > > Addressing phk's request about removal: there was exactly 93 > questions related to ipx/nwfs in November. This indeed encourages me to > fix them. Although, I can't promise anything at this point because > earning on life doesn't left much free time these days. > Boris, This is wonderful news too! If you have any questions or need help with testing, please don't hesitate to ask. Scott