From owner-freebsd-stable@FreeBSD.ORG Tue Jan 13 14:08:53 2004 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 4EF3116A4E6 for ; Tue, 13 Jan 2004 14:08:53 -0800 (PST) Received: from mail3.panix.com (mail3.panix.com [166.84.1.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F75943D72 for ; Tue, 13 Jan 2004 14:08:27 -0800 (PST) (envelope-from fj@panix.com) Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail3.panix.com (Postfix) with ESMTP id 3CE1F983E3 for ; Tue, 13 Jan 2004 17:08:26 -0500 (EST) Received: (from fj@localhost) by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i0DM8Qt27147 for freebsd-stable@FreeBSD.ORG; Tue, 13 Jan 2004 17:08:26 -0500 (EST) Date: Tue, 13 Jan 2004 17:08:26 -0500 From: Joe Altman To: freebsd-stable@FreeBSD.ORG Message-ID: <20040113220825.GA25495@panix.com> Mail-Followup-To: Joe Altman , freebsd-stable@FreeBSD.ORG References: <20040113204738.GA14543@panix.com> <200401132056.i0DKu1YO011391@bunrab.catwhisker.org> <20040113213324.GA14556@VARK.homeunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040113213324.GA14556@VARK.homeunix.com> User-Agent: Mutt/1.4.1i Subject: Re: make buildkernel KERNCONF errors... 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: Tue, 13 Jan 2004 22:08:53 -0000 In this context, "...committed a fix.." means something like: "I applied a patch to the root of a CVS source tree, and it will dist over the next 24-48 hours to all of the relevant CVSUP machines. Try to upgrade sources at intervals over this time period; if it fails after this interim, send another heads-up." I ask because in the three years I've used FreeBSD, I've never seen this type of failure, so I'm not at all informed WRT the parameters and such about the fix. Feel free to redirect to -questions; I only ask here because I'm not sure if either of the two respondents read -questions. Thanks for your help, David and David... fj On Tue, Jan 13, 2004 at 01:33:24PM -0800, David Schultz wrote: > On Tue, Jan 13, 2004, David Wolfskill wrote: > > Anyway, this worked for me on 2 machines, but I don't actually use > > unionfs on either one: > > > > Index: sys/miscfs/union/union_vnops.c > > Thanks, and sorry about the botch. I just committed a fix. > > I had decided to test this patch under my free copy of VirtualPC > (new toy!), but since NFS didn't immediately work over the virtual > network, I copied the merged sources, fixed the bug when I > encountered it, and forgot to copy them back. Whups. But the > biggest whups of all was using VirtualPC at all---the buildworld > took close to 20 hours on a P3-450.