-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Sun, Jan 20, 2019 at 05:03:05PM -0600, Andrew David Wong wrote:
> What is the advantage of this?
>
> $ qvm-run --dispvm=work --service qubes.StartApp+firefox
This one will look for "firefox.desktop" in standard locations in target
qube and launch application described by it.
> Over this?
>
> $ qvm-run --dispvm=work firefox
This one will run "firefox" command directly.
For many applications the actual name will be the same, but there are
exceptions - for example Nautilus have org.gnome.Nautilus.desktop.
The practical difference is that bare qvm-run use qubes.VMShell service
and allow you to run arbitrary command with arbitrary arguments - so,
basically full control over the target VM. The qubes.StartApp service
allow you to run only applications advertised in /usr/share/applications
(or other standard locations), without control over the arguments - so
giving access to qubes.StartApp service is much safer thing to do.
While there isn't much practical difference when you do that from dom0,
it matters a lot if you start applications from non-dom0 - like from
the upcoming GUI domain.
> The behavior looks the same to me. As far as I can tell, none of our
> documentation mentioning qubes.StartApp explains this, and a search
> didn't turn up any relevant ML threads.
There is a brief documentation here:
https://www.qubes-os.org/doc/managing-appvm-shortcuts/#behind-the-scenes
But indeed it could be expanded.
- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlxFCe4ACgkQ24/THMrX
1yxWTgf+IUivAER7ONvnAUr8LmBdKx8+OLjkHWWfYMdK45qT3ubMgyah8KrXQxpk
IL4/qkdiZc6bq7XwCGKyEEU6FIViBJi8x/fBabeR18ePMoJoX2hfnARTWDD8EOSY
y2GaCp9iV5R1+Fr5FWFbHxBZb/K00me7jqxdTnQTuUFAX9Nsbp3mcsbB2qR20ZpJ
EJ1qUYKIW6Twn5YgCvjSR1khx97H82an8EBQddqbWQkiVUSmEMZV9/9BLugDeoZE
b0VinYjTj9wyoU3JZKVLrq7/8WxnPzkANz5BdOpNoMpIOmGW1dG1Y4KaMbnCUYBn
c6tiJOBNwpDegmr1MwkTl0M7JHmivg==
=mTcu
-----END PGP SIGNATURE-----