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?
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. > 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? -- Thanks for your response, Zaz -- 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/87qzvp60p9.fsf%40localhost.
