"Michael R. Jinks" wrote: > > FWIW they announced this a month or so ago on (IIRC) BugTraq. I > understand that it's a once-only problem, the "Y2K+1" bug. Har har har > har har har har. > If I read the same article, it's not a once only problem. It said something about it happening when April 1st is on a Sunday, the next time being ~2007. [All statistics quoted entirely from an over-used memory, and may not be entirely accurate.<G>] -- =========================================== With regards, Ant Hover, Computer Engineer Albatross Networks Ltd. (http://www.albatross.co.uk) _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
- Micro$oft strikes again! Mike Watson
- Re: Micro$oft strikes again! David Brett
- Re: Micro$oft strikes again! Michael George
- Re: Micro$oft strikes aga... Mike Chambers
- Re: Micro$oft strikes again! Matthew Saltzman
- Re: Micro$oft strikes aga... David Brett
- Re: Micro$oft strikes... Mikkel L. Ellertson
- Re: Micro$oft strikes... Matthew Saltzman
- Re: Micro$oft strikes again! Krikofer
- Re: Micro$oft strikes again! Ant Hover
- Re: Micro$oft strikes again! Mike Watson
- Re: Micro$oft strikes again! Michael S. Dunsavage
- Re: Micro$oft strikes again! David Talkington
- RE: Micro$oft strikes again! TANNER
- RE: Micro$oft strikes again! David Brett
- copying David Brett
- Re: copying Bret Hughes
- RE: Micro$oft strikes again! Alejandro González Hernández - Imoq
- Re: Micro$oft strikes again! Bill Carlson