Date: Sat, 16 Jan 1999 21:48:16 +1100 (EST) From: "Daniel O'Callaghan" <danny@hilink.com.au> To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Cc: committers@FreeBSD.ORG Subject: Re: Y2K compliance question Message-ID: <Pine.BSF.3.96.990116213640.18759B-100000@helium.clari.net.au> In-Reply-To: <99092.916474783@zippy.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 16 Jan 1999, Jordan K. Hubbard wrote: > > Right now, FreeBSD-current is *NOT* y2k compliant. I know that there > > *are* bugs remaining. > > It would help vastly if you could be more specific. Saying, for > example, that you found "problems" or that there were "beasties" > lurking aren't technically detailed enough to be useful. I've been looking for, discovering and fixing y2k problems for a week. I was just trying to say that I have not finished looking and I expect to find more. Hence, statements that FreeBSD is compliant are, IMHO, not really true. At the time I wrote the above, I had some things in my "to do" list. Perhaps I should have said, "there are bugs remaining in cvs and bind and probably elsewhere". Danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990116213640.18759B-100000>