-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-12-11 02:38, Simon wrote:
> Le 2016-12-11 07:36, Andrew David Wong a écrit :
>> That's strange. My dom0 dnf history shows all my updates, including
>> recent ones.
>>
>> Are you sure your dom0 has been getting updated? How are you
>> performing updates?
> 
> Hello Andrew,
> 
> When I do `rpm -qa --last' I can list all installed and updated packages
> with the appropriates dates, so I can confirm that dom0 gets correctly
> updated:
> 
> ---------------- 8< ------------------------
> 
> [user@dom0 ~]$ rpm -qa --last | head
> perf-4.8.12-100.fc23.x86_64                   Sat Dec 10 18:10:11 2016
> pciutils-libs-3.5.2-1.fc23.x86_64             Sat Dec 10 18:10:11 2016
> pciutils-3.5.2-1.fc23.x86_64                  Sat Dec 10 18:10:11 2016
> dnsmasq-2.76-2.fc23.x86_64                    Thu Dec  8 23:33:14 2016
> dmidecode-3.0-6.fc23.x86_64                   Thu Dec  8 23:33:13 2016
> qubes-input-proxy-1.0.8-1.fc23.x86_64         Thu Dec  8 23:33:12 2016
> qubes-gpg-split-dom0-2.0.24-1.fc23.x86_64     Thu Dec  8 23:33:12 2016
> perl-Time-Local-1.250-1.fc23.noarch           Thu Dec  8 23:33:11 2016
> kernel-qubes-vm-4.4.31-11.pvops.qubes.x86_64  Thu Dec  8 23:33:06 2016
> kernel-4.4.31-11.pvops.qubes.x86_64           Thu Dec  8 23:32:57 2016
> 
> ---------------- 8< ------------------------
> 
> To update, I simply use the Qubes VM Manager. The only things which may
> be noticeable are the following:
> 
> - Usually I update all the templates and Dom0 simultaneously: I right
> click on the AppVM template and click `Update VM', I do this for each
> AppVM in a row (without waiting for the update of the previous AppVM to
> terminate) and finally for Dom0 (since it locks access to the Qubes VM
> Manager during the while Dom0 update process, which is the longest, see
> below).
> 

When you say "AppVM," do you actually mean TemplateVM? There should
normally be no reason to update AppVMs.

> - I have the impression that Dom0 updates are downloaded twice, most
> probably an issue around the proxy feature (there is no such issue with
> the templates, updating Dom0 takes twice as much time as updating the
> templates).
> 

Hm, that would be odd. The normal dom0 update process is for the updates
to b downloaded by the UpdateVM (default sys-firewall), then transferred
to dom0, where the signatures are checked, and the updates are installed.
This might have the appearance of the updates being downloaded twice,
but they're really only downloaded once.

> - I regularly have ghost updates (the icon announcing that updates are
> available while there are none) but I think this is a known issue.
> 

Yes, that's a known issue:

https://github.com/QubesOS/qubes-issues/issues/2086

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYTbrxAAoJENtN07w5UDAwhlgP/3zvrF174QxmCIPKM0CO1biT
R74ZdPm67yttn3ONy6YhuBpcVTtggKCjFBsc95lN8YopbqtImUyTIRC180u6RQ1x
EFVtdiGlFijtyBHxFCvkahMXpAdxJl3ZLVB26Ji+M3gr74wdAMESPe5tajQbuw5j
cmPb7q14+zOa5ei84J1b+OD53IryPxe89ZSwN3smIlq/DdhgWw38RpdM8nJbEJe7
rlRi1he52sx+E7aJqlk8oEuRxUFPg6nEBe7ijD+EW4GjPQqb2KS5oC6P1/1kyvFq
0SAnHpxIulW3mULRO7MM3SOhZ7I7H7mWYq7NsMfsVqf4Vl64WkJUgHC7cv58JPLW
b6/NmF+Aes5kre7qVcVTZdXU8gDLA/40NNZr3HRMqMJhWEVCVVAjyZg/ZwhR1B1m
Hr+OIdidMYyy8PoSgqkbB8KW+roZI3may7yXWJ7bDocO4i+ou+GwyX13mtgOGoth
dbvN5g+pPiK9t2XPRRyBxC9HRuoJB4dmfJKa2jK/tSR2p4i9f1/lsZwqGJfckkxc
el0N1VyAes5gL1iV5nQP9bpziKLVaWYcTNt4h21m3zXQYWd6//Ci+lhLuiO36CAK
YTHzWtT45gRCsZVTZRjBQXtgxWq0jf83l2q11fF8P+rqOZG9pK0xxJAP36pnQCvX
qGkjDxzqMf8NT0XvS0tV
=PK+K
-----END PGP SIGNATURE-----

-- 
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/b4194cc9-b819-b6e1-63b1-621fd51857e5%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.

Reply via email to