Y2K

Sean Donelan SEAN at SDG.DRA.COM
Sun May 10 01:31:21 UTC 1998


Since the rest of this has nothing to do with routers, for Randy:

clock set 00:00:00 1 jan 2000

>I don't but its an opportunity to sell the client.  And if you don't test it I
>recommend you don't get quoted saying it doesn't matter unless you want a
>lawsuit if anything happens.
>
>Customers want everything in writing to be Year 200 compliant or not having any
>affect on their operation and in many cases regulators are mandating it in
>writing. 

Funny how the customer wants it to be Y2K compliant, but they have no
problem with the rest of the software licenses that says "In no event
does xxxxx warrant that the Software is error free or that Customer
will be able to operate the Software without problems or interruptions."
Quoted directly from a very well-known vendor's license agreement, who
has issued big press releases about their Year 2000 Compliance program.
Its even going to be 'certified.'  Whoopie!

How about a challange, instead of issuing press releases about the Y2K
compliance, just remove the above sentence from your license agreement
and stand behind your product.

If something fails, does it really matter why it fails?  The problem is
it failed.

Some users have become so accustomed to using CTL-ALT-DEL, they think its
a normal part of the software function.  Why do I have this feeling on
January 3, 2000 (fortunately Jan 1, 2000 is a Saturday), the same number
of users are going to get the 'blue-screen of death' as on every other
day between now and then; but on the CBS evening news Dan Rather's
replacement will gravely report that millions of computers got the
'blue screen of death' because its the year 2000.
-- 
Sean Donelan, Data Research Associates, Inc, St. Louis, MO
  Affiliation given for identification not representation



More information about the NANOG mailing list