something should confirm that the current time is accurate
Bug #7175 reported by
Mark Shuttleworth
This bug affects 32 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
The default install mode of Warty is to take over the machine. We can decide
ourselves that the policy is for the hardware clock to reflect GMT, and set it
accordingly. This question is not needed.
Later, we can try ntpdate to set the date using known-good network services. And
failing that, we can ask the user to confrm the local time if we want to make
sure that is accurate, when we set the timezones would be a good idea.
Changed in clock-setup: | |
assignee: | kamion → nobody |
Changed in ubiquity: | |
assignee: | nobody → droppedmyoreo |
assignee: | droppedmyoreo → nobody |
Changed in ubiquity (Ubuntu): | |
assignee: | nobody → AMIT KUSHWAHA (amitkushwaha) |
Changed in ubiquity (Ubuntu): | |
assignee: | AMIT KUSHWAHA (amitkushwaha) → nobody |
To post a comment you must log in.
base-config (2.35ubuntu6) warty; urgency=low
* Colin Watson
- tzsetup: Drop priority of tzconfig/gmt question (#415).
- lib/menu/timezone: Stop telling tzsetup to default to non-UTC. This
means that we'll take our default from rcS in initscripts instead,
which sets UTC=yes (#415).
-- Colin Watson <email address hidden> Thu, 29 Jul 2004 14:52:20 +0100
I'm leaving this bug open as an enhancement request to confirm that the current
time is accurate, using ntpdate or otherwise as you mentioned.