Re: [LI] Linux on nonY2k compliant bios/motherboard?

[Raj Mathur <raju@xxxxxxx>]

Had a similar problem with a client in Goa (you figure out which one!)
-- he had a number of Winduhs boxen running on non-Y2K compliant
BIOS's.  The solution is elegant and simple: set up an NTP server in
your campus, and let the box (whether Winduhs or Linux) sync with that 
first thing after booting.  Then it doesn't really matter what date
the BIOS thinks it is, since the OS will have the correct date as soon 
as it boots.

As mentioned earlier, xntpd is part of stock RH Linux.  There are Duh
clients for NTP also available on the 'net.  Seek and thou shalt find.

Regards,

-- Raju

>>>>> "Atul" == Atul Chitnis <achitnis@xxxxxxxxxxx> writes:

    Atul> On Fri, 31 Dec 1999, aravind venkataraman wrote:
    >> Can linux run without problems on a pc withaa non y2k compliant
    >> bios or motherboard.

    Atul> Y2K issues come from three sources:

    Atul> - The system BIOS - The Operating System - The Applications

    Atul> Linux does not use the BIOS after booting. However, if the
    Atul> system date is wrong, Linux will get confused. This means
    Atul> that a system *running* Linux will rollover just fine, but a
    Atul> system booting after midnight today will have the wrong date
    Atul> since that is the date the system gives it on the initial
    Atul> boot.

    Atul> Linux itself is Y2K proof and has no issues - it does not
    Atul> care what the Y2K state of the machine is.

    Atul> Applications may or may not survive on such a machine,
    Atul> though that depends on whether the app queries Linux for the
    Atul> date, or the machine's hardware.

    Atul> In general, a non-compliant machine that has a fairly recent
    Atul> Linux distribution up and running at rollover time will
    Atul> survive.

    Atul> Atul
--------------------------------------------------------------------
The Linux India Mailing List Archives are now available.  Please search
the archive at http://lists.linux-india.org/ before posting your question
to avoid repetition and save bandwidth.