Monty Python's Take on YaST

Just to make sure everyone gets the message about YaST:

  • It’s not pinin’!
  • It’ s passed on!
  • This tool is no more! It has ceased to be!
  • It’s expired and gone to meet its maker!
  • It’s a stiff!
  • Bereft of life, it rests in peace!
  • If you hadn’t locked it to the perch it’d be pushing up the daisies!
  • Its metabolic processes are now history!
  • It’s off the twig!
  • It’s kicked the bucket.
  • It’s shuffled off ‘is mortal coil, run down the curtain and joined the bleedin’ choir invisible!!
  • IT IS AN EX-TOOL!!!

For reference: https://www.youtube.com/watch?v=4vuW6tQ0218

6 Likes

RIP. Regrets, but not forever.

Cockpit still falls short of Yast in terms of functionality, hence the lingering nostalgia of many users. Two or three more modules and Yast will be forgotten.

The end of an era, the beginning of a new one.

1 Like

Take some time to learn about fdidk, mkfs, vi(or another basic editor), useradd, etc, etc,. That looks boring, but they do their work already for tens of years and I assume they will do so for tens of years in the future.

Then you can smile about the coming and going (and the fuss hat this coming and going creates) of those “helper” tools, because you do not need their help.

1 Like

Cockpit plugins are being actively developed. There are many YaST modules that simply didn’t have a use case any more.

The five stages of grief are: alarm, searching, mitigation, anger and, lastly, gaining a new identity. No doubt different people will be at different stages in the grieving process.

2 Likes

It still miss a bootloader module. I see that an issue is open to vote : Feature Proposal: Cockpit GRUB2 Editor Module · cockpit-project/cockpit · Discussion #22431 · GitHub

Yes, I raised that, both upstream in the Cockpit project and more specifically as an openSUSE bugzilla request.

4 Likes

@deano_ferrari which grub? Grub2, Grub2-efi, Grub2-BLS and then there is systemd-boot :wink: Anyway, update-bootloader should work on any…

That’s why I suggested a front end to “update-bootloader” @malcolmlewis :wink:

For reference (already added to OP): https://www.youtube.com/watch?v=4vuW6tQ0218

I am well aware that plugins are actively being developed; it’s why I wrote that Cockpit only needs two or three more modules to bury Yast for good.

The Yast modules that I believe are essential to replace and that do not (yet) have a Cockpit equivalent are:
yast-bootloader
yast-snapper
yast-services-manager

They are rarely used, which is why I believe they are essential for many users who are not system administration professionals.

The features of yast-sudo and yast-users seem to be partially implemented by Cockpit; I think the only thing smissing are ‘user group’ and ‘sudo’ management.

Everything else it’s old, obsolete and useless. Or already implemented by desktop environments (sound and printer, for example).

Cockpit is much more modern than Yast and almost on par in terms of functionality.

We just need to be a little patient.

@Wolfheri Hi I run the flatpak version and there is a services manager there…

Edit: Account management is also there and covers adding a group to a user or create a group etc

1 Like

The service manager is also available in the openSUSE packaged Cockpit version…

1 Like

Thanks for the information. I hadn’t noticed that one.

I use these three modules, for instance. And how will I be able to manage my repositories? In Cockpit or in Myrlyn?

Via Myrlyn…

As for yast-users, I use it every time I have to install a new version of Leap. In the course of the installation, I then create “new users” in that module, but since they already have their home directories, with Yast I could attach these existing directories to the “newly created” users. I hope that Cockpit will not destroy the existing home directories for these users, or force me to create really new home directories …

Another question is about installer AGAMA. I always partitioned the existing partitions as an “expert”, with a BTRFS / partition to be formatted, where Yast always asked me to confirm that I wanted to make that BTRFS partition usable for snapper (by creating reserve copies), because after partitioning and installing it is too late for that. Will AGAMA even give me that possibility?

Cockpit has the possibility to define the path to the home directory as you wish.