On Sat, Mar 10, 2018 at 11:59:29PM +0100, 799 wrote: > Hello, > > On 10 March 2018 at 22:52, 'MirrorWay' via qubes-users < > qubes-users@googlegroups.com> wrote: > > > You can probably simplify this by basing it on named dispvms. > > That way you don't have to keep an xterm open somewhere, nor do you need > > to extract the dispvm name from Xwindows. > > Just restart the dispvm after you close the app. > > > > For example, assuming disp-untrusted is already running: > > $ qvm-run -p disp-untrusted firefox ; qvm-shutdown disp-untrusted ; > > qvm-start disp-untrusted > > -p above causes the qvm-run to block until you close firefox. Then it > > restarts the named dispvm, which stays running until the next launch > > request. > > > > > I've tested your suggestion, unfortunately this will not work like a normal > disposable VM. > I have downloaded an HTML-page in the disp-untrusted VM and when it gets > closed and started the next time, the file is still there. > This means it doesn't behave like a real disposable VM. >
Change your template - base it off a -dvm, and it *will* work like a 3.2 disposableVM. You can supplement this by cycling through a number of named disposableVMs, so you can at least open a few at once. -- 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/20180310232310.tm56qm623iu3s2ji%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
