On 01/31/2017 02:24 PM, mojosam wrote: >> it does protect you from user errors. e.g.: >> you have some malicious pdf in a vm. >> if you have noting to open the pdf, you can't accidentally open it and >> corrupt your vm. > Isn't that the concept behind "attack surface"? If the code is there, > something malicious might have the ability to call it. I think there was > malware that was recently discovered that could exploit the floppy disk > controller in either VMware or VirtualBox. > > The bigger practical concern is that PlayOnLinux expanded my template by 800 > MB. Is all of that cruft duplicated on the hard drive for every VM, or is it > just accessed from the template as needed when the VM is activated? > Accessed from the TemplateVM from the AppVM if needed, assuming all of your AppVMs are based on the same TemplateVM and PlayOnLinux installed it in the root partition. Clearly, it needs to do so when you first install the package, but all of your programs that you install in Wine including different Wine versions, libraries, etc once you start the PlayOnLinux client all get stored in /home/user/.PlayOnLinux and those are only accessible through the AppVM that you launched it from. A different AppVM based on the same TemplateVM wouldn't be able to access those apps unless you were to reinstall them on the new AppVM as well.
-- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/o6r071%24a45%241%40blaine.gmane.org. For more options, visit https://groups.google.com/d/optout.
