From owner-freebsd-current@FreeBSD.ORG Wed Mar 29 18:00:51 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 DFEF816A424; Wed, 29 Mar 2006 18:00:51 +0000 (UTC) (envelope-from skip.ford@verizon.net) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99C9F43D46; Wed, 29 Mar 2006 18:00:51 +0000 (GMT) (envelope-from skip.ford@verizon.net) Received: from pool-70-17-33-65.pskn.east.verizon.net ([70.17.33.65]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IWW00MDGI1EHO21@vms046.mailsrvcs.net>; Wed, 29 Mar 2006 12:00:51 -0600 (CST) Date: Wed, 29 Mar 2006 13:00:50 -0500 From: Skip Ford In-reply-to: <20060329115028.C19236@fledge.watson.org> To: Robert Watson Message-id: <20060329180050.GA997@lucy.pool-70-17-33-65.pskn.east.verizon.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline References: <20060317141627.W2181@fledge.watson.org> <20060329100839.V19236@fledge.watson.org> <20060329115028.C19236@fledge.watson.org> User-Agent: Mutt/1.4.2.1i Cc: Randall Stewart , current@FreeBSD.org Subject: Re: REMINDER: Re: HEADS UP: network stack and socket hackery over the next few weeks 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: Wed, 29 Mar 2006 18:00:52 -0000 Robert Watson wrote: > The following protocols are not updated for the new world order, and do not > have a maintainer: > > netatm > > I will commit the changes to make netatm compile, but am pretty sure there > will be socket reference problems. I've been working on bringing netatm into compliance with the new world order. There are currently so many other problems with netatm, socket reference problems aren't likely to cause much more of a headache for users. :-) I have a list of half a dozen or so netatm panics prior to your changes, without exercising much of code over just a few days. I've fixed two panics locally, the rest still exist in my tree, and all are still in HEAD. I don't believe the version in the tree can even do the simplest of tasks. My version at least has minimal functionality but I can still make it panic within seconds. So, it's hard for me to believe anyone will notice when it's disconnected from the build. That's not to say they won't miss it in a release though. -- Skip