On Friday, March 1, 2019 at 3:54:12 AM UTC+8, awokd wrote:
> Sphere:
> > On Thursday, February 28, 2019 at 11:57:22 AM UTC+8, awokd wrote:
> >> Sphere:
> >>
> >>> Making it seem like my sys-net has been set as the updateVM for my
> >>> fedora-29 template
> >>>
> >>> I haven't tried updating my
Sphere:
On Thursday, February 28, 2019 at 11:57:22 AM UTC+8, awokd wrote:
Sphere:
Making it seem like my sys-net has been set as the updateVM for my fedora-29
template
I haven't tried updating my other templates yet but performing a
"qubes-dom0-update" works properly as intended and is
On Thursday, February 28, 2019 at 11:57:22 AM UTC+8, awokd wrote:
> Sphere:
>
> > Making it seem like my sys-net has been set as the updateVM for my
> > fedora-29 template
> >
> > I haven't tried updating my other templates yet but performing a
> > "qubes-dom0-update" works properly as
Sphere:
Making it seem like my sys-net has been set as the updateVM for my fedora-29
template
I haven't tried updating my other templates yet but performing a
"qubes-dom0-update" works properly as intended and is using updateVM properly
Double check targets in
On Wednesday, February 27, 2019 at 8:30:53 PM UTC+8, unman wrote:
> On Tue, Feb 26, 2019 at 06:54:15PM -0800, Sphere wrote:
> > It started happening just today
> > Executing sudo dnf update command on my fedora-29 template forcefully makes
> > my sys-net start
> >
> > But thing is, I'm no longer
On Tue, Feb 26, 2019 at 06:54:15PM -0800, Sphere wrote:
> It started happening just today
> Executing sudo dnf update command on my fedora-29 template forcefully makes
> my sys-net start
>
> But thing is, I'm no longer using sys-net template as my net vm and this
> caused me to triple check my
It started happening just today
Executing sudo dnf update command on my fedora-29 template forcefully makes my
sys-net start
But thing is, I'm no longer using sys-net template as my net vm and this caused
me to triple check my settings and my update VM is showed correctly as I had
intended = a
