E: > Logic would dictate that an update is pushed to the all affected VM. > But, what I am now concerned with is the update packages that might be > altered in transit from ISP. > > **Side note, I came to Qubes because I was not satisfied with the > security protocols offered by MS OS.** > > > I will try updating from the terminal session. can you correct me on > the command: > > > user@VM $ sudo update ??????? (are update commands package specific) > > Bizarrely, I've seen some VM are now labeled localhost? > > > I am concerned about the file system corruption. How can I change the > system, or should I attempt a new install? > > > Thanks, > > > > On 7/14/20 8:19 PM, 'awokd' via qubes-users wrote: >> E. Foster: >> >>> Or do some updates occur because a template VM has been changed in a >>> repository, and the update package is then pushed to the respective VMs >>> using the template? >> This. Qubes Updater (Qubes menu/System Tools) runs periodically and >> checks for updates in repos. >> >>> Bizarrely, I have a VM and Template VM that keeps requesting to be >>> updated >>> and fails. >> Try updating the template from a terminal session on it. >> >>> And lastly, how many times can a device be rebooted before you should be >>> concerned about Xen issues. >> Until the hardware fails, I guess. Unless you're talking about hard >> power offs, in which case I'd be most concerned about file system >> corruption over any Xen issues. >> > Preventing packages from being altered in transit relies on the various distributions' security measures, not anything specific to Qubes. I feel you can reduce the likelihood of an attack by utilizing onion repositories where possible. Documentation on how to switch exists.
Update commands are specific to the distribution running in the template. Debian is apt update then apt upgrade (as sudo). Fedora uses dnf. These are not specific to Qubes either. If you have frequently hard powered off Qubes instead of a proper shutdown and are now concerned about file system corruption, be aware that fsck runs on every boot. It can often correct minor corruption, but if you want to be sure, a fresh reinstall choosing to delete and recreate the disk partitions should resolve it. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/78b7ed09-30f9-a04f-090a-c5e5792a2c71%40danwin1210.me.
