Le 20 oct. 08 à 04:05, Michael Schmitz a écrit :
Hi,
I don't know "how", but with 2.2 kernels I always had a correct
date
at boot without any tricks. It is true though that with high CPU
load
we had clockskew and that we didn't save back the date and
hourtime to
the clock, thus any clock setting needed to be done from the mac
side.
A compromoise, but better than the current situation.
IIRC the booter passed the current date to the kernel, and this date
was used to initialize the system clock.
It isn't a problem if you disable the time-stamp triggered fsck
and set
the clock from the network (rdate or ntp).
This is the answer I keep getting, but it isnt really helping.
* SSL/TLS and certificate validation. For example my gumtix uses
802.1X to
get online, when it is running in "1970-01-01", the server and client
certificates are ofcourse not valid and the authentication _will_
fail,
and it wont go online, and therefor no ntp. As .1x is becoming more
common
Valid point. I gues penguin still does pass the date, so the problem
boils down to 'why isn't it used by the kernel?'
EMILE passes the date too.
Regards,
Laurent
----------------------- Laurent Vivier ----------------------
"The best way to predict the future is to invent it."
- Alan Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
