diff --git a/en/y2kbug.sgml b/en/y2kbug.sgml
index 3d0d3ab7fe..1228b97a25 100644
--- a/en/y2kbug.sgml
+++ b/en/y2kbug.sgml
@@ -1,9 +1,9 @@
+
%includes;
]>
-
+
&header;
@@ -83,42 +83,51 @@
misc/1380
Several programs have a hardcoded 19%d in responses for the year.
- Affected programs include: yacc, ftpd, and make.
+ Affected programs include: yacc, ftpd, and make.
+ [Fixed: yacc v1.2 1999/01/18; ftpd v1.7 1996/08/05;
+ make v1.4 1996/10/06]
+
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.
+ 1999.[Fixed v1.21 1996/10/24]
+
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.
+ 1YYMMDD.[Fixed v1.2 1997/08/11]
+
gnu/4930 and
gnu/8321
- groff tmac macros have hardcoded 19 for generating some dates.
+ groff tmac macros have hardcoded 19 for generating some dates.
+ [Fixed: tmac.e v1.3 1998/12/06; doc-common v1.10 1999/01/19]
+
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.
+ as 1900-1968 instead of 2000-2068.[Fixed v1.7 1999/01/05]
+
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.
+ These errors affected all years.[Fixed v1.6 1999/01/12]
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
@@ -130,13 +139,14 @@
as always belonging to the current century unless they would be
50 or more years in the future. Since the HTTP servers which
use this obsolete format are no longer widespread, this is not expected
- to have a significant impact.
+ to have a significant impact.[Fixed v1.24 1999/01/15]
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]
bin/9503
PicoBSD's simple_httpd uses a raw tm_year and will therefore
- display 01/01/100 for 2000-JAN-01.
+ display 01/01/100 for 2000-JAN-01.[Fixed v1.2 1999/01/16]
bin/9505
Adduser uses a raw tm_year and will therefore display 100/01/01 for
- 2000-JAN-01.
+ 2000-JAN-01.[Fixed v1.42 1999/01/15]
bin/9506
Cron uses a raw tm_year and will therefore display 100 for 2000.
+ [Fixed v1.7 1999/01/16]
bin/9507
tcpslice(8) uses a raw tm_year and will therefore display
100y01m01d... for 2000-JAN-01. For compatibility, use a two-digit
- year until 2000.
+ year until 2000.[Fixed v1.8 1999/01/20]
@@ -190,25 +202,30 @@
TkDesk 1.0 uses a hardcoded 19 in the file listing window. A
file with a date > 2000 is displayed with a year looking like
"191xx" where xx is the last two numbers of the real date. This
- bug has been fixed in version 1.1.
+ bug has been fixed in version 1.1.[Port updated 1998/10/10]
+
ports/9295
INN 1.7.2 suffers from 2 Y2K related problems. One occurs when
pulling news (-f option to nntpget) and the other relates to
- the Expire header with relative dates past 2000.
+ the Expire header with relative dates past 2000.
+ [Fixed v1.30(both inn and inn-stable) 1999/01/13]
+
ports/9298
Knews suffers from 2 Y2K related problems. One occurs during
the generation of the NNTP NEWGROUPS command. The other occurs
because knews doesn't think that 2000 is a leap year.
- Both are fixed in knews-1.0b.1.
+ Both are fixed in knews-1.0b.1.[Port updated 1999/01/07]
+
ports/9300
Nntp-t5 suffers from a Y2K problem during the generation of
- the NEWNEWS command.
+ the NEWNEWS command.[Port patched 1999/01/05]
+
More information