[Fedora-livecd-list] UTC?

wbsec.flive at new.rr.com wbsec.flive at new.rr.com
Wed Jan 25 02:40:16 UTC 2012

Where in the kickstart process should adjtime be modified? After booting up, doing this doesn't seem to have an effect, even after logging out and back in again. As a temporary workaround, we're setting it to use network time, but that's less than ideal as the time is off until someone connects to their wireless network. The adjtime test was done prior to connecting to a network.

This is for approximately 500 people to work from home, ranging from on occasion to daily; having them change their BIOS clocks to UTC, and arguing the merits of this despite what it does to their windows installs and daylight savings time changes isn't really going to fly. It's a livecd/usb for the reasons of simplicity and co-existence.

Also, is it possible to force fallback mode for gnome3 in a livecd kickstart file? Gnome3 really breaks a lot of things that users have come to rely on since the early 90's, like being able to power off, minimize/maximize/restore, alt-tab between windows properly, clicking on an app launches an instance of the app ALWAYS rather than sometimes, etc.. Or is there a way, in the .ks file, to put these behaviors back? These factors are a real hindrance to adoption.

---- Jerry Vonau <jvonau at shaw.ca> wrote: 
> On Wed, 2012-01-18 at 13:20 -0500, wbsec.flive at new.rr.com wrote:
> Hi,
> Fedora 16 (unlike F15 and before) seems to assume that the hardware clock is 
> set to UTC, which definitely isn't the case with the occasional livecd user.  
> The average user is inclined to go to the top and change the time, which then 
> changes the hardware clock, and throws Windows off.

See some background at:

> Anyone know how to fix this within the .ks file, versus a user making a change?

echo LOCAL >> /etc/adjtime
echo UTC >> /etc/adjtime
as needed.


livecd mailing list
livecd at lists.fedoraproject.org

More information about the livecd mailing list