From owner-freebsd-stable@FreeBSD.ORG Fri Feb 25 13:56:58 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E613016A4CE for ; Fri, 25 Feb 2005 13:56:58 +0000 (GMT) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DC8843D64 for ; Fri, 25 Feb 2005 13:56:58 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with SMTP id DBC9B46B11 for ; Fri, 25 Feb 2005 08:56:57 -0500 (EST) Date: Fri, 25 Feb 2005 13:55:11 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: stable@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: HEADS UP: netipx mega-MFC (1/2) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Feb 2005 13:56:59 -0000 I've just merged a fairly large set of changes to the netipx tree from HEAD to RELENG_5. These primarily consist of structural changes required for the locking of the netipx protocol, but excludes the locking changes themselves. The theory is we'll let these changes settle for a few days, then bring the locking changes in in time for 5.4-RELEASE. While these changes have been tested in HEAD, and have been in the tree generally for at least a month, netipx doesn't get a lot of exercise so there may be problems. Please let me know if you experience any. I have received at least one report that netipx is still not working with Mars in RELENG_5. I hope to follow up on that report shortly. Unfortunately, I don't have a significant local IPX setup to test with, so have to release on third party reports. In general, when reporting netipx issues, it would be very helpful if you could indicate whether whatever problem you're experiencing occurs in the 4.x tree, in 5.x before my recent changes, and 5.x after my recent changes. Thanks, Robert N M Watson