From owner-freebsd-stable@FreeBSD.ORG Tue Jul 19 09:28:07 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D87716A41C for ; Tue, 19 Jul 2005 09:28:07 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE6D043D49 for ; Tue, 19 Jul 2005 09:28:05 +0000 (GMT) (envelope-from marcolz@stack.nl) Received: from hammer.stack.nl (hammer.stack.nl [IPv6:2001:610:1108:5010::153]) by mailhost.stack.nl (Postfix) with ESMTP id 01CFCA2FDD; Tue, 19 Jul 2005 11:28:04 +0200 (CEST) Received: by hammer.stack.nl (Postfix, from userid 333) id D493D6462; Tue, 19 Jul 2005 11:28:03 +0200 (CEST) Date: Tue, 19 Jul 2005 11:28:03 +0200 From: Marc Olzheim To: Mike Tancsa Message-ID: <20050719092803.GA10127@stack.nl> References: <20050608001306.3FB1F43D5C@mx1.FreeBSD.org> <42A6C7CE.9000002@incubus.de> <200506080908.02478.fcash@ocis.net> <42A71AE1.8020300@incubus.de> <6.2.1.2.0.20050608134054.06b8ccb0@64.7.153.2> <20050608180428.GA42445@stack.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline In-Reply-To: <20050608180428.GA42445@stack.nl> X-Operating-System: FreeBSD hammer.stack.nl 5.4-STABLE FreeBSD 5.4-STABLE X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.9i Cc: Matthias Buelow , freebsd-stable@freebsd.org Subject: Re: FreeBSD 5.4: Is it generally unstable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2005 09:28:07 -0000 --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 08, 2005 at 08:04:28PM +0200, Marc Olzheim wrote: > > >I remember 5.2.1 panicking left and right, on several machines, it was > > >completely unusable. Maybe we just live in different universes. > >=20 > > Me too, but a lot has changed since 5.2.1 which at the time was I think= was=20 > > called a preview. The topic is 5.4R. What parts of the OS do you feel= are=20 > > not production ready as compared to 4.X ? >=20 > Personnally, when upgrading from 4.x to 5.x, we ran into the following > 3 issues that are still not fixed in 5.4: >=20 > kern/80617: > Hangup writing large blocks to NFS mounted FS (Patches available) > Not exremely important: just don't do that. >=20 > kern/79208: > i387 libm's floorf(), ceilf() and truncf() (Fixed in RELENG_5) > PITA when running threaded calculations. >=20 > kern/78824 > socketpair()/close() race condition (Fixed in CURRENT) > Patch will be MFC'd to RELENG_5 soon. >=20 > Anyway: you won't catch me running an unpatched 5.4 system... I'd say > stick with RELENG_5 for the time being. Since I can't seem to keep any recent RELENG_5 kernel up and running atm. I'd change my viewpoint to run 5.4 and apply all necessary stability patches yourself. I'll prepare a patchset... Marc --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC3MejezjnobFOgrERAlyPAJ9VF3v4Q1qbJx0Ng2M2Kz1H9GAdlQCfcoYM YdcHgY92C3BP5sblSUvFh0s= =zBzG -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl--