Heya,
On 27.09.2011 22:07, Bill Nottingham wrote:
Chris Lumens (clumens@xxxxxxxxxx) said:
systemd whenever it changes /etc/localtime will also write
/etc/timezone to the right value. All I am asking here is that
anaconda as the initial tool that writes /etc/localtime does the
same.
Under which circumstances does systemd change /etc/localtime?
When it's told to, essentially.
Is this
something anaconda can just call so that /etc/timezone also gets written
out? We've pretty thoroughly bought into using systemd in the
installation environment, so we could conceivably just call into
whatever you're doing already.
There's a small dbus-activated service that runs; you call SetTimezone()
on it with the timezone you want. Similarly for NTP, locale, hostname, etc.
This should be pretty easy to frob in the running install environment; less
easy to do in the install root, as the service wouldn't be running there.
Is this currently done:
1) only in the install env (and then copied to the install root)
2) only in the install root
3) in both the install env and the install root separately
This is an interesting question: the mechanisms are bus activated, and
hence probably not fun to use from outside of the actual system. If the
anaconda firstboot stuff is the only code needing this functionality it
would make a lot of sense to use these mechanisms only after the first
boot into the actual system.
Lennart
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
