Microos question: Automatic upgrades and firewall setup

English Install/Boot/Login
#1

I had the following questions about MicroOS for a desktop setup:

  1. If automatic upgrades are enabled but automatic reboot is disabled, is the following correct?
    Here’s a scenario:
    Current setup (say, Snapshot 1)
    Automatic upgrade applied (say, Snapshot 2), but the system is not rebooted.
    Another automatic upgrade applied (say, Snapshot 3), again the system is not rebooted.
    Another automatic upgrade applied (say, Snapshot 4), system is now rebooted.

    With health-checker doing its job, would the user then reboot into Snapshot 4? (And Snapshots 2 and 3 are not applied at all?)

  2. How does MicroOS handle updates/upgrades if the system has not been online for, say, a month or so? Is the transition from, say Snapshot A to Snapshot-2-months-later handled automatically by the base system, or would the user need to intervene via CLI? (For context: I’m setting up a desktop for my parents, and wanted to make sure that MicroOS can work as a set-it-and-forget setup. I myself have been using MicroOS for about 2 months, and so far it’s been running smoothly).

  3. Firewall: I installed firewalld as an rpm via pkcon and it worked as expected. I’m just curious: What is the design consideration behind disabling firewall by default?

If any of the MicroOS developers are reading this, I wanted to express how great it has been to use it so far. Thank you so much.