From owner-freebsd-current Wed Sep 25 19:47:17 2002 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 C2F9837B401; Wed, 25 Sep 2002 19:47:16 -0700 (PDT) Received: from corbulon.video-collage.com (corbulon.video-collage.com [64.35.99.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FA6443E65; Wed, 25 Sep 2002 19:47:16 -0700 (PDT) (envelope-from mi@corbulon.video-collage.com) Received: from corbulon.video-collage.com (localhost [127.0.0.1]) by corbulon.video-collage.com (8.12.2/8.12.2) with ESMTP id g8Q2l91P095890 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 25 Sep 2002 22:47:09 -0400 (EDT) (envelope-from mi@corbulon.video-collage.com) Received: (from root@localhost) by corbulon.video-collage.com (8.12.2/8.12.2/Submit) id g8Q2l8xA095889; Wed, 25 Sep 2002 22:47:08 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <200209260247.g8Q2l8xA095889@corbulon.video-collage.com> Subject: Re: troubles with recent -current In-Reply-To: To: Robert Watson Date: Wed, 25 Sep 2002 22:47:08 -0400 (EDT) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL92b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Scanned-By: MIMEDefang 2.15 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > On Wed, 25 Sep 2002, Mikhail Teterin wrote: > > FWIW, this -- introducing this sort of instability just two months > > before the scheduled release -- is a lot more damaging than the > > stupid trolls, IMO. The finger-breakers should consider leaving the > > troll alone and switching to super-gluing the pointy hats to the > > apropriate skulls :-| > There are probably going to be a few nits involved in the VFS changes, > but there are a number of serious bugs being fixed here. I've been > running into a bug on some boxes involving a race condition that > occurs when newsyslog runs on a busy system resulting in a inode > deadlock. It also may be that many of the problems were bumping into > now may merely be existing bugs that are now more visible. I'm sure we made progress. But it would be better, if the "few nits" were noticed and fixed before committing. They are impossible not to bump into -- judging by the others' responses -- unless, of course, the developers do not routinely use -current as their primary OS. Something we all should be doing now, that the long promised release date is only two months away. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message