Not a single comment about Kali that I can pick a fight with?? So disappointed rn
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
Endeavour
Went straight from ubuntu to fedora so I guess I skipped the whole ride.
Where does sadistic curiosity about Slackware fit on this graph after daily driving OpenSuSE Tumbleweed?
Being a Debian guy for a long time, now Guix.
Damn I jumped right from Pop_OS to Endeavour, then plunged into Arch before running back crying to Endeavour...
I skipped that whole initial peak: started on Ubuntu 20 years ago, moved to kubuntu after unity and moved to tumbleweed 6 months ago.
I went from Ubuntu to Mint to Debian and, now, Guix; soβ¦I dunno.
Gravity brought me back to Arch from Fedora.
I use Debian and Kali funnily enough. But then again im studying cysec.
20+ years in, I just use the tool I know will get the job done.
LMDE on the laptops.
Arch on the media/gaming rig.
OpenBSD on the writing machine.
Linux Mint and haven't done anything else for over a year.
Ok this describes me annoyingly well. Ubuntu, then Manjaro, then Arch, and now Gentoo. Now I don't really want to go any further because I quite like this distro :p
Pretty sure my journey looked something like:
- Ubuntu for a while
- A furious bout of hopping experiments: Debian, ElementaryOS, Crunchbang, MX Linux, Fedora
- Arch for a bit, but it was too much struggle
- Ubuntu for a while, embracing the "vanilla" lifestyle
- Manjaro for a while. It seemed to solve my previous issues with vanilla Arch.
- EndeavourOS, basically a better Manjaro.
- NixOS, which had a significant learning curve but ultimately gives me the most control and repeatability for all of my machine configs. Still daily driving this on my desktop, router, and some web servers.
- Tried out Fedora Atomic on my old laptop out of curiosity. Installing packages was ultra slow. Workflows were too annoying.
So I think the graph is actually pretty reflective of my own experience, aside from some of the specific distro choices during my peak ignorance phase, and obviously I ended up at NixOS which isn't even on here.
ironically started on fedora and debian like 20 years ago (which i hate is 2006ish instead of 1976 T_T); mostly for servers.
now i'm on mint in my first foray into using it full time as a desktop so i know most of the cli and backend stuff and it's just getting used to the ui and desktop parts.
I feel like nixos doesn't belong on this meme, and I'm happy it's not. While it's technically Linux, I feel like it's different enough that learning nix only teaches you a bit about Linux and a lot about nix.
I run Fedora in the Valley of Despair.
30 years of using Linux and I think this chart is whack. RPM based distros run by enterpises are the worst. I was happier with Slackware than Fedora. π€£ I only use those when work forces me too and after the CentOS and SLES fiascos - F that noise. I'll only recommend debian for work servers unless there are STIG/FedRAMP security requirements and then it's begrudgingly over to Ubuntu.
When work isn't in the way: EndeavourOS on my desktop, Debian on my servers, and debian/alpine for my containers or better yet; golang and scratch.
Im using Debian but Iβm definitely at the end of the downward path of the first spike
After running arch for a long time, I just installed the sway community edition of endeavoros on all my machines. It works well, while allowing me to use tiling without having a ton of configuration time.
Fedora Silverblue. My version of "mount stupid" (or "valley of despair") probably.
Ubuntu: they tell you its easy, but in fact is a huge pain in the ass and breaks. Last two installs for projects I was working on were broken out of the box.
I remember trying Ubuntu 4 and wondering what the fuss was about. It IS the despair. Nice fonts and colors though.
Arch. After every update I check what broke. And then discover things I forgot to check.
I am still not sure if it's already safe to upgrade VirtualBox and iio-sensor-proxy, but I am too lazy to just downgrade them yet again.
So I just...
IgnorePkg = iio-sensor-proxy # Issues in Wayland after suspend
IgnorePkg = virtualbox virtualbox-host-modules-lts virtualbox-host-dkms virtualbox-guest-iso # Segfault in 7.2.x, reverted to 7.1.8 - see sys-management-log.txt entry 2025-08-29
If you're curious about the log entries:
2025-07-06:
downgraded iio-sensor-proxy to 3.6-1 as 3.7 caused issues after suspending
added iio-sensor-proxy to IgnorePkg in /etc/pacman.conf
2025-08-29:
downgraded virtualbox packages to 7.1.8 as 7.2.x was broken (segfault)
installed linux-lts-headers as the downgraded virtualbox suddenly wanted that
removed and reinstalled related packages a couple of times (virtualbox-host-modules-lts, virtualbox-host-modules-arch, virtualbox-host-dkms), as well as switching between linux-lts and linux. Hopefully that didn't create any brand new funny business.
I want to die
added IgnorePkg = virtualbox virtualbox-host-modules-lts virtualbox-host-dkms virtualbox-guest-iso to /etc/pacman.conf
I recommend writing some documentation about your system. My Manjaro install became a total unknown mess after a while. I know I had to create some symlinks at some point to fix something, something something custom "XDG_CONFIG_HOME" dir with separate theme to un-break Cisco Packet Tracer on dark theme, edited startup script for Packet Tracer.
On one Ubuntu VM I edited a bunch of config files that I didn't remember so it was just don't touch it while it works.
But hey, I feel better after knowing that during high school our internet was down for weeks because something broke on main proxy server and nobody had documentation for the 2 decades old backup server, including the password, so it just ended up running in a "don't touch it" mode, except that it also limited download speed on unknown PCs (based on MAC) to something like 32Kbps, which after 20 years meant nearly any PC so the solution was to copy MACs from basically ewaste.
Anyway... write documentation for what you do.