From owner-freebsd-stable@FreeBSD.ORG Mon Mar 19 12:22:56 2007 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 85B7A16A401 for ; Mon, 19 Mar 2007 12:22:56 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.freebsd.org (Postfix) with ESMTP id 4954513C45D for ; Mon, 19 Mar 2007 12:22:56 +0000 (UTC) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.ticketswitch.com) by mail.ticketswitch.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1HTGt5-0009Ww-I9; Mon, 19 Mar 2007 12:22:55 +0000 Received: from petefrench by dilbert.ticketswitch.com with local (Exim 4.66 (FreeBSD)) (envelope-from ) id 1HTGt3-000F0K-9m; Mon, 19 Mar 2007 12:22:53 +0000 To: delphij@delphij.net In-Reply-To: <45FE75AD.6090000@delphij.net> Message-Id: From: Pete French Date: Mon, 19 Mar 2007 12:22:53 +0000 Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Reverting to 6.2-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2007 12:22:56 -0000 > I think you will want RELENG_6_2_0_RELEASE. thanks (and to the others who responded) > What happens with RELENG_6_2, IIRC there was only very limited changes > to kernel which should only affect IPv6... Indeed! Part of the reason I want to do the revert is to make absolutely sure that it runs the GENERIC kernel from RELEASE properly. The kernel I have running on it is a binary from elsewherre which was built from the 6.2 RELEASE code, but I no longer have the options it was built with (though I can tell it does not contain IPv6). Hence I want to make sure that the problem is with the change to IPv6 and not the existence of IPv6 in general on that machine. Will report back if it turns out to be a problem with RELENG_6_2 cheers, -pete.