Existing users should first remove the old submodule files, and move the
nmtrust config files to their new location:
# rm /usr/local/bin/nmtrust
# rm /usr/local/bin/ttoggle
# rm /etc/NetworkManager/dispatcher.d/10trust
# mkdir /etc/nmtrust
# mv /usr/local/etc/trusted_* /etc/nmtrust/
While debugging a clock issue I noticed that my RTC was out of sync.
Clearly this should be impossible, since any NTP implementation will
periodically set the hardware clock to the system clock. Except, for
reasons that I entirely fail to grok[1], systemd-timesyncd.
So I am disabling that pile of junk and replacing it with an NTP
implementation that actually meets the bare requirements of an NTP
implantation. I could be convinced to replace this with OpenNTPD.
Existing users should first disable the pile of junk before upgrading to
chrony:
$ sudo timedatectl set-ntp false
Chrony is started in offline mode, and is told to attempt to communicate
with the pools via a NetworkManager dispatcher. I considered plugging
this in to nmtrust, as part of my campaign to minimize traffic on
untrusted networks, but this seems likely to be overkill. I could be
convinced otherwise.
Chrony's dial-up configuration[2] is attractive and may be worth
implementing. My inclination is that in the current setup with the
normal NetworkManager dispatcher, most spark clients will be online
frequently enough that setting system time by tracking RTC drift is
unnecessary. If the dispatcher is changed to plug into nmtrust, the
drift-tracking configuration becomes much more attractive -- when on the
road, a machine may not connect to a trusted network for weeks. I could
be convinced otherwise.
Chrony is configured to use the same Arch vendor pools as were used by
systemd-timesyncd. I am unsure if we should specify these by IP rather
than hostname, if there are better or smarter defaults we should
provide, or if it worth making the pools a configuration option.
[1]: https://lists.freedesktop.org/archives/systemd-devel/2011-May/002526.html
[2]: https://chrony.tuxfamily.org/manual.html#Dial_002dup-overview
Note that this is only supported for grub. That is the only bootloader I
use. Patches for other bootloaders will be accepted.
The default params:
* quiet the boot process
* cause all virtual terminals to blank (ie, screen power off) after 60 seconds
* enable panel self refresh v2
Blanking the screen is useful with physlock. Physlock does not run in X,
so DPMS settings have no effect on it.
PSR can potentially improve battery life on some machines, but cause
screen flicker on others. I have happily been using v2 on a ThinkPad
X260 for 6 months, but users should experiment between 1/2/3/4 to find
the best setting for their machine, or disable it entirely with 0. See:
* https://hansdegoede.livejournal.com/18653.html
* https://patchwork.kernel.org/patch/8182841/
Starting macchiato here brings down the network connection for a couple
seconds, which will cause subsequent network dependent tasks to fail.
Start the service with a handler after everything else is done.
When we started this project vdirsyncer/khard/khal was a mess of AUR
dependencies that I didn't want to deal with. Everything has official
packages now.
Existing users should remove the old virtualenv and symlinks.
$ sudo rm -r /usr/local/env/pim
$ sudo rm /usr/local/bin/khard
$ sudo rm /usr/local/bin/khal
$ sudo rm /usr/local/bin/vdirsyncer
Both GDM and GNOME uses DConf to manage its own configuration. Extract
the common dependencies into a separate role called "dconf".
DConf provides:
- creating empty directories for configuration
- handler to apply configuration when configuration has changed
Add ability to install the GNOME desktop environment.
Most common global settings (date and time, power management, touchpad settings, theme) can be configured via Ansible variables.
See "group_vars/all" file.
