Hi allWe are now building, testing, and shipping separate MicroOSinstallation media in addition to the long established Kubic MediaYou can download it today fromBelow are some FAQ's to explain why we're doing this, which willlikely be a part of a future MicroOS website/blogpost/marketing.Meanwhile please download, play around, and let us know what you think!Feel free to question/add/comment/correct any of the FAQs also.FAQ===Q: What is openSUSE MicroOS?A: MicroOS is a Tumbleweed based operating system focused on being theperfect "single purpose" operating system.Q: What is meant by "single purpose" Operating System?A: Traditional Operating Systems are designed and implemented with anassumption that they will be deployed on a system that could domultiple tasks at once (eg. Web Server, and Mail Server). Theoperating system needs to therefore be designed in a particular waythat allows the simultaneous running, maintenance, and upgrade of theOS and all the services atop it.This creates complex real world issues, such as ensuring multiplesystems running the same OS all act the same way after upgrades,regardless of which services they run.A "single purpose" OS assumes that a single installed system will onlybe used for one task, with other tasks being handled by either othermeans or other systems. This could be multiple VMs or physicalmachines each running a "single purpose" OS, or using some kind ofcontainerisation framework to provide multiple services.Q: What are the benefits of MicroOS for "single purpose" workloads?A: MicroOS is built around the same transactional-update stack longused in Kubic. Transactional Updates are the perfect update mechanismfor "single purpose" systems, as they guarantee that the runningsystem never changes, and that any changes that do occur happen insingle atomic operations that can trivially be undone. With MicroOSTransactional Updates are automatic by default, patching the whole OS,rebooting and able to rollback without any user interaction.This makes it perfect for systems that need to be deployed, do onejob, and keep doing it for a long time even while the OS and serviceprovided are receiving updates for a long period of time.As a Tumbleweed derivative, MicroOS benefits from having all of thesoftware packages available from regular Tumbleweed.This meansQ: What system roles can be chosen when installing MicroOS?A: There are currently two system roles in MicroOS"MicroOS" which provides the standard MicroOS runtime environment,with no services installed or configured."MicroOS Container Host" which adds the Podman so the system is readyand configured to run containers as its "single purpose".If you have any ideas for additional System Roles that should beoffered with MicroOS, please reply with your suggestion.Q: What is the difference between MicroOS and Kubic?A: Kubic is now a derivative of MicroOS and identifies itself as suchin it's /etc/os-release.Kubic has been and will continue to be focused on Containers andKubernetes, whereas regular MicroOS is intended to be used for a morediverse range of use cases.The Kubic system role that was formerly called "openSUSE MicroOS" isnow renamed "MicroOS Container Host" and is absolutely identical tothe "MicroOS Container Host" provided by the MicroOS install media.Q: Will there be official qcow/vmware/vagrant images?A: Yes, absolutely. We would also expect there to be Raspberry Piimages soon as MicroOS should be a perfect fit for many users of thathardware--To unsubscribe, e-mail: opensuse-kubic+unsubscribe@xxxxxxxxxxxxTo contact the owner, e-mail: opensuse-kubic+owner@xxxxxxxxxxxx