The future of YaST in Tumbleweed – what do you think?

Hey Everyone,

I’ve been on openSUSE Tumbleweed for quite a while now, and honestly one of the biggest reasons I stick with it is YaST. It’s always felt like such a powerful yet simple tool for managing the system, and I’ve really come to rely on it.

With Leap 16.0 dropping YaST and the talk about moving towards Agama and Cockpit, Myrlyn, I’ve got to admit I’m a bit worried — YaST has always been such a core part of the openSUSE experience for me.

I’m curious how others feel about this shift:

  • Do you feel the same sense of loss if YaST goes away?
  • Are there certain YaST features you think will be hard to replace?
  • Has anyone here already moved over to Agama, Cockpit, Myrlyn, and how’s it been?
  • Do you think the new tools will actually give a better experience once we get used to them?

Would love to hear your thoughts!

1 Like

It’s been awhile since I used YaST in earnest, been using Cockpit for awhile now as I can connect to all my systems on the local Lan without having to install anything as I use the Flatpak version. Sure there are a few things missing, but I’m also comfortable from the command line to perform tasks. AFAIK there will still be some ncurses module versions around.

@flourbot7725:

First, welcome to the openSUSE Forums.


Yes, I can agree with you – YaST was a wonderful way to learn Linux System Administration.

But, it’s currently in a “nobody wants to maintain it” parallel Universe.

SUSE possibly has lost interest in the System Management of single systems –

But, that’s a totally different scenario to what many private system users want to do … :smiling_imp:

2 Likes

@malcolmlewis
Thanks a lot for sharing your thoughts.
Helpful to hear your experience with Cockpit. I’ll give the alternatives a try.

@dcurtisfra
Thanks for the welcome and your reply.
It’s a bit sad that YaST isn’t being maintained anymore, and maybe I’ll try the new tools soon.

I would say that YAST2 is too old to find candidates to keep it alive. It’s a technology of the past with an approach that has had its day.

The choice of Ruby now seems questionable, as it is no longer as popular as it was when it was chosen. This makes it more difficult to find maintainers.

For my part, I didn’t understand why Ruby was preferred over Python.

We discussed this issue in May on the factory mailing list: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/message/ONIUAWRROJ5XEZKEROONZLYKV2P3U56Q/

1 Like

As for Myrlyn, you can install and use it immediately on Tumbleweed and Slowroll; it’s a drop-in replacement for the “YaST Software” module. You don’t even need to uninstall YaST to use it.

It can do all package and patterns operations that YaST could do and more (zypper up and zypper dup equivalent), and also the common repo operations (add, edit, remove), including community repos like PackMan, NVidia etc.; just try it.

2 Likes

Given the long term value of YaST2 to so many users, I don’t get why the developers of myrlyn didn’t name it YaST3.

Because, you know the difference between YaST and Myrlyn? Myrlyn is only a replacement for the YaST Software module (one of ~150 modules)…not for YaST itself…

3 Likes

Because it’s not YaST3.

It doesn’t want to be; it’s strictly only about the package management part, which was always largely a separate component. Naming it YaST3 would raise expectations that all the other YaST2 modules would be added in the future, and, worse, that there would also be an NCurses (text-based) user interface. None of that is going to happen; I explained that at length in the original documentation and also at the hack week project.

Myrlyn is following the Linux/Unix principle: Do one thing, and be good at it; don’t try to cover a whole range of tasks. Trying to be everybody’s darling doing everything never worked in the past.

7 Likes

Along with hui’s response about Myrlyn’s purpose, Cockpit, and its growing list of plugins, provides a modern, web-based alternative to YaST for managing (local and remote) systems. Its architecture makes it highly extensible, and suitable for supporting multiple Linux distros.

1 Like

Presumably you are referring to Myrlyn Package Manager. To my experience most users prefer clicking on an inline link instead of searching for it.

I rarely use GUI applications for maintaining systems. However I always wanted to browse available resources with a performant lightweight application such as User Mode Myrlyn. :wink:

By reading this really, really short thread, you would have seen that Stefan provided this link already 5 posts above yours.

2 Likes

For the case of “Cockpit”, please be aware that, the current Leap 15.6 version is somewhat outdated –

  • Cockpit 321 – openSUSE Backports.

On the Cockpit web site, the newest version is 345, dated Tuesday the 19th of August 2025.

And of course, for those of us running Leap 15.6, who have installed Cockpit using Discover as a Flatpak, we are up to date with version 345:
.

1 Like

Hello everyone,
So as a new user 3 months now.
I noticed that Myrlyn was installed through the updates ,will the same be applied for Agama and Cockpit or we have to handle the transition by ourselves?
The only thing that I used YaST was to decrease grub2 menu time to 2s instead of 8.
without any problem.

I have never used YAST except, iirc, back in the day I think that’s how you installed software (though I could be misremembering).

TL;DR I’ve recently built a new computer (ASRock X870 Steel Legend WiFi) and I’ve been bouncing around trying to find a really good, X870 chipset-supporting kernel/distro combo. Anyhow, I saw Myrlyn and was wondering what it was.

It is a software manager, basically a redesign of YaST2-Software module and going to replace it sooner or later.

1 Like

It’s “sooner” rather than “later”. It’s the default with the upcoming Leap 16 … and will be with TW. Endless posts about this transition :+1:

1 Like