Am 14.06.2013 21:11, schrieb John Stultz:
On 06/14/2013 09:52 AM, Alexander Holler wrote:
Those config options don't make sense anymore with the new hctosys
mechanism introduced with the previous patch.
That means two things:
- If a (hardware) clock is available it will be used to set the
Am 14.06.2013 21:11, schrieb John Stultz:
On 06/14/2013 09:52 AM, Alexander Holler wrote:
Those config options don't make sense anymore with the new hctosys
mechanism introduced with the previous patch.
That means two things:
- If a (hardware) clock is available it will be used to set the
On 06/14/2013 09:52 AM, Alexander Holler wrote:
Those config options don't make sense anymore with the new hctosys
mechanism introduced with the previous patch.
That means two things:
- If a (hardware) clock is available it will be used to set the time at
boot. This was already the case for
Those config options don't make sense anymore with the new hctosys
mechanism introduced with the previous patch.
That means two things:
- If a (hardware) clock is available it will be used to set the time at
boot. This was already the case for system which have a "persistent"
clock, e.g.
Those config options don't make sense anymore with the new hctosys
mechanism introduced with the previous patch.
That means two things:
- If a (hardware) clock is available it will be used to set the time at
boot. This was already the case for system which have a persistent
clock, e.g. most
On 06/14/2013 09:52 AM, Alexander Holler wrote:
Those config options don't make sense anymore with the new hctosys
mechanism introduced with the previous patch.
That means two things:
- If a (hardware) clock is available it will be used to set the time at
boot. This was already the case for
6 matches
Mail list logo
