From owner-freebsd-bugs Wed Nov 25 04:45:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01215 for freebsd-bugs-outgoing; Wed, 25 Nov 1998 04:45:36 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01209; Wed, 25 Nov 1998 04:45:32 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id EAA04142; Wed, 25 Nov 1998 04:46:43 -0800 (PST) Message-Id: <199811251246.EAA04142@root.com> To: Michael Ryan cc: "Jonathan M. Bresler" , Poul-Henning Kamp , wollman@khavrinen.lcs.mit.edu, freebsd-bugs@FreeBSD.ORG Subject: Re: Y2K In-reply-to: Your message of "Wed, 25 Nov 1998 10:08:47 PST." From: David Greenman Reply-To: dg@root.com Date: Wed, 25 Nov 1998 04:46:43 -0800 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >On Tue, 24 Nov 1998 09:49:20 -0800 (PST) Jonathan M. Bresler wrote: > >> since FreeBSD-2.2.5, there have been a number of bug fixes. >> These are available in FreeBSD-2.2.7 and soon to be >> released (Nov 30th) FreeBSD-2.2.8. >> >> Your customer is "entitled" to these bug fixes, is he not? >> When you upgrade to fix those bugs, our Y2K statement >> will apply to the resulting installtion of FreeBSD-2.2.[78] > >Thank you for a reasonable and friendly answer, Jonathan. >This exchange between myself and phk has already worn out but >my simple query is whether there's a statement of compliance or >not (or a "don't know") for 2.2.5R in particular. The upgrade >process is a simple one technically but takes time, which is >what I'm trying to avoid, as it'll cost my customer money. I think 2.2.5 was released after we made our Y2K compliance statement, so 2.2.5 would have been thought to be Y2K compliant at the time. It wouldn't surprise me if there have been minor Y2K fixes since that release, but this isn't something that we keep track of, at least not in terms of it affecting the Y2K compliance of previous releases. We can never guarantee that any release of FreeBSD is "compliant" - only that as far as we can tell it is. Guarantees have certain legal obligations (and remedies under law) which we are not able to make. I think the main thing that people are taking issue with is the idea that upgrades can be avoided if Y2K compliance is assured. FreeBSD (or any other unix) has never had 'major' Y2K problems, so putting the importance of that above all else really diminishes the importance of other bugfixes and improvements. In other words, you have plenty of good (better) reasons to upgrade your customer's machine(s), nevermind Y2K. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message