1*a53f50b9Schristos AM-UTILS YEAR-2000 COMPLIANCE 2*a53f50b9Schristos 3*a53f50b9SchristosMost likely am-utils is y2k compliant. 4*a53f50b9Schristos 5*a53f50b9SchristosI do not know for sure because I have not certified am-utils myself, nor do 6*a53f50b9SchristosI have the time for it. I do not think that amd will be affected by y2k at 7*a53f50b9Schristosall, because it does not do anything with dates other than print the date on 8*a53f50b9Schristosthe log file, in whatever format is provided by your os/libc --- especially 9*a53f50b9Schristosthe ctime(3) call. 10*a53f50b9Schristos 11*a53f50b9SchristosHowever, on Friday, September 18th 1998, Matthew Crosby <mcrosby AT ms.com> 12*a53f50b9Schristosreported that they evaluated 6.0a16 and found it to be compliant. 13*a53f50b9Schristos 14*a53f50b9SchristosOn March 26, 1999, Paul Balyoz <pbalyoz AT sedona.ch.intel.com> submitted a 15*a53f50b9Schristospatch to lostaltmail which makes it print Y2K compliant dates. He used a 16*a53f50b9Schristoscode scanner and manually "eyeballed" the code and could not find any more 17*a53f50b9Schristosproblems. Paul's patch is included in am-utils-6.0.1s7 and newer versions. 18*a53f50b9SchristosPaul also said that other 2-digit years used in am-utils are "harmless." 19*a53f50b9Schristos 20*a53f50b9SchristosNOTE: NONE OF THE PERSONS MENTIONED HERE, AUTHOR INCLUDED, ARE WILLING TO 21*a53f50b9SchristosCERTIFY AM-UTILS AS Y2K COMPLIANT. USE AT YOUR OWN RISK. 22*a53f50b9Schristos 23*a53f50b9Schristos--- 24*a53f50b9SchristosErez Zadok. 25*a53f50b9SchristosMaintainer, am-utils package and am-utils list. 26*a53f50b9SchristosWWW: http://www.am-utils.org 27