The case for Linux and openSUSE is clear. Linux provides viable, cost-effective and sustainable alternatives. Users can enjoy a free, open-source operating system that doesn’t require costly upgrades or restrictive hardware requirements with installing openSUSE. Here are a few things users that want to transition can consider:
- Complete Transparency: Linux distributions like openSUSE are governed by open-source principles, ensuring clear and consistent development.
- No Forced Obsolescence: openSUSE supports a wide range of hardware like modern machines to older PCs that allow users to extend the life of their devices.
- Cost Savings: openSUSE is free to use, with no licensing fees or hidden subscription costs for extended support.
By switching to Linux, users can help combat e-waste as every PC saved from a landfill is a win for the environment.
openSUSE is the GOAT for several reasons, but by far my favorite reason is Zypper.
I’m daily driving it for ~3 years and I only started yast once to see why everyone praises it so much and second time when I actually needed something (don’t even know if I suceeded or failed).
Snapper on the other hand… That is a bit I praise the most! I still don’t get it why it’s not default for more distros…
I continue to have a hard time with it. I desperately want to like it but feel like it doesn’t handle laptop Nvidia right. I keep getting boot to black screen on KDE and have to rfkill unblock on install and just a host of issues I can’t seem to ever nail down. Might have to try again since switcherooctl, but there are some rough edges for me.
Love MicroOS for server though. Rock solid.
For nvidia hardware, use nvidia images of Aurora/Bluefin (or Bazzite if you want gaming out of the box). All the OSes I mentioned are based on Fedora Atomic and offer image options for nvidia proprietary drivers. They even signing the kernel drivers, so you can use Secure Boot.
I have distro hopped my dang brains out with everything under the sun. I’m back to Mint. It works without being an absolute pain and is boring as watching paint dry, which is the point of an OS. I just use it to compute, work, code, and game. it boots and updates eventually.
Hey, may I ask how has it been MicroOS for you? I’m interested in using it for my small server and self-hosting, but I mostly use containers with Docker and I’ve seen that MicroOS comes with Podman by default.
Podman is good, you should try it.
Most docker’s commands can be replaced by podman’s.
Will do, thanks!. Have you used something like Docker Compose? I didn’t have a lot of time before, but I’m still researching and I don’t get what is the “standardized” way of dealing with composed containers
I have never used Podman Compose but it exists. I guess it’s really similar to docker compose.
With podman you can use “Quadlets”, which are systemd files allowing the services to integrate very well with the system (you can use journalctl to see the logs of a container).
Podman supports building, and starting containers (and creating vol‐ umes) via systemd by using a systemd generator. These files are read during boot (and when systemctl daemon-reload is run) and generate cor‐ responding regular systemd service unit files. Both system and user systemd units are supported. All options and tables available in stan‐ dard systemd unit files are supported. For example, options defined in the [Service] table and [Install] tables pass directly to systemd and are handled by it. See systemd.unit(5) man page for more information. The Podman generator reads the search paths above and reads files with the extensions .container .volume, .network, .build, .pod and .kube, and for each file generates a similarly named .service file.
I ended up installing docker. Didn’t want to make a bunch of systemd files. It automatically updates each day and has required almost no maintenance at all. It’s a little strange, but can work great.
