The other unixes demand system clokc in utc. It would be trivial to do the
same as the other unixes, but I bet that you would not like that solution
(kernel overwriting clock with utc).
Please don't claim others do better, when, in fact, they don't.
> because the kernel can not set the RTC, it can only read it (RTC driver
> excepted).
The kernel very well can set the rtc (it updates it regularly), it just
will not set the hour and date (because it can't).
> Wel, well. How do you explain that the system clock is still the same
> after having used "date -s" several times?
The system clock *is* updated by using date -s. You mean the RTC!
> cron job to update the RTC via hwclock hourly, or maybe update it
> during system shutdown?
That would be a very nice solution for your problem. Why bloat the kernel
with a problem that could be solved that easily in userspace?
> Also: The kernel can probably do the job more precisely than a user
> daemon. (I'm talking about fractional seconds)
No, it can't, because it doesn't know the timezone. And learning that
would require a dataset of over one megabyte in the kernel (talk about
compression..)
Let's drop this topic, I think it's clear that this all is out of the
question.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@opengroup.org |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/