Alternative and corresponding configuration tools to YaST modules

oldcpu · September 2, 2025, 8:46am

I have been reading the comments and and discussions re: the demise of YaST and new applications such as Agama, Myrlyn, and Cockpit with interest. I surfed a bit on the internet, but I could not as of yet find a list or table , with a one-for-one equivalency list as to what was in YaST and what there will be in LEAP-16.0.

If anyone has seen such a detailed list, please let me know. Here is my current list, which could unforunately, have errors in it. I would be most happy to flag (or delete) this entire preliminary/draft list as inaccurate, and go with a better list. The numbers in this list are arbitrary and just numbers I wrote down when creating the list. Many of the apps require root permissions and further, most have arguments required that I did not list.

Again, if there a big mistakes let me know. I am a bit surprised not to see such a list yet, and I suspect it is due to my pathetic surfing ability … and likely I have many errors … so please take this list with lots of skepticism.

YaST Feature	Bash Shell Command / Application / Alternative - v.0.9.5.3
1. Software
1a. Add-on-Products	`zypper addrepo` / Myrlyn
1b. Software Management	Myrlyn, zypper
1c. Media check	`checkmedia`
1d. Software Repositories	`zypper modifyrepo` / Myrlyn
1e. Online update	Myrlyn, `zypper up`
2. Hardware
2a. System Keyboard Layout	`localectl`, GNOME/KDE Settings (GUI)
2b. Printer	`lpadmin` , CUPS Web Interface ( http://localhost:631/admin ) , and vendor-specific tools (such as hplip tools for HP printers: example: `hp-setup`(GUI)) , GNOME/KDE Settings (GUI), See also Note-1 (bottom of table)
2c. Scanner	Enter scanner’s IP address in a browser, or use a vendor-specific tool like (for HP scanners) `hp-setup`
2d. Sound	`pactl` (CLI); `pavucontrol` (GUI); KDE menu “`Settings > System Settings > Audio`(GUI)” or `systemsettings kcm_pulseaudio` (KDE GUI) ; Gnome Menu “`Applications > Settings > Sound`” or `gnome-control-center sound` (Gnome GUI); xfce4-pulseaudio-plugin (xfce panel plugin)
3. System
3a. Boot Loader	`grub2-mkconfig` (Grub2), `grubby` (Grub2-BLS), or `bootctl` (systemd-boot). Consult man pages for each.
3b. Date and Time	`timedatectl`, Cockpit, GNOME/KDE Settings(GUI)
3c. Network Settings	`nmcli` (CLI), `nmtui` (TUI), `nm-connection-editor` (GUI), or Cockpit (web-based). Consult man pages where appropriate.
3d. Partitioner	`fdisk`, `parted(CLI)` , GParted (GUI), Cockpit
3e. Services Manager	`systemctl`, Cockpit, `system-manager` (GUI)
3f. Sysconfig Editor	vim / nano (edit `/etc/sysconfig/` files directly)
4. Network Services
4a. Hostnames	`hostnamectl`, Cockpit
4b. NTP Configuration	`timedatectl`, edit `/etc/chrony.conf`, Cockpit, GNOME/KDE Settings (GUI)
4c. Proxy	`export http_proxy=http://your.proxy.server:port`, GNOME Desktop Settings(GUI)
4d. Remote Administration	Wayland-native solutions (e.g., GNOME Sharing/KDE Remote Desktop), web-based tools like Cockpit, or x11vnc for X11 sessions.
4e. Samba Server	edit /etc/samba/smb.conf, `smbpasswd`, Cockpit
4f. Windows Domain Membership	`realm join`, Cockpit
5. Security and Users
5a. App Armor	SELinux (`sestatus`, `setenforce`, Cockpit) or AppArmor (`aa-status`, `aa-enforce`). SELinux is default.
5b. Firewall	`firewall-cmd` (CLI), `firewall-config` (GUI), or Cockpit (web-based - basic).
5c. Security Center	re: kernel parameters (sysctl) managed via files in /etc/sysctl.d/. Consult the “sysctl” and “sysctl.conf” man pages.
5d. User and Group Management	`useradd`, `usermod`, Cockpit, GNOME/KDE Settings (GUI)
6. Virtualization
6a. Install Hypervisor	`zypper in patterns-server-kvm`, Cockpit, `virt-manager` (GUI to manage only)
6b. Relocation Server Config	`virsh`(CLI), edit /etc/libvirt/ config files, `virt-manager`(GUI), Cockpit
7. Support
7a. Release notes	`firefox /usr/share/doc/packages/docbook-xsl-stylesheets/RELEASE-NOTES.html`
8. Miscellaneous
8a. & 8c. System Logs	`journalctl`, `tail -f /var/log/messages`, GNOME Logs
8b. Alternatives	`update-alternatives --config`
8d. Vendor Driver	Myrlyn, `zypper install`
Comments/Notes:
Note-1 (printer)	For network printer discovery: Avahi, avahi-discover-standalone (GUI)
Note-2 (TBD)	TBD

Version changes: ( I added consult ‘man’ pages for some , perhaps I should remove such, … where that was mostly for myself as recommendations are being provided below in which I have no experience (yet))
0.1 - 2-Sep - updated item 4d (remote administration) per a comment below.
0.2 - 2-Sep - attempted to update wording of 2c (scanner) per a comment below.
0.3 - 2-Sep - attempted to update wording of 5c (firewall) per a comment below.
0.4 - 2-Sep - attempted to update wording of 5d (Security Center) per a comment below.
0.5 - 2-Sep - attempted to update wording of 3a (boot loader) per a comment below.
0.6 - 2-Sep - attempted to update wording of 5c (firewall) per a comment below.
0.7 - 2-Sep - attempted to update wording of 5a (App Armor) per a comment below
0.8 - 2-Sep - Updated section-5 (Users) numbering from 5a(AppArmor), 5c(Firewall), 5d(Security), 5f(User and Group Management) to 5a(AppArmor), 5b(Firewall), 5c(Security), 5d(User and Group Management)
0.9 - 2-Sep - updated the command to open the 7a(Release notes)
0.9.1 - 2-Sep - clarified local host under 2b(Printer) per comment below
0.9.2 - 2-Sep - added lpadmin under 2b (Printer) per comment below
0.9.3 - 3-Sep - added more entries to 2d (Sound) per comments below and also added an xfce setting. (ie changed table entry to read: pactl (CLI); pavucontrol (GUI); KDE menu “Settings > System Settings > Audio” or systemsettings kcm_pulseaudio (KDE GUI) ; Gnome Menu “Applications > Settings > Sound” or gnome-control-center sound (Gnome GUI); xfce4-pulseaudio-plugin (xfce panel plugin)
0.9.4 - 3-Sep - added to 2.b(Printer) the entry “Avahi (network printer discovery)” per comment below.
0.9.5 - 4-Sep - removed duplication in 2.b(Printer) and added vendor-specific entry
0.9.5.1 - 4-Sep - added entries indicating a bit more as to which have a GUI
0.9.5.2 - 7-Sep - added ‘placeholder’ section at end of table for some notes that I may add in the future.
0.9.5.3 - 7-Sep - moved printer avahi network discovery reference to a ‘note’. May delete in the future.

Again … for most of the commands arguments need to be added else the commands won’t work. (also - I am inconsistent in referencing man pages and a better approach is needed than what I have in place).

and further, this list could still be wrong in place.

And if there is a better list somewhere, I am most happy to have this first ‘draft’ at such deleted - in which case my apologies for spamming the forum. I simply could not find such.

deano_ferrari · September 2, 2025, 9:39am

What you list above is not for configuring scanner backends, and the last two are just graphical scanner utilities (front ends). Not comparable to the YaST scanner module’s purpose. In any case, the exact configuration required often depends on the scanner vendor, and sometimes the associated /etc/sane.d/.conf file. With the advent of driverless (eSCL and AirScan) scanning support (via sane-airscan), often no explicit configuration is required, beyond allowing DNS-SD (UDP port 5353) through the firewall.

There is also firewall-config (package of the same name) for those who prefer graphical firewalld management. Cockpit also provides for basic firewall configuration (refer to the Cockpit “Networking” configuration).

deano_ferrari · September 2, 2025, 9:58am

This is a bit simplistic. ^^

With the advent of Wayland, remote administration has shifted away from generic tools like x11vnc that worked by directly accessing the X11 display. Under Wayland, each desktop environment provides its own remote desktop functionality, typically built on PipeWire for screen/audio sharing and integrated VNC/RDP servers, or compositor-specific tools like wayvnc. For example, on Plasma Wayland, this currently means connecting to an already running desktop session rather than starting one remotely.

That’s where a web-based management utility like Cockpit can be especially useful, since it provides reliable remote administration without depending on the display server being active.

dcurtisfra · September 2, 2025, 10:07am

One of the things which I use from those settings is, the magic SysRq keys –

AFAICS, the only help is available from the “sysctl” and “sysctl.conf” man pages.

We may well have to carefully save everything in ‘/etc/sysctl.d/’

And, we’ll have to carefully read the “Security and Hardening Guide” documentation …

malcolmlewis · September 2, 2025, 12:04pm

@oldcpu
3a. There are three bootloaders available now Grub2, Grub2-BLS and systemd-boot…
5b(?). SELinux is the default (and has Cockpit support), not AppArmor.
3c. Can also use nm-connection-editor.

oldcpu · September 2, 2025, 1:27pm

Thanks for the input. … Is it worth editing my original post, perhaps with a change history, based on the comments? (I am happy to do so) or just leave ‘as is’ and users can simply read the comments?

I admit freely, there is a lot I do not know re : the details of the YaST alternatives.

dcurtisfra · September 2, 2025, 1:29pm

Yes!!

A change history is also a good idea …

malcolmlewis · September 2, 2025, 1:29pm

@oldcpu Sounds like an openSUSE Wiki page would be the best, then others can edit?

oldcpu · September 2, 2025, 1:44pm

It thought about that … I also thought it might be the best idea … but I confess I am feeling rather ‘gun shy’ here … I concede a lot of this is above my knowledge level and I might struggle with comments if too pointed and critical.

I even debated wether to start this thread, but in the end I did, not for the best of motives but to be honest, rather in some part due to my own self interest, in case I myself should need such.

I guess I need to ponder such.

Also, last time I wrote an openSUSE wiki was over 15 years ago … so I have mostly forgotten how (plus the method for doing wiki have long since changed).

I will need to research this.

oldcpu · September 2, 2025, 2:54pm

Starting configuration GUI to configuring a printer & scanner (?) without YaST

More on this topic of no more YaST … take for example printer configuring. I have relied on YaST heavily to successfully configure my network printers and scanners for over 20 years. So I just now took a look to see what I might do in Nov ?? this year when I go to install LEAP-16.0.

I may have this wrong …

First I thought to get my Printer’s IP address, but to get that I need to know a bit about my network. So I ran ifconfig to learn about my PC’s IP address.

Edit: instead of ifconfig see use ip addr show … see below post on how to get one’s PC IP address and use that instead of my ifconfig example.

oldcpu@lenovo:~> ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 5443  bytes 910716 (889.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5443  bytes 910716 (889.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.31.120  netmask 255.255.255.0  broadcast 192.168.31.255
        inet6 fe80::8b0f:f07a:3a3a:62aa  prefixlen 64  scopeid 0x20<link>
        ether 10:3d:1c:c4:27:b9  txqueuelen 1000  (Ethernet)
        RX packets 1549586  bytes 1767159624 (1.6 GiB)
        RX errors 0  dropped 69  overruns 0  frame 0
        TX packets 371729  bytes 82056386 (78.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

There is a lot to go through, but basically in that one can see from here:
inet 192.168.31.120 netmask 255.255.255.0 broadcast 192.168.31.255

that on my home LAN my laptop is

192.168.31.120
.

From that, I deduced I need to use 192.168.31.0 in a network search (scan) to find my network printer (ie use “0” in the scan instead of the “120” for my laptop).

oldcpu@lenovo:~> sudo nmap -p 631,9100 -sV 192.168.31.0/24 | grep -B 5 -E "open.*(HP|Epson|Canon|Brother|ipp|jetdirect|printer)"

Nmap scan report for e4e749ecf0dd (192.168.31.46)
Host is up (0.090s latency).

PORT     STATE SERVICE    VERSION
631/tcp  open  http       HP DeskJet 2600 series printer http config (Serial CN93J871Y806MF)
9100/tcp open  jetdirect?
oldcpu@lenovo:~>

That works for my HP printer, and from that one can see my HP printer’s IP address is 192.168.31.46 (ie where it says: Nmap scan report for e4e749ecf0dd (192.168.31.46) )
I also composed the above nmap command look for more than just my HP printer ( I inserted Epson, Canon, Brother in the grep filter ), but given I have never tested such for those printers, I do not know if that is correct.

Then typing one’s IP address into a browser (ie http://192.168.31.46) will open the printer’s Embedded Web Server (EWS). This is a web-based configuration tool built into many HP, Epson, Canon, and other network printers and it may allow one to configure the network printer.

BUT … having an HP printer, there are HP provided apps that I believe one can run directly instead from a bash shell. ie hp-setup or hp-toolbox.

Initial setup: I read hp-setup is best for managing an already configured HP device (including a network device). hp-setup is a wizard-based utility designed specifically for the initial installation and configuration of a new HP printer or scanner. It will guide you through connecting the device, installing the necessary drivers, and configuring it for use with CUPS and SANE.

Managing an existing configured HP device on the network: I read hp-toolbox is the better choice for managing an already-configured HP device. Honestly, other than check that the command brings up a GUI, I have never used the ‘hp-toolbox’ app.

My assumption is that when configuring the scanner, these apps may also help there.

Again - in the past I never bothered with this - I let YaST help me.

And today, likely if I had taken the time, I would have found a nice wiki explaining all of this - but sometimes its fun to figure these things out one’s self.

oldcpu · September 2, 2025, 3:48pm

I update thed list of ‘equivalencies’ a bit. Unfortunately the mail server users will not see the update. Likely this needs to eventually go in a proper wiki - perhaps when more mature?

I see I am missing a 5b. Somehow i screwed up my numbering. In which YaST equivalent would this go? 5a ( AppArmor)?

Edit- thinking about it (its late at night so I am slow) … obviously 5a.

myswtest · September 2, 2025, 4:17pm

Hmm. Rumor has it “ifconfig” (and its parent tools’ package) , has not been maintained for a very long time (i.e., deprecated). Probably best to not advertise it, or use it.
I’ll try it though

#  ifconfig
If 'ifconfig' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf ifconfig
#

.
Here’s how I do it these days (as many others do, no doubt):

# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: ...
... snipped a bunch of output ...
.
       valid_lft forever preferred_lft forever
#

oldcpu · September 2, 2025, 4:21pm

Thanks !! I like that.

dcurtisfra · September 2, 2025, 4:32pm

@oldcpu:

Lee, as far as my Kyocera printer (connected via Ethernet to my DSL Router) is concerned –

 > avahi-browse -a
+   eth0 IPv6 Kyocera ECOSYS M5521cdn                       _privet._tcp         local
+   eth0 IPv4 Kyocera ECOSYS M5521cdn                       _privet._tcp         local
+   eth0 IPv6 Kyocera ECOSYS M5521cdn                       _tdrsservices._tcp   local
+   eth0 IPv4 Kyocera ECOSYS M5521cdn                       _tdrsservices._tcp   local
+   eth0 IPv6 Kyocera ECOSYS M5521cdn                       _tdrsservice._tcp    local
+   eth0 IPv4 Kyocera ECOSYS M5521cdn                       _tdrsservice._tcp    local
+   eth0 IPv6 Kyocera ECOSYS M5521cdn                       _uscans._tcp         local
+   eth0 IPv4 Kyocera ECOSYS M5521cdn                       _uscans._tcp         local
+   eth0 IPv6 Kyocera ECOSYS M5521cdn                       _uscan._tcp          local
+   eth0 IPv4 Kyocera ECOSYS M5521cdn                       _uscan._tcp          local
+   eth0 IPv6 Kyocera ECOSYS M5521cdn                       PDL Printer          local
+   eth0 IPv4 Kyocera ECOSYS M5521cdn                       PDL Printer          local
+   eth0 IPv6 Kyocera ECOSYS M5521cdn                       Secure Internet Printer local
+   eth0 IPv4 Kyocera ECOSYS M5521cdn                       Secure Internet Printer local
+   eth0 IPv6 Kyocera ECOSYS M5521cdn                       Internet Printer     local
+   eth0 IPv4 Kyocera ECOSYS M5521cdn                       Internet Printer     local
+   eth0 IPv6 Kyocera ECOSYS M5521cdn                       Sicheres Web-Angebot local
+   eth0 IPv4 Kyocera ECOSYS M5521cdn                       Sicheres Web-Angebot local
+   eth0 IPv6 Kyocera ECOSYS M5521cdn                       Web-Angebot          local
+   eth0 IPv4 Kyocera ECOSYS M5521cdn                       Web-Angebot          local
+   eth0 IPv6 Kyocera ECOSYS M5521cdn                       UNIX Printer         local
+   eth0 IPv4 Kyocera ECOSYS M5521cdn                       UNIX Printer         local
 . 
 . 
 . 
 > 
 > LANG=C lpstat -v
device for M5521cdn: dnssd://Kyocera%20ECOSYS%20M5521cdn._ipp._tcp.local/?uuid=4509a320-00a4-0124-0110-002507513a11
 >

 # lpinfo -v
network beh
serial serial:/dev/ttyS0?baud=115200
network socket
network ipps
network lpd
network https
network http
network ipp
network smb
network dnssd://Kyocera%20ECOSYS%20M5521cdn._ipp._tcp.local/?uuid=4509a320-00a4-0124-0110-002507513a11
network socket://192.168.178.22
network ipp://KyoceraM5521cdn.local:631/ipp/print
 #

And, there’s the CUPS Web Administration page – <http://localhost:631/admin>

Or, “lpadmin” …

oldcpu · September 2, 2025, 4:35pm

I am getting senile … I have used that page many times in the past - and I forgot.

… age-71 is too young to be senile. I have a 92-year old friend who is as sharp as a whip.

… sigh …

thanks for suggestion.

dcurtisfra · September 2, 2025, 4:42pm

As far as KDE Plasma is concerned, I mainly use the KDE System Settings to manage sound.
Presumably the same for GNOME …

There’s also the JACK world, which YaST never supported …

oldcpu · September 2, 2025, 4:53pm

Your noteable observation that there are aspects (such as jack) that YaST never supported has me thinking this may be the opportunity or best time (with LEAP-16.0 on its way) to either produce one bigger list, or two lists.

If one list, basically such a list would include ONLY the equivalencies to YaST , which is what I have sort have undertaken

Or if two lists, one list would include the identical list as the above (only YaST equivalencies - more or less) and a maybe second (superior) list - possibly in a different/better format (if such possible), that would include pointers to apps that not only include YaST equivalencies (more or less) but also include a number of aspects that YaST never covered.

At the moment, I am challenged just to do a list of sort of YaST equivalencies. … I also soon will be a bit short of time … in about 1 months time I am going travelling close to the other side of the world from where I live in Thailand - heading to Canada for over a month. Likely I won’t do much then.
.

oldcpu · September 2, 2025, 4:59pm

Under KDE is this Settings > System Settings > Audio what you are referring to ?

I confess, < gulp > I have never looked at this until you mentioned it now. I guess I never had to.

Can a Gnome user please chime in as to whether there is some Gnome specific aspect?

I may update the ‘hardware/sound’ equivalency tomorrow.

oldcpu · September 2, 2025, 5:25pm

If that is the setting, then I note that KDE menu can be opened by this bash shell command:

systemsettings5 kcm_pulseaudio

I note i get an authentication error when I open such that way:

oldcpu@lenovo:~> systemsettings5 kcm_pulseaudio
Qt: Session management error: Authentication Rejected, reason : MIT-MAGIC-COOKIE-1 authentication rejected
oldcpu@lenovo:~>

I could put my head in the sand (like an ostrich) and open up that menu this way:
systemsettings5 kcm_pulseaudio 2>/dev/null

I wonder thou. if systemsettings5 may be specific to LEAP-15.6 and Leap-16.0 have a different command. I speculate LEAP-16.0 could be systemsettings6 kcm_pulseaudio or kcmshell6 kcm_pulseaudio . I don’t yet have a LEAP-16.0 beta nor RC1 yet to test such on.

And this all may be a mute point. Its just as easy under KDE to go to Settings > System Settings > Audio

hui · September 2, 2025, 5:32pm

The version (Plasma 5 or 6) doesn’t matter. You can always use simply systemsettings without any number.