On Wed, Jul 29, 1998 at 08:18:36AM -0700, Alexander wrote: > Hi... > > Linux has no Y2K issues aside from the BIOS. It's that simple. However, > sometime in the 2030s, it will have some time_t problems if not fixed by > then. They should be, although you will probably need to upgrade your > embedded system if you want it to keep running after then.
actually...as I remember its 2038...and once it is fixed we will be good for another 2 million years I think. hmm... think that rembedded system will be used 2 million years form now? AFAIK its just a matter of changing time_t to a 64 bit integer (instead of 32 bit) and recompiling everything that uses it... actually...BTW there are (or were) some Y2K issues in linux applications. I know as shipping hamm has 1 in some cvs package...but thats the last one. It only really will effect databases which store dates in their own way -Steve > Alex > > On Thu, 23 Jul 1998, Rick Fadler wrote: > > > > > Hi, > > > > I'm assuming with all the year 2000 compliance hype that there > > must be a document somewhere describing the year 2000 issues > > related to specific Debian releases of linux. > > > > Specifically, we have built an embedded system using Debian > > version 1.3. Being an embedded system, we've stripped out most of > > the utilities and standard packages. We now need to verify that > > our system is year 2000 compliant. > > > > Does anyone have any information on this? > > > > Rick Fadler > > NetLeaf, Inc > > [EMAIL PROTECTED] > > 425-643-9610 > > > > > > -- > > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > > > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > -- ** Stephen Carpenter ** ** ** ** ** ** ** ** ** ** ** ** [EMAIL PROTECTED] ** "All authority is quite degrading." -- Oscar Wilde
pgpXTRarZwmQ8.pgp
Description: PGP signature
