On Tue, Jul 19, 2005 at 11:28:03AM +0200, Marc Olzheim wrote: > 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. > > > > > > Me too, but a lot has changed since 5.2.1 which at the time was I think > > > was > > > called a preview. The topic is 5.4R. What parts of the OS do you feel > > > are > > > not production ready as compared to 4.X ? > > > > Personnally, when upgrading from 4.x to 5.x, we ran into the following > > 3 issues that are still not fixed in 5.4: > > > > kern/80617: > > Hangup writing large blocks to NFS mounted FS (Patches available) > > Not exremely important: just don't do that. > > > > kern/79208: > > i387 libm's floorf(), ceilf() and truncf() (Fixed in RELENG_5) > > PITA when running threaded calculations. > > > > kern/78824 > > socketpair()/close() race condition (Fixed in CURRENT) > > Patch will be MFC'd to RELENG_5 soon. > > > > 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...
ARGH, nevermind, 5.4-release-p4 crashes on: kern/83375 Fatal trap 12 cloning a pty (Broken in 5.4-7.x) I'll have to revert to 4.10 or 4.11 for our servers, until I can manage to keep a single test machine up and rnuning... :-( Marc
pgpVvfv16tHjJ.pgp
Description: PGP signature
