fli4l - Base - OPT_Y2K

Package BASE
OPT_SYSLOGD | OPT_KLOGD | OPT_PNP | OPT_Y2K

##### :::[ OPT_Y2K ][ Y2K_DAYS ]:::

#### OPT_Y2K - date correction on not-Y2K-compliant computers

In most cases FLI4L routers are built from old hardware parts. This implies, that sometimes non-Y2k-compliant BIOSs are used. That is the case in my 486 PC: when I set the date: 27.05.2000 in the BIOS, I will see 27.05.2094 after next boot-up! By the way - Linux shows: 27.05.2004 ! :-)

Under normal circumstances you may not care about the date of your FLI4L router. But - if you want to use it as a least-cost-router, it IS important !

Reason: The 27. of May in 1994 was a Friday, the 27. of May in 2000 was a SATURDAY. That means: Saturday is much cheaper to surf than Friday.....

The solution for FLI4L is as follows:

I set the BIOS date on 27.05.2000 to 27.05.1994. That WAS a Saturday. The problem was solved..

But....it was the WRONG date. FLI4L not only uses informations about day-of-the-week and time for least-cast-routing, but also holidays.

##### [ top ]

#### Y2K_DAYS (add N days to system date)

Since the date I gave in differs from actual date by 2191 days, there will be an addition of 2191 days when the following is set:

    Y2K_DAYS='2191'

After this the Linux date will be set. BIOS date remains unchanged, because - after next boot-up - it would be set again to 2094 (or: 1994). ;-)

Alternatively you may do the following:

Accessing a time server will enable FLI4L to get the actual date and time from the internet. From version 1.4 there is an additional package included which enables this function (OPT_TIME). Both settings may be combined. That may be useful: first correct date with Y2K_DAYS and then set time by using a time server.

When you donīt have any problems with Y2k: set variable OPT_Y2K to 'no' and forget about it.....

##### [ top ]

» To documentation «