On 12/07/2017 10:17 PM, gro...@gmail.com wrote:
Although a long-time user of Qubes 3.2, I'm a novice in the sense of not having
much understanding under the hood yet, and also am quite new to this group. If
I've overlooked some FAQ or relevant posting, apologies in advance; terse
pointers welcome.
With the old VM Manager in Qubes 3.2, when a "dom0 updates are available" notification
appeared, I would dutifully update and reboot. On my new machine with a fresh Qubes 4.0-rc3
install, in a dom0 terminal I did "sudo qubes-dom0-update" got myself into trouble.
After reboot, sys-net would not start and of course life is difficult after that. I found it
easiest to just re-install from scratch.
question 1: Is there something else I should have done, besides take more
careful notes about how I got myself wedged?
That's the way you update in rc3. But you might want to update with
--enablerepo=qubes*testing to see if that resolves the sys-net issue. Of
course, it might bring the problem back.
You could try to snapshot your dom0 LVM volume (called 'pool00/root')
before the update and then restore the snapshot if something goes wrong.
question 2: Is there a standard way one is supposed to sign up for VM update
availability notices in the new world?
I'm not aware of an update notifier (yet) in R4.0.
--
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
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/073ebf82-2ba9-ab7e-7b90-a85911b004b2%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
