Mathias Homann <Mathias.Homann@opensuse.org> writes:
Am Mittwoch, 20. Juli 2022, 11:11:29 CEST schrieb Lil Frogg:
you were expecting this test phase to immediately convince you of the merits of this new approach
Actually, I got exactly what I wanted, which was to see whether a transactional µOS would be good for a desktop.
- for preinstalled corporate-y setups where noone ever has the power to add software: it might work. - for "power users" that install and/or remove stuff all the time: nope. not gonna work that well.
Just imagine trying to file a bugreport for a KDE app, where you have to install debugpackages for a good backtrace...
That being said, for any kind of server that is set up to do exactly the same kind of workloads all the time until it gets decommissioned, or for any kind of virtualisation or container worker, a transactional OS is exactly the right thing. I just don't think a transactional µOS would sit too well with any kind of "desktop power user".
Here's a thought: It would be dead useful to have some kind of "builder kit" a.k.a. diskimage-builder that could be used to create µOS-based customized images that already have everything that the specific use case needs, and then you'd just clonezilla the image onto the harddisk (or import as VM) - but manually installing stuff on a transactional µOS is just too painful.
There is kiwi [1], it is currently being used on OBS to build the MicroOS desktop images over at devel:microos:images. You could branch that package into your home project, adjust it to your liking and use that image instead of the official one. Cheers, Dan Footnotes: [1] https://osinside.github.io/kiwi/ -- Dan Čermák <dcermak@suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Frankenstrasse 146 90461 Nürnberg Germany (HRB 36809, AG Nürnberg) Managing Director/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman