> So to clarify:
>
> > Sys-net and sys-firewall (and sys-vpn if you use it) will need it enabled.
>
> When you say "need it enabled", you're just referring again to "provides
> network", is that correct?
>
Yes.
> And secondly: Do I understand correctly so long as any qube sits in between
>
> On 1/20/20 3:09 PM, tortuga verde wrote:
>
> > Also, since it was not listed in systemctl status, how would I be able
> > to easily enumerate all such services, so that if I want to see if any
> > service is running because I failed to disable it at install time, I can
> > find and disable
> Hello,
>
> I was wondering if there are guides in the docs that I missed which
> describe proper creation/upgrades of "special" VMs (sys-net, sys-firewall,
> and possibly vault). I preferred Debian for my vault. I created a new VM with
> a
> black lock icon and no network connectivity. Other
> > I've a question about the Qubes default desktop setup. Basically, the
> > latest Qubes is running XFCE desktop environment, but I've noticed
> > certain default programs are actually from Gnome.
> >
> Dom0 uses xfce but the templates use Gnome.
Qubes offers a fedora xfce template.
> I've a question about the Qubes default desktop setup. Basically, the
> latest Qubes is running XFCE desktop environment, but I've noticed
> certain default programs are actually from Gnome.
>
Dom0 uses xfce but the templates use Gnome.
> I did a quick test installing Thunar and it seemed to
> > $ sudo qubes-dom0-update redshift-gtk
> >
> > The dnf command is only used for removing packages.
> >
>
> do you invoke it from command line? if so, may I ask with what command
> argument ?
>
I invoke it via the session and startup preferences in system tools, so it
loads every
time
>
> so $sudo dnf install redshift-gtk ?
>
> seems to not be the package name , hmm
>
$ sudo qubes-dom0-update redshift-gtk
The dnf command is only used for removing packages.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe
> I installed Kali Linux (as a non template vm) and in the qubes setting for
> this Kali it says:
>
> default dispvm template has a different networking setting than this qube,
> unexpected network access may occur
>
> what should I do in Kali for it to work?
>
DispVMs inheret their network
> On 9/18/19 2:43 PM, unman wrote:
> >> today I had a look in logs of my router, and discovered that it logs my
> >> qubes machine as "sys-net". I did not change anything in my
> >> "out-of-the-box" sys-net, so I presume that the observed behaviour is
> >> common to all standard qubes installs.
>