I never tried it but from the screenshots it looks almost like a Yast clone (which is good in my opinion).
What I don’t like is that it isn’t promoted as the main tool instead of the push for cockpit. At least that is my perception.
Don’t get me wrong. It’s totally fine ofcourse if (Open)SuSE wants to be a distro for admins and/or software professionals who need to manage servers but that’s not what I’m looking for.
I’m in embedded electronics and also with Mint I only need a couple of commands in order to be able to write, compile and test software. The same with setting up a simple Samba server at home so that my Raspberry Pi with Libreelec connected to my TV can stream the TV-series from my pc via LAN.
Under the hood it’s all Linux in the end.
Myrlyn is strictly about managing software and repos, not about all the things that the other YaST modules could also do (and that are now largely obsolete).
I know that some bloggers announced it otherwise, but they just couldn’t be bothered to read the original announcement or (heaven forbid) the Myrlyn documentation.
Myrlyn is as finished as it will ever get. The only thing that is missing is the translations package - because nobody cared enough to take it over.
That’s a misconception. Myrlyn and Cockpit aren’t alternatives to each other. They solve different problems and have different scopes. Cockpit isn’t being pushed in place of Myrlyn. They’re complementary tools, not competing ones.
Nonsense. You can upgrade Leap from one release to another. You can just as well claim that you are forced to do a fresh install every 6 months with Ubuntu.
Sure. Yast and a lot of useful and carefully selected default options and integrated projects is what make me choose SuSE years ago. In those ancient ages, you just install a base system, a few needed packages according to the roles of your server, and just change a few lines of config and you are just up and running. With other distros were left much more far away from your goals, and you needed to change and adjust lots of configs, integrate manually other software packages, … a lot of time ($) lost…
Both, as installer and as config tool for several services. Not to mention the magic of SuSEfirewall, where just setting internal and external interfaces and a few more options and you get a wonderful set of stateful rules. Compare that with the effort needed to get the same result in other distros…
That’s been deprecated for some time. Firewalld these days, and that comes with its own CLI and GUI management utilities. Cockpit for basic firewalld management as Malcolm already mentioned.
Deprecated sure, but never forgotten. AFAIK neither firewalld nor Cockpit has options to put the same kind rules that SuSEfirewall created with just some options, just the kind of safe and carefully selected choices of default options that made it easy to use them. I know that with firewalld GUI or CLI you can probably do more or less the same rules, but you have to do it yourself, not just selecting an option and let the tool do it for yourself.
Same with qdiscs and traffic shaping, but i just didn’t use opensuse for that kind of firewall role anymore.
Huh? There are various zones (with pre-selected defaults) that are appropriate for most regular users. If you prefer a GUI, then use firewall-config - it’s very intuitive IMHO.
The reason I left was that I could not longer get RDP to work on Opensuse 16. I use it extensively to access remote Linux boxes from my Windows Servers.
I migrated away from Susefirewall2 around 2018, so i don’t have any system using it nowadays, and neither online backups from configs i supposed i wouldn’t need anymore, but i remember that it was very easy to say you want htb traffic shaping/prioritizing, protection against src spoofing, class routing between interfaces, and many other kernel level settings. And last but nor least, Susefirewall was a SuSE project, firewalld is from RH. I choosed SuSE over RH for what they offer back then, for all the great and small features that were different between both distros. I still choose SuSE now, and I would like to keep that way, but is loosing some technical advantages i value.
FWIW I’ve updated to Debian 13 a few months ago. It ships with Plasma 6 which defaults to Wayland. I need to use X11 applications for work (e.g. I do a lot of X11 forwarding) and so far XWayland has been working very well for me. Maybe you’d have no issues if you tried to run KiCad under Wayland, regardless of the distro.
It was deprecated for good reason. For a start it was explicitly designed around the iptables/ip6tables backend. Modern kernels use nftables as the primary firewall subsystem, with iptables only available through legacy or compatibility layers.
SuSEfirewall2 never provided UI options for HTB traffic shaping, class-based routing, or advanced kernel networking. Those functions always required tc, ip rule, or custom scripts. YaST’s firewall module was strictly a front-end to iptables, and quite limited compared with Firewalld really.
I moved here from LMDE (Linux Mint Debian Edition) because the desktop had some minor bugs when they released a major version. Point release upgrades are always a pain…
With Slowroll, there might be some small bugs here and there but at least I get all the latest stuff including fixes. Rolling upgrades on SR are also surprisingly smooth
