Thinking about backup procedures, some VMs carry large amounts of
transient data in places like ~/.cache. For a block-device incremental
backup system to exclude the data, the folder would have to be in a
separate volume such as vm-name-cache instead of vm-name-private. And
people seem to prefer block-device backups.
So having a "cache" class of storage volume for each VM makes sense from
this perspective.
I just wanted to post this idea to explore whether its worth exploring.
--
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
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 qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/54019754-816f-86a3-ca62-de87335f9c60%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
