Rusty Bird wrote: Everything in /etc/skel/ on the TemplateVM is copied to /home/user/ on VM creation, e.g. /etc/skel/.config/gtk-3.0/settings.ini (although for this specific case you could just use /etc/gtk-3.0/settings.ini which would also apply to existing VMs, not just newly created ones).
Is there a sane way to update existing `*.conf` files on VMs that are already running?
For example, I have installed new software in a Template that is used by several VMs. I would like a default look and feel across all of the VMs when I use the new software but the software stores its configuration in `~/.config/.......`
I can put the default configuration in `/etc/skel/.config/.......',which will apply to newly created VMs, but this will not apply to already created and running VMs.
Is there a not-so-labour-intensive way to solve this problem? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0cf4e184-f257-6937-84b9-dbcf62ba74af%40ak47.co.za.
