Date: 06 Jun 2002 18:20:00 +0400 From: "Vladimir B. " Grebenschikov <vova@sw.ru> To: Sheldon Hearn <sheldonh@starjuice.net> Cc: "current@freebsd.org" <current@freebsd.org> Subject: Re: "Safe" to go to -CURRENT? Message-ID: <1023373200.470.13.camel@vbook.express.ru> In-Reply-To: <1626.1023353655@axl.seasidesoftware.co.za> References: <1626.1023353655@axl.seasidesoftware.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
=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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1023373200.470.13.camel>