On Fri, Mar 5, 2021 at 9:26 AM Ancor Gonzalez Sosa <ancor@suse.de> wrote:
MicroOS does not use YaST as local system management tool, as most modules don't work on a read-only root filesystem.
We have/are working on Cockpit.
At least yast2-storage-ng can be use, because only modify /etc/fstab and can be use to internally manage LVM partition. "the user will/have to learn that modifying the read-only partition will break the system." I have not tried, but my gut feelings tell me that using the YaST Partitioner in a transactional system will result in some things working
On 2/28/21 4:08 PM, Walddys Emmanuel Dorrejo Céspedes wrote: perfectly and others not working at all, with every Partitioner operation being in a different point of that spectrum. If that's the case, including it in MicroOS would be more confusing than helpful.
Not to mention the dependencies yast2-storage-ng would drag in (specially Ruby).
It makes sense to focus on improving Cockpit, as the individual MicroOS nodes can avoid interpreter runtimes and such. That gives us updates management (through PackageKit with my txnupd plugin for the DNF backend), storage management (through UDisks2), network management (through NetworkManager), service management and logging (through systemd), simple container management (through Podman), and the ability to extend things with our own Cockpit modules later. -- 真実はいつも一つ！/ Always, there's only one truth!