Re: hwclock
--On Friday, June 09 2000, 08:40:18 Christian T. Steigies cts@debian.org
wrote:
>On Fri, Jun 09, 2000 at 12:58:01AM -0500, JAG wrote:
>> hwclock --systohc command doesn't seem to work...
>>
>> here is the syntax i use to change the time:
>>
>> date 0609125000
>>
>> that works fine. But whn I reboot, the time reverts back to the incorrect
>time.
>>
>> So I tried
>>
>> hwclock --systohc
>>
>> and i get
>>
>> mktim () failed unexpectedly (rc-1) Aborting.
>>
>> Debian Slink 2.1
>> Mac SE/30 32 megs ram
>Aiee... if you said Amiga, I would understand it. Macs also have a y2k
>problem? Was discussed in dec99/jan00 on linux-m68k. I think people agree on
>a fix in the kernel, but AFAIK nobody bothered to implement it yet.
>Or was it a y2k bug in hwclock _and_ in the kernel? I don't remember, please
>search the archives.
AFAIK, macs don't have a y2k problem. And even on an SE/30, I think the clock
should last until 2038 or so. I can't remember when they switched from 32bits
to 64bits...
-Jan
Reply to:
- Follow-Ups:
- Re: hwclock
- From: Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de>
- References:
- hwclock
- From: JAG <jag@jagshouse.com>
- Re: hwclock
- From: "Christian T. Steigies" <cts@debian.org>