After a couple years on Fedora I decided to do one more Distro hop- to one I have little experience with, openSUSE.
But it seems the everything from the installer, philosophy, package manager, configs, and general way of working is just very different than every Distro I’ve tried before (Debian/*Buntu, Fedora, Arch, Gentoo)
Like what’s up with YaST? It’s like a system-wide settings/configs program plus a package manager front end unique to openSUSE?
And to update grub it seems the best command is “update-bootloader” - for example. This isn’t standard on anything else afaik. Is there anywhere other than practice I can learn all of these quirks?
Most modern distros are either new distro trying to have more modern sensibilities, distros based off of Debian, Arch, or Fedora, or occasionally original things that are okay with being superficially similar to one of those while doing things differently at lower levels. OpenSUSE is one of the few remaining distros from the olden days that has been independent and doing their own thing for decades without spawning a bunch of forks or dying off. If you want to try something even older and crazier Slackware is sure an experience.
you may not know this, but suse was originally based off of slackware way, way, waaaaay back in the day before changing over to a jurix base.
Slackware’s package manager doesn’t even do dependency resolution. I respect the fact that it’s managed to keep existing this long and that so much of what it did inspired other distros, but I honestly have no idea why anyone would use it in 2023. Imo dependency resolution is the main reason to even have a package manager, without that I might as well install everything by cloning random git repos. If you want packages compiled from source, why not just use Gentoo (or Source Mage? Idk much about it, but I read through their website and it seems neat).
That being said, if anyone uses Slackware, I’d love to know why. It’s survived this long, surely it must be doing something right.
The Slackware community has produced about 8 package manager front-ends that handle dependency resolution, so it’s not an issue at all and hasn’t been for over a decade. The big thing with Slackware is an emphasis on simplicity of design over ease of use and an expectation that the user will make all the decisions regarding how their system is maintained. I love it, use it on my main machine (Void on my laptop, Ubuntu on my server). It’s taught me a lot about operating systems in general and Linux in particular, and it lets me do whatever I like. I use sbotools and flatpak for my 3rd party software, the former being a ports-like interface to slackbuilds.org (like the AUR for Slackware, but far smaller and with a lot more quality control). Works great, no surprises, boots fast, rock solid and dependable.
It’s completely surprise free. You’re not going to wake up tomorrow and find it’s dumped Systemd and Wayland on your front porch like some unsokicited car wreck.
I use it because 22 years ago it was more appealing than redhat or Mandrake. It forced me to learn more about Linux because I had to resolve almost everything myself than any other distro. I was using before it had a package manager and honestly after the dependency hell of rpms in 2000s it just seemed more problematic to use one that resolved dependencies than not. Usually I used to and sometimes still use it for a nice base to compile everything on. I dunno. It’s my Linux equivalent to my first car that I loved.
It’s a wonderful distro that will teach you a lot about how Linux works. It’s weird, and beautiful and you might brick your system or an essential component (why the heck would I need groff?), but you’ll come out the other side knowing more and appreciating how things work and how easy they’ve become.