When you run OpenSUSE, you can feel it was made by Germans.
The installer is a beautiful example of German engineering.
The package manager is a perfect example of German over-engineering.
If you run it with KDE, you have 2 redundant GUI admin tools for every config in the system, and 4 for setting up printers.Yeah that sounds like a typical BMW engine layout.
It’s amazing how OpenSUSE got my laptop’s valve covers to leak oil.
As the owner of many old German cars this is funny but only because it means no one read the technical manual that came with the car
As the former owner of an E36 and then an E90 I can tell you that the more modern ones still piss oil just as badly. And the consequences can be much worse (read: expensive) to boot.
Hey the BMW engine that had 2 redundant everything was pretty awesome because half the engine could die and it’d keep going as an inline 6. It was 2 of everything. ECU, Distributor, even fuel pumps and rails
German engineering.
I can hear this gif. I guess it’s time to have my colonoscopy.
Sees “Germany”
Die Kommentarspalte dieser Pfostierung befindet sich ab sofort im Besitz der Bundesrepublik Deutschland meine Kameraden!
Ich bevorzuge:
𝕯𝖎𝖊𝖘𝖊 𝕶𝖔𝖒𝖒𝖊𝖓𝖙𝖆𝖗𝖘𝖊𝖐𝖙𝖎𝖔𝖓 𝖎𝖘𝖙 𝖓𝖚𝖓 𝕰𝖎𝖌𝖊𝖓𝖙𝖚𝖒 𝖉𝖊𝖗 𝕭𝖚𝖓𝖉𝖊𝖘𝖗𝖊𝖕𝖚𝖇𝖑𝖎𝖐 𝕯𝖊𝖚𝖙𝖘𝖈𝖍𝖑𝖆𝖓𝖉
Ahoi, Genosse! Wie läuft die Germanisierung? Verbreiten Sie erfolgreich das Wort von Linux in Ihrem Heimatland?
(Übersetzung von DeepL)
Ohhh ich spreche auch Wurst. Wie geht es ihnen mein Herr, toetet den fuehrer und benutzt Linux statt Fenster.
Wir sprechen Kraut, bitte sehr.
Nixos: everything everywhere all at once
Good for you there wasn’t an “ease of use” or “intuitive” field.
I’m still a Linux noob all things considered, and I’ve been using NixOS for six months or more.
It is HARD, but I see the true value of it. I will never need to reinstall Linux because I broke it, that’s simply impossible.
If I ever need to migrate my system, it’s all backed up to github. With a single
Bash update.sh
every single .config file backed up, system upgraded, all packages updated.
I just love Nix, it’s the perfect OS for me.
Now I just need to learn how to use flakes…
Sidebar: I’ve never asked before, but maybe someone can help me out. If I install a flake of an application, am I supposed to add it to the existing flake, or can I modulate flakes?
I’ve noticed when installing the nixvim flake it generates a new flake and it runs when I issue the
nix run ~/.dotfiles/nixvim/flake.nix
command, but I don’t want to have to run that command every time. I feel like making a fish abbreviation isn’t the correct way of doing this.
So I’ve only been using nix about a year and only used flakes. I use in two ways.
First, I have my main nix flake. Most everything is controlled from that. It has several outputs from full blown nixos builds per host or some home manager builds for non-nixos systems.
Third-party flakes I use as inputs to my own flake then use the override system to inject them into nixpkgs. Then I just install whatever like normal from nixpkgs. I can either override an existing pkg (neovim nightly replaces regular neovim for me), or you can just add as a new package to nixpkgs by using a different attribute name.
Second way is for projects with their own repo. I’ll add a project flake that has a devshell with direnv so as soon as I enter that directory it sets up a sort of virtual environment just for that project. You can add outputs to it so others can use as a third-party flake.
My main starting point was https://github.com/Misterio77/nix-config for this design.
Terminal, Terminal, Terminal, German Terminal
Console, Console, Console, Konsole
Konsole must be a KDE app, but since KDE is a German project…
Hmm… k.de
Helau! Ach warte…
do you use lynx for web browsing?
Who doesn’t?
I mean version 2.9.2 just came out in May.
*Links 🇩🇪
??
Links means Left in german. Same pronunciation. Bilingual play on words if you will.
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
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ಠ_ಠ
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/
I mean, sure Arch is flexible. All good footguns can mutilate me in a bunch of different ways.
Danke für dies handbuch
ITT - “I DISAGREE WITH THE FACTUAL ACCURACY OF THE SETUP AND/OR PUNCHLINE OF YOUR JOKE.”
I would have put OpenBSD in “focus on security”. Or hell The only prebuild thing their is pain, pain and suffering
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.
Qubes is the actuall security distro tho.
How slow is qubes? I imagine that virtualising everything is slow. Does it have a containerised mode?
I mean, I’m on Debian and I’m on the same install instance I’ve had for almost four years now. I’m constantly reading about how some of you people keep hosing your other distros with a normal update…
Lol, I ran 5 years on arch without a break.
Now 6 months of Bazzite without a break.
I think the age of distros shipping severely broken updated is over. And it was always, ALWAYS grub that broke after an update on mint and opensuse 10 years ago for me.
Four years? Some rookie numbers you got there.
Maybe they mean four year uptime…
Flexibility translates to unpredictable.
I’ve never had any issues with my Arch install being unpredictable. It has always worked exactly as I expected it to, even though I update it every couple of days.
It has always worked exactly as I expected it to
Just expect it to break, then it will behave as expected taps head
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)