Date: Tue, 25 May 1999 03:40:28 -0700 From: Don Lewis <Don.Lewis@tsc.tdk.com> To: Sergey <serge69@nym.alias.net>, "Mike Smith" <mike@smith.net.au> Cc: <freebsd-stable@FreeBSD.ORG> Subject: Re: [Q] How stable is FreeBSD 3.X ? Message-ID: <199905251040.DAA04271@salsa.gv.tsc.tdk.com> In-Reply-To: Sergey <serge69@nym.alias.net> "Re: [Q] How stable is FreeBSD 3.X ?" (May 25, 6:27am)
next in thread | previous in thread | raw e-mail | index | archive | help
We upgraded our news server to the 3.0 branch just after the worst of the softupdates bugs were fixed (before 3.0-RELEASE), and it ran for months with problems. The only two times it was down were the time I shut it down to install another disk and the time I shut it down to upgrade to a newer version of 3.x so that I could use vinum. I had a couple of minor problems with the upgrade and one hang that was caused by a filesystem bug which was fixed around the time of 3.2-RELEASE. I also got bit by a lingering inetd bug which I tracked down to a longstanding bug in libutil. The current uptime is two weeks. I'm planning on upgrading to the latest -STABLE in the next week, since there are some bug fixes I'd like to pick up. On the other hand, we use some closed-source commercial software that costs well up into five figures, with an annual maintenance charge in the same neighborhood, and the vendor won't do squat about bugs unless you send in a reproduceable example of something that will break their software. If we're lucky, the bug will be fixed in the next release. We also have a Sun support contract. They never have fixed the bug that causes their X server to core dump. Instead they blame off on the vendor of the client that provokes the problem. There's nothing like losing a couple of hours of work on a random basis. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905251040.DAA04271>