From owner-freebsd-current@FreeBSD.ORG Sun Apr 2 23:00:13 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 BF73216A426; Sun, 2 Apr 2006 23:00:13 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id E05C243D45; Sun, 2 Apr 2006 23:00:12 +0000 (GMT) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id 51A3778C1D; Sun, 2 Apr 2006 23:00:12 +0000 (GMT) Date: Sun, 2 Apr 2006 23:00:12 +0000 From: John Birrell To: Robert Watson Message-ID: <20060402230012.GA24758@what-creek.com> References: <20060317141627.W2181@fledge.watson.org> <20060329100839.V19236@fledge.watson.org> <20060401102918.P79188@fledge.watson.org> <20060401170554.R82503@fledge.watson.org> <20060402233436.P76562@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060402233436.P76562@fledge.watson.org> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Wed, 05 Apr 2006 12:18:01 +0000 Cc: current@FreeBSD.org Subject: Re: HEADS UP: socket and pcb reference changes entering tree today 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: Sun, 02 Apr 2006 23:00:14 -0000 On Sun, Apr 02, 2006 at 11:37:21PM +0100, Robert Watson wrote: > OK, so it's been >24 hours since this was committed, and I've not received > any bug reports yet. This means once of three things: > > (1) There are no bugs. > > (2) I've broken everyone's systems so badly they can't submit bug reports. > > (3) Everyone is waiting for everyone else to upgrade due to the advance > notice > of instability. > > I consider (1) highly likely, (2) a property of 1990's development and > we've left that time since most people have multiple machines now, and (3) > much more likely. > > Please help test these changes! I leave for a trip to the US on Thursday, > and I'd rather get things working before I leave than while on travel, it > will save a lot of hassle for everyone. > > And if you're reading this after spending 48 hours getting your systems > working again to the point where you can read e-mail, sorry :-). I've just updated a current system which also serves as a (socket based) backup system for a remotely hosted web site with LOTS of file updates. The update went without a hitch and the system seems to work fine AFAICT. I guess that sounds like a bit of an anti-climax, but there really isn't anything to report. Sorry. 8-) Perhaps I just don't know what to look for. Shrug. -- John Birrell