On 09/18/2017 09:58 PM, Alex wrote:
On 09/19/2017 09:47 AM, [email protected]
wrote:
Hi! I haven't been using qubes (or computers, for that matter) for a
wee bit of time and now that I'm back I see fedora 24 going the way
of dinosaurs.
Also, on github, I noticed
https://github.com/QubesOS/qubes-issues/issues/2574
Do I understand correctly that Dom0 is Fedora 25 now?
Is that only for Qubes > 4, or will R 3.2 get a Fedora 25 dom0 too
(I'd like to stick with R3.2 for the time being)
If Fedora R 3.2 get/got a Fedora 25 in Dom0, what precautions should
I observe when updating Dom0 (besides BACKUP EVERY SINGLE THING)
My last Qubes update was around February-March 2017 or somesuch.
Only dom0 in Qubes R4 will be F25; as of now I can't find the e-mail
thread, but I remember that the reasoning was that it's better to keep
the stable release as stable (i.e. not embracing potentially troublesome
upgrade paths), and focus the cutting-edge integration on new releases only.
It makes sense to me: dom0 has the only ungrateful task of supporting
hardware in R3.2, and the main reason for upgrade is VGA hardware
drivers. There are no security implications for remote attack vectors in
the particular version of software in dom0, since it can't directly
access the network and should not be remotely accessible.
In Qubes 4 and later, the roadmap states that VGA support will be
demanded to an appvm, that will be upgraded like any other appVM in the
system - best of both world: isolated UI and updated drivers.
In the unlikely case that R3.2 receives a dom0 upgrade it will likely
still be a fedora distro, just an upgraded version, so the upgrade path
will not be too extravagant. Beside backing up everything (please use
the included backup tool: it will be the only supported way to move to a
newer version or restore the same version it was created on), there
isn't really much to do. If you customized the system beyond your home
directory you should take care of these customizations, but you're
mainly on your own in that case...
So, do a qvm-backup on all AppVMs, (though, this won't allow upgrade to
4.0?)
And, also do the "paranoid" backup ?
something like this :
[user@dom0 ~]$ qvm-backup-restore --paranoid-mode --ignore-missing -d
sys-usb /media/disk/backup.bin
I personally don't even have a sys-usb VM , is there some less terse
explanation on how to prep and/or do the "paranoid" backup?
I had stopped looking at it, as it seemed only for those whom suspect a
"compromised" system?
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/a05a94de-b2e5-1e4b-6897-5236bffa1d7f%40riseup.net.
For more options, visit https://groups.google.com/d/optout.
