Per Jessen
Per Jessen wrote:
Is this really a hard error?
I feel fairly certain I can reproduce it although I've now started over after having adjusted the hwardware clock.
Well, I've now tried to repeat the exercise on the initial system as well as another one just like it - but I can't reproduce the situation. I suspect that something happened when the "time in the past" situation was discovered that then made it impossible to change the hardware clock. How does YasT determine that "time is in the past"?
I don't know :-( I just tried to reproduce it on my laptop with setting date to "1988-01-01" but my BIOS rejected this date (stopped at next boot and ask me to check date and time) :-( Then I tried 2001-01-01 which my BIOS allowed and did a new installation and got the message you described. But I could change the time to 2004-12-31 without problems. If you - or anybody can reproduce the situation (that it's not possible to change the time), please tar together /var/log/YaST and sent it to me *privately* and I'll file a bugreport, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126