From owner-freebsd-doc Wed Jun 2 18:51:56 1999 Delivered-To: freebsd-doc@freebsd.org Received: from istari.home.net (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (Postfix) with ESMTP id A44E014DF3 for ; Wed, 2 Jun 1999 18:51:49 -0700 (PDT) (envelope-from sjr@home.net) Received: (from sjr@localhost) by istari.home.net (8.9.3/8.9.3) id VAA12813 for freebsd-doc@freebsd.org; Wed, 2 Jun 1999 21:51:48 -0400 (EDT) (envelope-from sjr) Date: Wed, 2 Jun 1999 21:51:48 -0400 (EDT) From: "Stephen J. Roznowski" Message-Id: <199906030151.VAA12813@istari.home.net> To: freebsd-doc@freebsd.org Subject: Suggested enhancement to y2kbug.sgml page Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been looking at adding the following section to the Y2K bug web page (patch below). Basically, this adds a letter in front of each problem report, and creates a little table showing compliance. However, after doing this, it doesn't seem like it would be very useful (since most of the problems weren't fixed until the most recent releases). Also, I was unsure of where -STABLE releases fit in this timeline. So...... I'm looking for some feedback whether the attached is worth pursuing... Thanks, -SR --- en/y2kbug.sgml.orig Wed May 19 21:15:06 1999 +++ en/y2kbug.sgml Wed May 19 22:13:18 1999 @@ -74,13 +74,23 @@ FreeBSD project

+

Release information

+

+ Individual releases (without any additional patches) have the following + problems: +

+Previous releases, FreeBSD 2.1.5 - A, B, C, D, E, F, G, H, I, J, K, L, M, N, O
+FreeBSD 2.1.6, 2.1.7, 2.2, 2.2.1, 2.2.2 - A, C, D, E, F, G, H, I, J, K, L, M, N, O
+FreeBSD 2.2.5, 2.2.6, 2.2.7, 2.2.8, 3.0 - A, D, E, F, G, H, I, J, K, L, M, N, O
+FreeBSD 3.1, FreeBSD 3.2 - K
+

Fixed problems

The following Y2K problems have been identified and fixed in FreeBSD.

-
A. misc/1380
Several programs have a hardcoded 19%d in responses for the year. Affected programs include: yacc, ftpd, and make. @@ -88,21 +98,21 @@ make v1.4 1996/10/06]
-
B. conf/1382
The sed script in /etc/rc.local that builds the host/kernel ID line for the message of the day relies on the year not going past 1999.[Fixed v1.21 1996/10/24]
-
C. misc/3465
The etc/namedb/make-localhost command generates the DNS serial number as YYMMDD. In the year 2000, this will be generated as 1YYMMDD.[Fixed v1.2 1997/08/11]
-
D. gnu/4930 and gnu/8321
groff tmac macros have hardcoded 19 for generating some dates. @@ -110,27 +120,27 @@
-
bin/9323
+
E. bin/9323
In its obsolescent form, touch doesn't treat the two digit year year specification correctly. Years in the range 00-68 are treated as 1900-1968 instead of 2000-2068.[Fixed v1.7 1999/01/05]
-
xntpd/parse/util/dcfd.c
+
F. xntpd/parse/util/dcfd.c
The leap year calculations for the number of days in a year, and the conversion of DCF77 time to seconds since the Epoch were wrong. These errors affected all years.[Fixed v1.6 1999/01/12]
-
tar/getdate.y
+
G. tar/getdate.y
Function Convert() was hard-coded for two digit years in range 70-99. Now adjusted to allow two digit years for 1970-2069. The function does not allow for century non-leap years - y2k1 alert! [Fixed v1.4 1999/01/12]
-
fetch/http.c
+
H. fetch/http.c
The HTTP protocol includes an obsolete date format which uses a two-digit year. Previous versions of fetch would interpret all such dates in the 1900s; subsequent to this revision, the pivot described @@ -142,14 +152,14 @@ to have a significant impact.[Fixed v1.24 1999/01/15]
-
I. misc/9500
The `edithook' script in the CVSROOT directory uses a raw tm_year and will therefore display 01/01/100 for 2000-JAN-01. [Fixed v1.2 1999/01/17]
-
J. bin/9501
Several cvs contrib files are not Y2K compliant. The log.pl and sccs2rcs.csh scripts prepend `19' to the year @@ -160,32 +170,32 @@ [Fixed: log.pl v1.2 1999/01/15; sccs2rcs.csh v1.3 1999/01/15]
-
K. bin/9502
The groff number register `yr' is assigned from a (struct tm).tm_year and therefore represents the number of years since 1900, not the year within the century (see definition in troff/input.cc).
-
L. bin/9503
PicoBSD's simple_httpd uses a raw tm_year and will therefore display 01/01/100 for 2000-JAN-01.[Fixed v1.2 1999/01/16]
-
M. bin/9505
Adduser uses a raw tm_year and will therefore display 100/01/01 for 2000-JAN-01.[Fixed v1.42 1999/01/15]
-
N. bin/9506
Cron uses a raw tm_year and will therefore display 100 for 2000. [Fixed v1.7 1999/01/16]
-
O. bin/9507
tcpslice(8) uses a raw tm_year and will therefore display 100y01m01d... for 2000-JAN-01. For compatibility, use a two-digit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message