From owner-freebsd-current@FreeBSD.ORG  Tue Sep 16 03:13:09 2003
Return-Path: <owner-freebsd-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 BBC8A16A4B3; Tue, 16 Sep 2003 03:13:09 -0700 (PDT)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id BAF0343FBF; Tue, 16 Sep 2003 03:13:07 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246])
	by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id UAA06955;
	Tue, 16 Sep 2003 20:13:04 +1000
Date: Tue, 16 Sep 2003 20:11:42 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: Maxim Konovalov <maxim@freebsd.org>
In-Reply-To: <20030916131622.N54869@news1.macomnet.ru>
Message-ID: <20030916200513.R4917@gamplex.bde.org>
References: <3F66A446.7090408@freebsd.org>
	<20030916131622.N54869@news1.macomnet.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: Re: Release Engineering Status Report
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2003 10:13:09 -0000

On Tue, 16 Sep 2003, Maxim Konovalov wrote:

> PAE MFC brought an incredible instability to stable branch.  It
> affects 100% of our user community especially when we issued several
> SAs since PAE commit.  They often can't switch to RELENG_4_x security
> branches because even RELENG_4_8 misses several critical non-security
> fixes.

I merged PAE into my version of -current a bit at a time and didn't
notice any problems (with PAE not actually configured) despite having
some large logical inconsistencies from not having all of it.  Most
of the global changes had no effect since they just changed the names
of some typedefs without changing the underlying types in the !PAE
case.  So I suspect that any instabilities in RELENG_4 in the !PAE
case are indirectly related to PAE and/or localized and thus easy to
find and fix.

Bruce