This bug was fixed in the package clock-setup - 0.97ubuntu1
---
clock-setup (0.97ubuntu1) jaunty; urgency=low
* Resynchronise with Debian. Remaining changes:
- Default to ntp.ubuntu.com for the NTP server.
- Ask the UTC question, defaulting to true, even if we appear to be
Sorry for the multiple negatives. Actually I'm saying the exact
opposite: I'm saying that I would expect a Unix-like OS to keep the
hardware clock in UTC when no other operating systems are involved. At
the risk of belabouring the point, Unix-like operating systems simply
work better with the
Actually, while I've made the change in revision control, I'm going to
have to ask for more references, because I find it very unlikely that a
Unix-like system would default to keeping the hardware clock in UTC when
no other operating systems are involved; it's a terrible idea for
mission-critical
OK, though this is very surprising; typically, Unix-like operating
systems are happier keeping the hardware clock in UTC, since that
produces much more sensible results across DST changes. (The operating
system is better at managing this than the BIOS is, and trying to have
both of them manage it
If you're unfamiliar with the reasons why keeping the hardware clock in
local time is a bad idea, please read:
http://www.cl.cam.ac.uk/~mgk25/mswish/ut-rtc.html
--
The live CD installer should detect the presence of OpenSolaris
https://bugs.launchpad.net/bugs/279065
You received this bug
Colin thank you so much for the reference on the hardware clock! I do
appreciate having the bigger picture.
As for this statement: I find it very unlikely that a Unix-like system
would default to keeping the hardware clock in UTC when no other
operating systems are involved: I'm not sure I follow
