From owner-freebsd-newbies Sat Jun 27 08:11:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20526 for freebsd-newbies-outgoing; Sat, 27 Jun 1998 08:11:50 -0700 (PDT) (envelope-from owner-freebsd-newbies@FreeBSD.ORG) Received: from pteradactyl (pteradactyl.vaniercollege.qc.ca [205.236.144.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA20521 for ; Sat, 27 Jun 1998 08:11:47 -0700 (PDT) (envelope-from labrinop@pop.vaniercollege.qc.ca) From: labrinop@pop.vaniercollege.qc.ca Received: from labrinop.vaniercollege.qc.ca by pteradactyl (SMI-8.6/SMI-SVR4) id LAA08869; Sat, 27 Jun 1998 11:15:03 -0400 Message-Id: <199806271515.LAA08869@pteradactyl> To: freebsd-newbies@FreeBSD.ORG Date: Sat, 27 Jun 1998 11:13:32 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Re: References: Unix in 20-30 years Sender: owner-freebsd-newbies@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 26 Jun 1998 Tim Gerchmez wrote: > No, the fact is that I personally am unconcerned with Y2K issues as > of yet. I'm not a business, I'm a home user, and I don't even run > any software I know of that would be affected (and I don't program > in C at the current time, either). The worst that's gonna happen is > that my Email will be dated 1900. Big deal, so anyone with > cerebrospinal fluid where their brain is supposed to be might think > it's 1900. Maybe they'll go looking for Thomas Edison for light > bulbs instead of going to the supermarket. I used to do the weekly tape backup on a VAX-11/750, and remembered once that one of the directory entries got corrupted, and on a directory listing it showed the a file creatation date of 1856, that was one old file. Hmmm, wonder if VAXs are Y2K compliant. I also have a friend who wanted to test the Y2K bug on his machine, so he set the year to 1999 and forgot to restore it. All his email was dated 1999. PeterL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message