Dear M,
You are indeed correct - that solved the mystery, and I sincerely appreciate a real developer like you taking the time and making the effort to allow someone like me to use your distro.
Now, with that fixed, everything works, period.
For the record, in case anyone googles this, the install from zero to full flash, java, 3d accel, network, and all codecs working in browsers, is, on my 2.16g pentium m, is only twenty-seven minutes. (not including the dreadful kde install, which takes of course, at least half an hour.
In short, a distro where everything just works out of the box, with the one exception we have just repaired, which is only a problem for those of us outside of central europe ;).
With much gratitude,
M
On Sun, 2006-04-23 at 11:20 +0200, Michael Prokop wrote:
- my yazdzik@nyct.net [20060423 05:15]:
In an attempt to retrace the whole install, I took the following actions while still in grml live-
- tzconfig to America/New_York
date revealed the local time, EDT, to be five hours earlier than UTC, and showed as well UTC as being the value obtained from my hw clock, which is, of course, set to local time.
- clean reboot, using tzselect with posix value set as "NYC-0", date
revealed local time to be CEST and utc to be what my hw clock says.
Ok.
Thinking about this rationally, this can only mean that the live disk reports the hw clock as being UTC and there appears to be no way to tell it that this laptop BIOS is set to local time.
On the debian installer, for instance, it asks at install if the hw clock is set to utc. This is an urgent need, as there was some dreadful workaround in kanotix, which was also a pain.
Thus, the grml2hd needs one or two more questions, perhaps something like "is the bios clock set to utc?" and something like "location" as many config files set the locations as at.
In other words two things have to happen at hd install:
- location has to be set as where it is, not at
- we have to be able to tell the install that the BIOS clock settings
are either UTC or localtime.
On Debian systems you can set/unset UTC in /etc/default/rcS. But this should be fine for you already.
I've one further idea: Can you please set CONFIG_TIME and CONFIG_TIMEZONE to 'no' in /etc/grml/autoconfig and retry it again then. After rebooting does it work for you as requested? If that works for you I think I found a way to handle it.
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/
"...children and young people feel instinctively the difference between those who genuinely wish them well and those who regard them merely as raw material for some scheme." --Russell
