From owner-freebsd-current Thu Jun 6 7:20:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from vbook.express.ru (asplinux.ru [195.133.213.194]) by hub.freebsd.org (Postfix) with ESMTP id 25BCD37B400 for ; Thu, 6 Jun 2002 07:20:15 -0700 (PDT) Received: from vova by vbook.express.ru with local (Exim 3.36 #1) id 17Fy7N-0008Qa-00; Thu, 06 Jun 2002 18:20:01 +0400 Subject: Re: "Safe" to go to -CURRENT? From: "Vladimir B. " Grebenschikov To: Sheldon Hearn Cc: "current@freebsd.org" In-Reply-To: <1626.1023353655@axl.seasidesoftware.co.za> References: <1626.1023353655@axl.seasidesoftware.co.za> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable X-Mailer: Ximian Evolution 1.0.5 Date: 06 Jun 2002 18:20:00 +0400 Message-Id: <1023373200.470.13.camel@vbook.express.ru> Mime-Version: 1.0 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 =F7 Thu, 06.06.2002, =D7 12:54, Sheldon Hearn =CE=C1=D0=C9=D3=C1=CC: > > I've been monitoring the -CURRENT mailing list for about a day or two, > > and haven't seen anything that's really broken (except for GCC 3.x, > > which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet? > > TIA for the info, > > Chris >=20 > There are still issues with the C++ compiler in the base system that > make building X and some other C++ ports tricky. If you use a lot of X > applications, you might want to hold back if you're looking for a smooth > ride. >=20 > The base system itself seems pretty stable, though. Not sure, yesterdays kernel give me panic somewhere about ufsdir. Week-old kernel work very good. Turning off softupdates and doing fsck not in background not helps. I will fill PR just after connecting serial console. =20 > Ciao, > Sheldon. =20 --=20 Vladimir B. Grebenschikov vova@sw.ru, SWsoft, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message