This won’t be useful, just to let off steam
I decided to upgrade to leap 16.1 since 15.6
the surprise was good during the migration, I found a pleasant user interface again and everything has been preserved!
The apprehension I had was related to Yast, having read that this tool no longer existed.
Well, it’s worse than I thought!! Cockpit doesn’t do 10% of what Yast did. On the software side, no problem, Myrlin does what Yast Software does, it’s perfect,
but no more control center as Yast did, configuration of Apache, DNS, services, session manager, windows, etc.
SUSE should not dare to put this OS online without the tools necessary for management
When I adopted Suse more than 25 years ago, it was because this distribution managed network ISDN cards and because there was Yast.
When I started using Linux (“slackware”), 30 years ago it was because it provided TEX and LaTEX. I no longer use those, and I’m now on openSUSE. Things change during life, and we find ways of adapting to those changes.
I started to use (open)SuSE in 2000 and use it ever since as my main Linux distribution (although I look at other distributions from time to time) but I have not used YaST for years now. It is not even installed on any of my systems.
I joined almost ( next year ) 30 years ago, saw YaST rise and slowly fall. Modules were dropped earlier, like ( from my head ) SSH, DNS, recently Printing, @shundhammer will probably no more. It goes with what happens and no longer happens otherwise. It’s like life. When systemd came, eeeeeveryone was so upset that I decided to read what it was all about, and found it very promissing. Same with KDE’s Plasma concept, Wayland. The world did not die, and we ( except for some)'re happily using the new stuff.
Ranting never helps anyone. Just saying. It blurs your sight.
There are a ton of regressions feature wise between 15 and 16. It’s not a “soapbox” issue, it’s just the way it is. Is that ok? Depends on what your expectations are.
My guess. We’ll see some of the beneficial things in 16 and eventually forget or work around the missing elements. Really, not much different that the same sort of recent pains in Windows land.
At the same time there’s zero benefit in using “fanbois” bravado to try to boost 16. That doesn’t really help anyone.
Let me put it mildly: This is a lousy way of discussing, any disagreement is in advance degraded to “fanbois” bravado, so the poster is a “fanboi”. That doesn’t really help anyone either, right? Nor does it take away anything from @deano_ferrari 's “soapbox” statement, rather confirms it IMNSHO.
35 or 40 years ago , i did’nt have the courage to look at the date real ; M$ win again’st Netware because the put mouse to admin windaube
Also because Novell did’nt listen to users attemps
If you think the futur of Suse is in the hand code admin your are wrong way
Hi, but any system setup etc, surely you have backups or notes on what was configured and can duplicate via autoyast and convert to a Agama profile for initial setup?
Once systems are setup, generally it’s just maintenance after that… Cockpit works fine for that task, but have been using the command line for many years.
Systemd services are way easier to create than init scripts…
I was merely pointing out that “the opposite” is also very true. We should be objective rather than judging first when people are expressing frustration, especially when we know there are valid points.
Wow, if you file bugreports and feature requests ( where are yours? ) like this a “Closed as Won’t fix” would not surprise me.
No, you are wrong, and not just a bit. If you want to see me mad, go on. I have been at all the feature request meetings ( see calendar.opensuse.org ) for 15.6, 16.0 and now 16.1 , did the testing surveys and so on and never ever saw you and any of the other loud complainers in these forums even once. There is stuff that landed in the mentioned three that did get in thanks to people that did. Despite the public character of all the options users have, they prefer to moan and groan here, instead of contributing. The Leap release manager does listen, and is very actively asking for input. But once the distro is set in stone ( i.e. GA ) even he should not touch it. You can also not expect him to take over maintenance of all the community built packages that were, despite continuous requests, were not built for 16.0 . That he listens can be seen by the fact that he did sneak in a couple of packages in the distro that were not there at GA. If all these complainers would show up, that really would help, but usually it is just the three-four of us, incl. Luboš. And, that devs and packagers in general are not in these forums, is something that has been said thousands of times here.
I stop here
80 years old retired i don’t spend more time in a steril discussion
best to you and don’t change anything
Just on thing Myrlin est best than yast software
that’s was not possible for DNS, HTTP server , Desktop settings and so on … ?
have a good way me i am on the end off
I seem than everywhere on earth the new generation does’nt want to listened previous experience
@Enthalpie It’s not about listening, it’s about Community support for the items that users want, YaST was/is available, it just needs contributors to step up and maintain.
I’ve been using computers since the 80’s and happy with the changes I see
I am only 14 years younger. And have 38 years of IT experience. I just don’t want to be a grumpy old man saying everything was better in the olden days, and moan about younger generations that in return state that I have become a bitter old man. How could I expect them to listen, if I don’t listen to them?
No room for age shaming here, so many of us retirees writing here .
That said, let’s stick to some facts.
YaST interface is Qt5 only, Qt5 is unmaintained upstream since May 2025 (please see Phase out of Qt 5?): anybody stepping up?
Many YaST modules already don’t work on current systems (Networking, Sound) or are not up to current standards (Users) or have been replaced by better alternatives on the main desktops (Printing, Scanner) and basically all are nearly unmaintainable with current tool chains (see several detailed reports by @shundhammer also here on the Forums).
Down to details:
DNS
Open Cockpit Networking tab, choose the interface of interest, at the end of the IPV4 and IPV6 lines hit the “edit” link and the configuration is easier than it ever was on YaST.
SERVICES
Hit the Cockpit Services tab: it’s way better than the YaST Services ever was. Also please be aware that currently (on Tumbleweed) YaST does not “see” many systemd services.
Apache / https:/ server
Cannot comment, no meaningful experience here; guess that YaST doesn’t cope with current standards?
Session manager, windows, etc.
Cannot even figure out what’s at stake here.
To be fair, SUSE did no such thing. The Community “put this OS online” (Leap 16.1? Still beta. Leap 16.0?)
SUSE put online SLES 15.7, with regular support through Jul 31, 2031 and extended support to Dec 2037 on the basic parts.
The Community couldn’t afford to support two releases in parallel (15.7 and 16.0), so we ended up being the “Guinea Pigs” for SLES 16. We know, it was always that way, nevertheless we are grateful to SUSE for sponsoring so many resources used by the Community.
As usual, you get what you pay for (in €, $, or time volunteering to develop, maintain, document or support).
How do other (community) distributions do that? Do they have (some) paid staff (at least) or (just) volunteers (at all)?
I don’t want to bother: I am asking seriously. I really don’t know. When I am following forums.o.o I sometimes get the impression that openSUSE has a lack of volunteers — whereas other (community) distributions obviously seem to have a lot of.
Is it this way? Has it been different in the (very) past?
.