Bug#541436: Bug541436: clock-setup: should not change hardware clock if the system time is not updated

[Frans Pop <elendil@planet.nl>]

tags 541436 pending
thanks

My analysis was not entirely correct (or actually quite wrong in some 
respects). The timezone in the D-I environment was not the issue as the 
correct timezone _is_ known in the chroot where we run hwclock.
So as long as the system time in the D-I environment is set to UTC (which 
it will be if rdate is run), then the time in the target chroot should be 
correctly corrected to local time and hwclock will have the correct 
reference time.

The main issue was that we did not let hwclock know correctly whether the 
clock was to be set to UTC or local time as the file /etc/adjtime does 
not yet exist when we try to modify it.

I hope that my changes will have made setting the clock more reliable now. 
I cannot be 100% sure as I only tested it in an emulator, not on real 
hardware.

Cheers,
FJP