From owner-freebsd-current Wed Jan 24 8:37:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5EC4837B698; Wed, 24 Jan 2001 08:37:09 -0800 (PST) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.1/8.11.0) with ESMTP id f0OGb8s15794; Wed, 24 Jan 2001 09:37:08 -0700 (MST) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.1/8.8.3) with ESMTP id f0OGZMs07562; Wed, 24 Jan 2001 09:35:24 -0700 (MST) Message-Id: <200101241635.f0OGZMs07562@billy-club.village.org> To: Peter Wemm Subject: Re: HEADS UP: current broken for a while Cc: John Baldwin , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 24 Jan 2001 07:03:16 PST." <200101241503.f0OF3G481822@mobile.wemm.org> References: <200101241503.f0OF3G481822@mobile.wemm.org> Date: Wed, 24 Jan 2001 09:35:22 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101241503.f0OF3G481822@mobile.wemm.org> Peter Wemm writes: : Normal - as in "It compiles". I would *strongly* caution anybody (even : more so than usual) about using -current where a crash would be bad. A lot : of new stuff went in and INVARIANTS and WITNESS are still finding some edge : cases. The proc locking stuff is not yet finished, this part of the commit : has the files with dependencies on changes in other files. There is more : to come. Will this new instability last long enough to warrant a note in UPDATING? Or is it a day or two sort of instability. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message