Updating a new installation

[Shawn Creighton]

What is the quickest and most secure way to update the entire system including Dom0 on the first boot of a new install? I've noticed that it takes awhile for the updates to populate to the qubes updater when first connected to the net even though there are obviously updates available. Is there a way to expedite the process?

[0spin...@gmail.com]

sure, just open a terminal in dom0 and run 'sudo qubes-dom0-update --clean'

[Ulrich Windl]

I think you can always run the dom0 updater to get the updates, and for
the VMs it seems that starting one reduces the time until updates for
the corresponding template are found.
Still I'd like an explicit "check for updates"...

>
> --
> 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...@googlegroups.com
> <mailto:qubes-users...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/qubes-users/CABF_mq1OTL78t%3DHfeOGkGrdyCogJPWOQ1sLW-qf5WgLa6n7TiQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/qubes-users/CABF_mq1OTL78t%3DHfeOGkGrdyCogJPWOQ1sLW-qf5WgLa6n7TiQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.

[unman]

On Mon, Feb 01, 2021 at 11:34:30PM +0100, Ulrich Windl wrote:
> On 1/27/21 7:44 AM, Shawn Creighton wrote:
> > What is the quickest and most secure way to update the entire system
> > including Dom0 on the first boot of a new install? I've noticed that it
> > takes awhile for the updates to populate to the qubes updater when first
> > connected to the net even though there are obviously updates available.
> > Is there a way to expedite the process?
>
> I think you can always run the dom0 updater to get the updates, and for the
> VMs it seems that starting one reduces the time until updates for the
> corresponding template are found.
> Still I'd like an explicit "check for updates"...
>

It's also worth checking to see what templates were installed with the
new install.
Depending on what installer you used you may find you have outdated
templates - rather than upgrading these in place it''s almost always
better to install a clean new template:
e.g. sudo qubes-dom0-update template-qubes-debian-10

As Ulrich says, starting a qube will (by default) check for updates and
report back to the system - you may or may not want this to happen
automatically - it's a service that can be disabled across the system.

You need not wait for this to happen if you use the gui updater tool -
just open the tool, select "Enable updates for qubes without known
available updates", and go ahead.
N.B Install any new templates *before* you do this.

unman

[Shawn Creighton]

So  "sudo qubes-dom0-update template-qubes-debian-10" installs a new fully updated Debian 10 template? Why is it better than updating the default templates?

Is it best to do all updating via Dom0? 

Thanks

[Shawn Creighton]

Also does the baremetal hypervisor ever need to be updated from a default install of the newest version of Qubes? I am using a Purism Librem 15v4 laptop. 

[unman]

No, this will install a new template *as it was when it was built* - you
will still need to update that template to bring it fully up to date.
N.B. You will only need to install in this way if the install medium you have
used does not provide the latest templates - Fedora32, Debian10.

Yes, the Qubes updater tool is used to provision certain other aspects of
the template in addition to performing the update, so it is best to use
it if possible.
On Thu, Feb 04, 2021 at 06:52:22PM -0800, Shawn Creighton wrote:

[unman]

Just updating dom0 using the tool or qubes-dom0-update is fine.