I've just spent about an hour configuring a new install - I wanted a fairly small footprint. Now that I'm ready to go, yast tells me "Time is in the past - please correct it". I try to correct it, but it has no effect. Seriously, this p...... me off. What does YasT care about the time? (never did before) - and I don't care anyway, it will be set via NTP when the box is up. Assuming I'll have to set the time via the BIOS setup, I'm now stuck with having to start over, customizing the config etc - at least another hours worth of work. Where's the YasT override for this sort of idiotic sillyness?? /Per Jessen, Zürich -- http://www.spamchek.com/freetrial - managed anti-spam and anti-virus solution. Sign up for your free 30-day trial now!
On Sat, 2005-07-16 at 12:26 +0200, Per Jessen wrote:
I've just spent about an hour configuring a new install - I wanted a fairly small footprint. Now that I'm ready to go, yast tells me "Time is in the past - please correct it". I try to correct it, but it has no effect. Seriously, this p...... me off. What does YasT care about the time? (never did before) - and I don't care anyway, it will be set via NTP when the box is up. Assuming I'll have to set the time via the BIOS setup, I'm now stuck with having to start over, customizing the config etc - at least another hours worth of work. Where's the YasT override for this sort of idiotic sillyness??
Try using the date command to set the date. man date for how to set the date/time. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
Try using the date command to set the date. man date for how to set the date/time.
Right. On a yet-to-be-installed system? I've now started over after having set a new time (only 2 hours off) via the BIOS setup. It would be nice if someone could explain : 1) why does YasT care about what time the system is running? (especially when it never did before) 2) how does YasT determine that time is in the past?? 3) why didn't YasT change the time when I entered a new time? /Per Jessen, Zürich
On Sat, 2005-07-16 at 13:10 +0200, Per Jessen wrote:
Ken Schneider wrote:
Try using the date command to set the date. man date for how to set the date/time.
Right. On a yet-to-be-installed system?
Then set it in the bios before install. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
Then set it in the bios before install.
Ken, that is what I was trying to _avoid_ after I'd spent a good hour adjusting the install config. Had I known about this sillyness, I would _obviously_ have adjusted it before I started. /Per Jessen, Zürich
On Saturday 16 July 2005 07:15 am, Per Jessen wrote:
Ken Schneider wrote:
Then set it in the bios before install.
Ken,
that is what I was trying to _avoid_ after I'd spent a good hour adjusting the install config. Had I known about this sillyness, I would _obviously_ have adjusted it before I started.
/Per Jessen, Zürich
On the same install screen where you select the time zone (very early in the install and before software selection) you CAN change the time on your clock... there is a button on the bottom to allow this. Did you try that?
Bruce Marshall wrote:
On the same install screen where you select the time zone (very early in the install and before software selection) you CAN change the time on your clock... there is a button on the bottom to allow this. Did you try that?
Yep, tried that - it doesn't work. /Per Jessen, Zürich
Per Jessen
I've just spent about an hour configuring a new install - I wanted a fairly small footprint. Now that I'm ready to go, yast tells me "Time is in the past - please correct it". I try to correct it, but it has no effect.
How did you try?
Seriously, this p...... me off. What does YasT care about the time? (never did before) - and I don't care anyway, it will be set via NTP when the box is up. Assuming I'll have to set the time via the BIOS setup, I'm now stuck with having to start over, customizing the config etc - at least another hours worth of work. Where's the YasT override for this sort of idiotic sillyness??
You can change the time in the timezone dialog. Is this really a hard error? 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
Andreas Jaeger wrote:
Per Jessen
writes: I've just spent about an hour configuring a new install - I wanted a fairly small footprint. Now that I'm ready to go, yast tells me "Time is in the past - please correct it". I try to correct it, but it has no effect.
How did you try?
When I change the install config - select timezone (which is also where the error was displayed) - change Time & Date - alter hour (I added 2 hours) - then Apply. No effect.
You can change the time in the timezone dialog.
Well, no, I can't. See above.
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. /Per Jessen, Zürich
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"? /Per Jessen, Zürich
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
Andreas Jaeger wrote:
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.
Ah, maybe I need to try that - when I first saw the problem, the clock was only a couple of hours off - maybe I need to try it with a year or two :-)
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,
Willdo. Thanks. /Per Jessen, Zürich
----- Original Message -----
From: "Silviu Marin-Caea"
On Sunday 17 July 2005 13:58, Andreas Jaeger wrote:
How does YasT determine that "time is in the past"?
I don't know :-(
Maybe it tests if the computer time is set before the date 9.3 was released?
Files have time stamps
participants (6)
-
Andre Venter
-
Andreas Jaeger
-
Bruce Marshall
-
Ken Schneider
-
Per Jessen
-
Silviu Marin-Caea