I mean, sure Arch is flexible. All good footguns can mutilate me in a bunch of different ways.
I, uh, use Kubuntu LTS (
--minimal-install, so nosnap).Are *buntu flavors risky for my workstation? Should I be considering Fedora?
I would have put OpenBSD in “focus on security”. Or hell The only prebuild thing their is pain, pain and suffering
BSD isn’t linux. Or am I mistaken?
It is not
I actually run OpenBSD on one of my ThinkPads, but I was only including Linux distros in this.
Don’t forget SUSE’s focus on SAP… Which is also Germany I guess
Its Germany’s version of oracle. A strategic reserve of evil.
shitstemd, glibc, bloated kernel, sudo and proprietary blobs are not secure
yet he can’t write a web server with c from scratch. Curious.
(yes I’m mirroring)
Danke für dies handbuch
Sorry I dont speak swedish would you mind translating?
Ha. You want STABLE, use NixOS.
If you’re cannot parse the configuration file, you don’t update. It is perfectly, 100% stable, about 60% of the time (when I change my config file without an error).
nixOS appeals to niche audiences who like to brag about it. I think it is not a good idea to base everything on config files, since there is a lot of room for user error
Not to mention it is a utter pain in the ass.
With that being said, if just the package manager was a config file and there was a reasonable CLI then I could get on board.
The config files literally won’t compile if there is an incompatibility or error in the code.
Also, every distro has an audience who love to brag about it. The worst part of being a Nix user is I can no longer say “Arch BTW”.
Oh you don’t use arch? Don’t worry bud you’ll get there some day.
ITT - “I DISAGREE WITH THE FACTUAL ACCURACY OF THE SETUP AND/OR PUNCHLINE OF YOUR JOKE.”
What else do you expect from germans? Ich bin stolz auf euch, jungs.
I’ll never stop hating that debian is labeled stable. I’m fully aware that they are using the definition of stable that simply means not updating constantly but the problem is that people conflate that with stability as in unbreaking. Except it’s the exact opposite in my experience, I’ve had apt absolutely obliterate debian systems way too often. Vs pacman on arxh seems to be exceptionally good at avoiding that. Sure the updated package itself could potentially have a bug or cause a problem but I can’t think of any instance where the actual process of updating itself is what eviscerated the system like with apt and dpkg.
And even in the event of an update going catastrophically wrong to the point that the system is inoperable I can simply chroot in use a statically built binary pacman and in a oneliner command reinstall ALL native packages in one go which I’ve never had not fix a borked system from interrupted update or needing a rollback
To me the issue is the people calling a system stable because it is reliable, even if it updates unpredictably to changing functionality.
They really should have used the word “static” instead of stable. Stable definitely has connotations of functional stability, and unstable of functional instability.
Average Grandaddy Stable distro hater
depends on workload. Debian has very old packages and can be insecure but it is a set it and forget it type of thing, it is good when uptime is critical for a server. For desktops, or servers that need better security, but can tolerate a little downtime, rolling releases are good too, if you are enough to update frequently, and you should, since updates usually contain a lot of patched vulrenabilities
FWIW I’ve got a Debian server that hosts most of my sites and primary DNS server, that’s been running since Etch (4.0, 2007ish). I’ve upgraded it over the years, switched from a dedicated server to OpenVZ to KVM, and it’s still running today on Bookworm. No major issues with upgrades.
It’s definitely not something that will happen 100%. I’ve also had long standing debian systems that seem to not care. However I’ve had plenty that, for whatever reason couldn’t handle multiple major version hops and just eviscerated themselves, I’ve not had that with arch personally. You may need to download the latest statically built pacman depending on how old it is but that and a keyring update usually has you covered
However I’ve had plenty that, for whatever reason couldn’t handle multiple major version hops
Debian only supports upgrading one major version at a time. If you’re upgrading from Debian 10 to 12, you need to first do 10 to 11, then 11 to 12. Upgrading multiple versions at a time is completely untested and unsupported.
You are maybe conflating stability with convenience.
“Why is this stable version of my OS unstable when I update and or install new packages…”
The entire OS falling down randomly on every distribution during normal OS background operations was always an issue or worry, and old Debbie Stables was meant to help make linux feel reliable for production server use, and it has done a decent job at it.
I mean when I can take an Arch Linux installation that I forgot about on my server and is now 8 years out of date and simply manually update the key ring and then be up to date without any issue but every time I’ve ever tried to do many multiple major version jumps on debian it’s died horrifically… I would personally call the latter less stable. Or at least less robust lol.
I genuinely think that because Arch Linux is a rolling distribution that it’s update process is just somehow more thorough and less likely to explode.
The last one with debian was a buster to bookworm jump. Midway through something went horrifically wrong and dpkg just bailed out. The only problem was that it somehow during all of that removed the entirety of every binary in /bin. Leaving the system completely inoperable and I attempted to Google for a similar solution as arch. Where i could chroot in and fix it with one simple line. But so far as I was able to find there is no such option with apt/dpkg. If I wanted to attempt to recover the system it would have been an entirely manual Endeavor with a lot of pain.
I would also personally label having the tools to recover from catastrophic failure as being an important part of stability especially when people advocate for things like Debian in a server critical environment and actively discourage the use of things like Arch
If the only thing granting at the title of stability is the lack of update frequency that can simply be recreated on Arch Linux by just not updating frequentlyಠ_ಠ
Did you go buster -> bullseye -> bookworm or just straight to bookworm? It sounds like something got screwed up with the usr merge.
Straight to bookworm. Sounds like that’s not supported but that just further shows why i don’t find it to be a functionally stable, or perhaps reliable is a better wording, system. But that’s also just my opinion
it would have been an entirely manual Endeavor with a lot of pain.
It’s funny that your phone auto corrected or you typed a capital E out of habit. I imagine you talk about Endeavor OS a lot lol.
Was using voice to text, it auto capitalizes words at absolute random. However yes i do use EndeavorOS so it comes up from time to time :p
I mean when I can take an Arch Linux installation that I forgot about on my server and is now 8 years out of date and simply manually update the key ring and then be up to date
That won’t work, old pacman versions can’t deal with the fact that packages are now zstandard compressed. In fact, the window were you could successful do the update without a whole bunch of additional work was something like a couple of months. Certainly a whole lot less than a year.
I mean, if you want to use your system pacman sure. But you can just download the latest statically built pacman to do the large jump without issues. However i will concede that is more than JUST keyring update
Edit: another fun way to get around that issue pretty easily. Boot any up to date arch installer, mount the old ass system root to /mnt and just run
pacman -Sy
pacman --sysroot /mnt
Now just normal syu and the live environment pacman will update the old system, arch/pacman has a plethora of easy ways to get around what would otherwise be show stoppers on apt/dpkg :)
No opinion on Debian but as a heavy ArchLinux user I should point out you shouldn’t upgrade without reading the news as occasionally manual intervention is required. Upgrades can and will break things if you’re not careful.
https://archlinux.org/news/openblas-0323-2-update-requires-manual-intervention/
https://archlinux.org/news/ansible-core-2153-1-update-may-require-manual-intervention/
https://archlinux.org/news/incoming-changes-in-jdk-jre-21-packages-may-require-manual-intervention/
While I personally agree with your sentiment, and much prefer arch to debian for my own systems, there is one way where debian can be more stable. When projects release software with bugs I usually have to deal with those on Arch, even if someone else has already submitted the bug reports upstream and they are already being worked on. There are often periods of a couple of weeks where something is broken - usually nothing big enough to be more than a minor annoyance that I can work around. Admittedly, I could just stop doing updates when everything seems to be working, to stay in a more stable state, but debian is a bit more broadly and thoroughly tested. Although the downside is that when upstream bugs do slip through into debian, they tend to stay there longer than they do on arch. That said, most of those bugs wouldn’t get fixed as fast upstream if not for rolling distro users testing things and finding bugs before buggy releases get to non-rolling “stable” distros.
I honestly don’t see this thorough testing. Not for a lot of apps I use anyway. It’s normal tbf even with 2 year you can’t thoroughly test every package for every bug, so you’re stuck with very old bugs a lot more often than people think. And on top of that some packages are so old that instructions you find on their git pages or wherever are too new and don’t work.
Good point! But I recently swapped to Debian 12 from Fedora 41. The latter needing constant updates several times a day. And despite this, it was not stable at all.
Fedora is good on laptops since it has the very newest kernel and thus includes all the latest driver fixes (which are needed for laptops like the Framework where they’re actively improving things). On the other hand, it has the very newest kernel and thus includes all the latest bugs.
… and the latest security patches
Debian also has the latest security patches
Mint: easy
Mint: come for the ease of installation and use, stay because it’s just Ubuntu and Debian under the hood so it has tons of support, and the terminal is right there if you need to out so some real shit.
I think mine doesn’t roll off the tongue in quite the same way.
From my experience of Fedora: would you like to update today? Debian: You’re good bro, no updates today.
5, years, later…
Debian: You’re good bro, no updates today.
I think I’ve put fedora on at least 4 personal systems and it has never caused an issue. It’s so smooth it’s boring in the best way. Switched to it for daily computing abouy 4 years ago. I use a minipc as a media server with Arch and turning it on it’s exciting. Just this fucking morning the default configuration decided that my main audio device was a microphone. Lovely. So flexible.
On the other hand, my server running Arch testing has never had any issues. In fact, the only issue on any of my devices, all Arch testing, was nvidia.
This is a YMMV situation. I had Gentoo running on a minipc for a while and it never had any random issues pop up. Any screw up was fully traceable to configuration and entirely my fault. It was kinda funny. Hope your server stays healthy.
I eventually landed on Fedora too. Its level of “it just works” is amazing.
Right!? Almost everything I need is one dnf command away with minimal setup on my part.
I think, a more serious attempt to summarize openSUSE would probably be: Functionality
Debian, Arch, Fedora and such are all weirdly similar in that they focus so much on minimalism. For example, Debian uses
dashas the default shell, which breaks TTYs, but possibly squeezes out a tiny bit of performance, so I guess, that’s worth it…?i used Tumbleweed with KDE. It is something i can recommend. Not that customizable, but it has tons of features and very stable for a rolling distro. It only breaks if you try to customize stuff too much
still much more customizable than GNOME
Debian only uses dash for the system shell, and it does improve performance a bit given how many shell scripts run on a typical Linux system. Interactive shell is still set to Bash by default.
More accurate i would describe Fedora is:
Adopting Modern features first(Wayland,pipewire,etc Like there is no x mode in most stable Wayland desktops) and only having free and open source Repos(Rpmfusion can be added but its not official and excludes the Kernel drivers).
