From owner-freebsd-bugs Mon Dec 28 13:10:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20408 for freebsd-bugs-outgoing; Mon, 28 Dec 1998 13:10:38 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from u2.bbrown.com ([192.30.147.97]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA20400 for ; Mon, 28 Dec 1998 13:10:35 -0800 (PST) (envelope-from pekarske_bob@burr-brown.com) Received: from [192.30.147.253] by u2.bbrown.com with SMTP (1.38.193.5/16.2) id AA15926; Mon, 28 Dec 1998 14:10:17 -0700 Message-Id: <36879149.6418@burr-brown.com> Date: Mon, 28 Dec 1998 14:10:17 +0000 From: Bob Pekarske X-Mailer: Mozilla 3.01 (Win95; U) Mime-Version: 1.0 To: freebsd-bugs@FreeBSD.ORG Cc: pekarske_bob@u2.bbrown.com Subject: Y2K Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have been trying for years to convince my management to take FreeBSD seriously as an platform in our business. It has also been my misfortune to be assigned to our Y2K project. I must say that I am VERY disappointed in the FreeBSD Y2K compliance page and its compliance statement. I emplore you to take this issue more seriously, if only to be consistant with all of your competitors in the corporate server market. Take a look at the HP Y2K page, or cisco's. (Both sell unix-based products.) The clock is the least of your problems. And the clock is not the basis for the original Y2K bug. You have programs and library calls in the distribution which convert ticks to calendar time: date and ctime are examples. Do they work correctly? Do they deal with the leap year status of 2000 correctly. You also distribute a bundle of shell applications with the core distribution. Any one of them could access the time conversion functions and work with a two digit date. You need to verify they do not. Will "ls" sort by date correctly? Will "find -mtime" filter correctly? Your "known fixes" sections includes make, ftpd, dns, etc., all functions that a corporate user would consider part of the OS. You need to address them seriously. If the answer is they all work correctly, GREAT! But please don't leave your site the way it is now. My fellows in industry CANNOT take it seriously, and we will not test it for you. My management will simply say "I told you that was an unsupported OS. Convert to a real system before 2000." That would be a shame, and would negate much of the recent progress. Thank you for listening. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message