Bazzite. It’s based on Fedora uBlue so it’s technically Fedora, but being an immutable OS, it works quite differently enough that it counts as its own distro. For instance, you don’t use dnf or yum to install stuff, you’d use Flatpak/Distrobox/Nix. Updates are done using the rpm-ostree command, and it’s effectively a rolling release model, but atomic in nature so you get none of the instability that you’d get in a typical rolling release.
Give Zorin a try. It’s based on Ubuntu but even more user friendly - so much so that my elderly mother has no issues using it, she even prints and scans (a Brother MFD) and has no issues.
I’ve only started using yadm recently so I may not be able to elaborate in detail, but for me the main draw for using yadm (as opposed to Ansible, which I use at work) is the simplicity. It’s basically just a bash script that uses git, so there’s no dependencies besides git and tools installed on most Unix systems. Ansible felt like overkill for what I needed, ie just something to manage and sync my dotfiles.
Also, maybe it’s personal bias, but I really hate installing/using Python-based programs - they often tend to go wild with their dependencies and eventually break. I recall trying to install Ansible on a Raspberry Pi at some point (via pip) and it failed because one of the dependencies couldn’t be compiled for whatever reason. I gave up after trying to fix it for a while, and dropped the idea. I’ve had similar experiences with other large Python projects, there’s always some drama. Why is why I prefer compiled binaries or simple shell scripts like yadm.
I’ve no issues using Ansible at work though. We use it on RHEL so it’s quite stable and doesn’t have the dependency issues you’d get on a bleeding-edge, ever-changing, end-user system. Plus it really shines at the Infrastructure as Code stuff so we use it to automate everything from networking gear to VMs. But I feel it’s overkill for something as simple as syncing a bunch of text files.
I am also thinking about making my own image based on silverblue. there is a video made by bigpod a youtuber about how to make your own custom ublue image
Personally, as a gamer, I use Bazzite, but recently I’ve rebased to a fork of it with my own customisations, and it’s been amazing.
Distrobox > Toolbox btw. Both use podman behind the scenes but Distrobox is a bit more easier to use/fleshed out for desktop usage (eg makes it easy to export/integrate container apps with your the host).
I’d also recommend checking out Nix for installing any packages not on Flatpak or your Distrobox distro, as Nix has its own advantages since it’s you’re running real application binaries directly on your host OS, instead of an exported script (as in the case of Distrobox), so you get better/direct access to system resources and won’t face some of the quirks/bugs you may get from running a containerised app.
That’s only true you succumb to the hardcore Nix fanatics and follow their recommended “declarative” way. However, Nix, as a package manager, is perfectly usable - and accessible - with the imperative way, without having to subscribe to their religion and learn their language and terminology.
In the imperative path, Nix is as easy to use as any other package manager, yet it still retains many of the unique Nix features such as versioned packaged, instant rollback, non-root user-based installs etc.
It’s a shame because Nix is actually really cool and very easy to use if used this way - and especially useful on immutable distros, locked-down systems or distros which have a limited number of packages - but unfortunately, most people are missing out because the fanatics keep preaching the declarative way as if it’s the only option out there.
This was already fixed in 6.1.66. Both are “old” kernels, so it’s nothing to worry about, unless you/your distro was deliberately staying on 6.1 for some odd reason (yes, I’m aware 6.1 is LTS, but so is 6.6).
I have been using Windows since 3.1 with MSDOS 6.2 since forever and I have seen everything from Microsoft. At the same time I’m a senior Microsoft engineer and have been for more than a decade
Same here! Grew up using DOS and Win 3.1, and been a Windows sysadmin for a long time. But over the past few years I’ve been growing increasingly dissatisfied at the direction Microsoft’s been going in, particularly the way they’ve been shoving their half-baked cloud services (and telemetry) onto us, and enterprises, being married to MS, have no choice but forced to comply. At least, that’s the case where I live, companies just lap up every new thing Microsoft does and treat it like the next best thing since sliced bread.
I was being turned from an engineer into a middleman, a lackey at the mercy of MS, and I didn’t like it one bit. I hated the thought of having my entire career being dictated by one corporation. So I quit my job and finally managed to land a Linux role this year and I’m so much happier. To be honest, it feels a bit weird throwing away my veteran MS hat and all the knowledge that I gained over the years and going back to being a total noob (at enterprise Linux that is), but I’m also learning a lot of cool stuff, but more importantly, I love being in control of our systems again, and no longer being at the mercy at a monopolistic mega corporation.
As others have said, there’s Vanilla and Endless, but both use GNOME.
Is there a reason why it has to be Debian? With an immutable distro, you won’t be using traditional package managers anyway (like apt), all have the same stability factor, and with the same systemd + KDE, it’s more or less the same experience regardless of which distro you go for.
One of the key usage patterns of an immutable distro is using a container to install your extra packages. So you could go for a Fedora-based immutable KDE distro like Kinoite, and set up a Debian container where you can use apt and other Debian tools.
As long as it doesn’t break I would take this over any alternative minipc
May I ask why though? One of the biggest advantages of using a MacBook is the performance-battery efficiency. If you’re going to get a Mac mini and loading Linux, you lose that advantage.
Unless you’re looking specifically for an ARM64 machine for whatever reason, I think an AMD mini PC, say something like the Minisforum EliteMini UM780 XTX would be technically a better option - you get dual NVMe, dual 2.5G network ports, USB 4.0, Oculink for even more b/w than Thunderbolt, and far more I/O options in general. Not to mention, excellent Linux support.
It’ll really depend on your local job market. I was on a serious job hunt earlier this year and I couldn’t find a single Linux job which asked for LFCS certs. There were a couple which asked for Red Hat certs though. Of course, this could be specific to where I live, so I’d recommend looking at some popular job sites for where you live (+ remote jobs too) and see how many, if any, ask for LFCS, and you’d get your answer.
Should I focus more on dev ops? Security? Straight SysAdmin?
From what I’ve seen so far, the days of “traditional” Linux sysadmin roles are numbered, if not long gone already - it’s all mostly DevOps-y stuff. Same with traditional security, these days it’s more about DevSecOps.
As a modern Linux sysadmin, the technologies you should be looking at would be Ansible, Kubernetes, Terraform, containers (Docker mainly, but also Podman/LXD), GitOps, CI/CD and Infrastructure as Code (IaC) concepts and tools.
Some Red Hat shops may also ask for OpenShift, Ansible Tower, Satellite etc experience. IBM shops also use a lot of IBM tools such as IBM Could Paks, Multicloud Management, and AIOps/Watson etc.
And finally there’s all the “cloud” stuff like AWS, Azure, GCP specific things - and they have their own terminologies that you’d need to know and understand (eg “S3”, “Lambda” etc) and they have their own certs to go with it. I suspect a “cloud” cert will net you more jobs than LFCS.
So as you’d probably be thinking by now, all of the above isn’t something you’d know from just using desktop Linux. Of course, desktop Linux experience is certainly useful for understanding some of the core concepts and how it all works under the hood, but unfortunately that experience alone just isn’t going to cut it if you’re out looking for a job.
As I mentioned before, start looking for jobs in your area/relevant to you and look at the technologies they’re asking for, note down the terms which appear most frequently and the certs they’re asking for, and start preparing for them. That is, assuming it’s something you want to work with in the future.
Personally, I’m not a big fan all this new tech (I’m fine with Ansible and containers, but don’t like the industry’s dependency on proprietary techs like Docker Desktop, Amazon or Red Hat’s stuff). I just wanted to work on pure Linux, with all the all standard POSIX/GNU tools and DEs that we’re familiar with, but sadly those sort of jobs don’t really exist anymore.