[wplug] y2k workaround

[Keir Josephson]

If you have a network connection at boot time, you could try polling the
current date from an ntp server at run-level 1. Or, if your network
connection comes up to late in the game, you can just set a simple date
command that sets the date 6 months or a year in advance then reset the
date once you get to a prompt. Just remember to update it before you pass
the preset time.

-Keir

On Wed, 10 Apr 2002, redtoade wrote:

>I've been lurking for a few months... and its time I
>asked my first question:
>
>Setup:  486/66 that I've been using as a
>firewall/gateway.  16M RAM.  RedHat 6.2.  (Why? 
>Because it's a pain in my butt to try to get Slackware
>to reckognize two ISA eth cards using the same
>SMC-Ultra mod.  Plus Bastille works better on
>RedHat.... unfortunately RedHat 7.0 and beyond
>requires 32M of memory to install... and memory for
>these legacy boards costs more than buying a new
>computer).
>
>Problem:  Bios on board isn't Y2K compliant.  Which
>means when I reboot, 2002 dates become 1993 dates.  My
>logs go haywire.
>
>Desired Solution:  I would like to store the current
>date on my system somewhere, and update it every 15
>minutes or so... and when a shutdown command is
>issued.  Then upon reboot add 10 minutes (based on
>average restart time) and set the system clock to this
>date PRIOR to doing ANYTHING else.... that way my logs
>won't show any 1993 dates... and they'll be in the
>ballpark.  I would then ntpdate to the correct time
>once eth0 is brought up.
>
>Any ideas how to go about doing this?  Or is there a
>better solution?
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! Tax Center - online filing with TurboTax
>http://taxes.yahoo.com/
>_______________________________________________
>wplug mailing list
>wplug at wplug.org
>http://www.wplug.org/mailman/listinfo/wplug
>