From owner-freebsd-current@FreeBSD.ORG Wed Mar 29 18:12:02 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 653FB16A426 for ; Wed, 29 Mar 2006 18:12:02 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9A8843D45 for ; Wed, 29 Mar 2006 18:12:01 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id EA8A746C73; Wed, 29 Mar 2006 13:11:52 -0500 (EST) Date: Wed, 29 Mar 2006 18:11:53 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Skip Ford In-Reply-To: <20060329180050.GA997@lucy.pool-70-17-33-65.pskn.east.verizon.net> Message-ID: <20060329181036.I19236@fledge.watson.org> References: <20060317141627.W2181@fledge.watson.org> <20060329100839.V19236@fledge.watson.org> <20060329115028.C19236@fledge.watson.org> <20060329180050.GA997@lucy.pool-70-17-33-65.pskn.east.verizon.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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:12:02 -0000 On Wed, 29 Mar 2006, Skip Ford 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. Ah, great. Please feel free to drop me (or Harti, or whomever) netatm patches to bring in. I will move ahead with disconnecting netatm (which primarily means not building it in LINT at this point), and merge my changes. Let me know if I can be of any use in working out issues in getting netatm updated with respect to the sockets side of the house. Robert N M Watson