On Mon, 29 Sep 2025 09:57:10 +0000 'Zaz Brown' via qubes-devel wrote: > I thought /etc/skel/ copies its files to the VM only when the VM is > first created? After that, if you make updates to files in /etc/skel/, > they are not propagated to the AppVMs, right?
That's my understanding too. > Furthermore, this duplicates storage. So if you wanted to share, for > example, a large program installed via pip or some other non-system > method, to all AppVMs, this could take up a lot of space, and keeping it > up to date across all AppVMs could be a pain. If you want it in all AppVMs, up-to-date and always-synced, the answer is pretty straightforward: Install it in the template. Even if the particular installation method installs in /rw, you can still move the destination to e.g. /root and symlink to it (in the template and in the AppVMs as well), so nothing will need to be duplicated at any time. > > Another possible approach might be to use /usr/local/etc for > > AppVM-specific config, however the particular app must be made to > > support that. > > Isn't this solving a different problem? Per-AppVM-specific config rather > than config shared across all AppVMs? I thought you were trying to solve both. In case /usr/local/etc has no config, the app will look upstream (in /etc). -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/qubes-devel/20250929170904.21f22ca5%40localhost.
