Hello,
After reboot, the system time is always incorrect. How to adjust it? Thank you!
On Mon, Mar 19, 2007 at 11:18:02AM +0800, coscell@mail.batol.net wrote:
Hello,
After reboot, the system time is always incorrect. How to adjust it? Thank you!
After setting the time locally, run hwclock --systohc
as root. This will update your system's BIOS clock to the current GMT time (08:23 at the moment)
* coscell@mail.batol.net coscell@mail.batol.net [20070319 05:15]:
After reboot, the system time is always incorrect. How to adjust it? Thank you!
Please notice that on your system $TZ is set in /etc/default/locale. grml-setland and the corresponding shell configuration have been adjusted for /etc/timezone only in the current Debian packages available in grml-testing pool.
regards, -mika-
On Mon, Mar 19, 2007 at 09:39:43AM +0100, Michael Prokop wrote:
- coscell@mail.batol.net coscell@mail.batol.net [20070319 05:15]:
After reboot, the system time is always incorrect. How to adjust it? Thank you!
That page reports
If you change the time (using 'date --set ...', ntpdate,...) it is worth setting also the hardware clock to the correct time: # hwclock --hctosys [--utc]
However man tzconfig states --hctosys Set the System Time from the Hardware Clock.
Which loads the time from hardware. Am I missing something? Shouldn't this read --systohc?
* Paul Weaver iso@isorox.co.uk [20070319 10:02]:
On Mon, Mar 19, 2007 at 09:39:43AM +0100, Michael Prokop wrote:
- coscell@mail.batol.net coscell@mail.batol.net [20070319 05:15]:
After reboot, the system time is always incorrect. How to adjust it? Thank you!
That page reports
If you change the time (using 'date --set ...', ntpdate,...) it is worth setting also the hardware clock to the correct time: # hwclock --hctosys [--utc]
However man tzconfig states --hctosys Set the System Time from the Hardware Clock.
Which loads the time from hardware. Am I missing something? Shouldn't this read --systohc?
Ouch, of course - yes. Thanks for pointing, fixed.
regards, -mika-
Dear Friends,
We may be making a false assumption that the original writer's bios clock is set to GMT. If not, setting it to GMT will make chaos for dual booting windows. For someone new to the grml way of doing things, one should note that during the original install, when asked for a language, the default setting US english leaves the time zone as austria(cet). One must, for example, in NY choose on of the us english settings at the bottom of the list, and so on.
If this be a dual boot system, and the clock is set to local time, leave it and use the grml-setlang command, which sets the locale, or, if one need an setup which is not in the locales provided, one can edit /etc/default/locale manually. Obviously, Mika did not set up locales there for someone speaking us english located in Kenya, or Japanese located in NYC, but these things exist, and living here in NYC, I see locales with "non-corresponding" time zones every day.
(yes, I did indeed use grml to set up a friends 'locale farsi, tz new york" laptop a few days ago ;) - welcome to new york....)
Best, m
On Mon, 2007-03-19 at 10:05 +0100, Michael Prokop wrote:
- Paul Weaver iso@isorox.co.uk [20070319 10:02]:
On Mon, Mar 19, 2007 at 09:39:43AM +0100, Michael Prokop wrote:
- coscell@mail.batol.net coscell@mail.batol.net [20070319 05:15]:
After reboot, the system time is always incorrect. How to adjust it? Thank you!
That page reports
If you change the time (using 'date --set ...', ntpdate,...) it is worth setting also the hardware clock to the correct time: # hwclock --hctosys [--utc]
However man tzconfig states --hctosys Set the System Time from the Hardware Clock.
Which loads the time from hardware. Am I missing something? Shouldn't this read --systohc?
Ouch, of course - yes. Thanks for pointing, fixed.
regards, -mika- _______________________________________________ Grml mailing list - Grml@mur.at http://lists.mur.at/mailman/listinfo/grml join #grml on irc.freenode.org grml-devel-blog: http://grml.supersized.org/
* martin yazdzik yazdzik@nyct.net [20070319 13:15]:
We may be making a false assumption that the original writer's bios clock is set to GMT. If not, setting it to GMT will make chaos for dual booting windows. For someone new to the grml way of doing things, one should note that during the original install, when asked for a language, the default setting US english leaves the time zone as austria(cet). One must, for example, in NY choose on of the us english settings at the bottom of the list, and so on.
If this be a dual boot system, and the clock is set to local time, leave it and use the grml-setlang command, which sets the locale, or, if one need an setup which is not in the locales provided, one can edit /etc/default/locale manually. Obviously, Mika did not set up locales there for someone speaking us english located in Kenya, or Japanese located in NYC, but these things exist, and living here in NYC, I see locales with "non-corresponding" time zones every day.
Martin, thanks for noting that. Are you happy with http://grml.org/faq/#timezone or is anything missing there which might be useful for users of grml? Do you miss anything inside grml-setlang/grml2hd which might improve the situation? Any patches againgst the documentation (and of course against sourcecode in general ;)) are highly appreciated from my side, because it's not that easy to write documentation for users from developers side of view.
regards, -mika-
participants (4)
-
coscell＠mail.batol.net -
martin yazdzik -
Michael Prokop -
Paul Weaver