Linux is Linux.
We should send all those people, pages and guides suggesting distros to hell.
And then instead we suggest update-schemes (fixed, rolling, slow-roll), package managers and Desktop environments. People with enough brain cells to start a computer are then absolutely able to chose a distro fitting them based on that. Everything else coming with a distro is just themeing/branding anyway...
(and just for the use statistic: Archlinux, Opensuse (Leap and Kalpa), Debian here...)
I’ve been using Arch and Manjaro for couple years each and in my experience they both break regularly. But, for some weird reason, Arch Linux is praised, when Manjaro is shamed upon.
No, there is not some weird reason but actual very good ones.
Things can break on a bleeding edge update scheme. That's to be expected from time to time. But the questions are "why did it break" and "what is done to fix it".
If something breaks on Archlinux it's because of some new package with a issue that escaped testing. Then the fix come out as fast as possible (often within minutes even, but let's assume hours as those things need to move through mirrors first...).
If something breaks on Manjaro it's either because of the exact same reason as above, but 2 weeks later. Because Manjaro keeps back updates for two weeks "for stability reasons", yet doesn't do anything in those 2 weeks. So they just add the same problem later, completely defeating the argumant about stability. Oh, and fixes are of course kept back for 2 weeks, too, because... reasons.
Or it breaks because they fucked up their internal QA. For example by letting their certificates expire again and again and again and again... of by screwing up their very own pacman-wrapper and then ddos'ing the AUR for all users, not only Manjaro ones.
Or -speaking about the AUR- it breaks because they give their users full access to the Arch User Repository (without any warnings about user content being less reliable and used at your own risk) pre-installed. Also they do it on a system generally out-of-date because it lags 2 weeks behind. Which is not what AUR packages are build for (they assume up-to-date systems) and is a straight path to dependency hell and breakings... not because something went wrong but because the whole concept of an out-of-date system not running their own also 2-weeks behind version onf the AUR is idiotic. On the "plus" side they have an easy fix: blame the user, because he should obviously know that an pre-installed part of Manjaro is conceptionally flawed and shouldn't be trusted.
Right decision but for the wrong reason.
Car-brains don't do standard logic, only car-logic...
Hydrogen or battery?
The answer is battery. If battery is an option then the answer is battery. Always.
This will only change if either there is an unlimited amount of free energy available or the laws of thermodynamics stop being valid.
with Apple dominating Europe...
Your own map diagrees, with 100% of the picked examples from Europe having Samsung as market leader.
Stick to a specific distro and train your staff
Linux is Linux. Train your staff to properly use one and they can use them all. "Distro" is just a fancy word for "which package manager and update cycle to we chose and what logo do we put on our pre-installed wallpaper".
Yes, I actually just use Wine with a default prefix and pray it works. If it doesn't (rarely) then the game gets his own prefix to tweak the settings.
you didn’t say what file system your /boot partition was using, so I don’t want to guess
It's actually easy to guess. There is exactly one filesystem UEFI has to support by its specification, everything else is optional... so unless you produce for Apple -because they demand apfs support for their hardware- no vendor actually cares to implement anything but FAT.
When you say system drive this will also have your efi system partition (usually FAT-formated as that's the only standard all UEFI implementations support), maybe also a swap partition (if not using a swap file instead) etc... so it's not just copiying the btrfs partition your system sits on.
Yes clonezilla will keep the same UUID when cloning (and I assume your fstab properly uses UUIDs to identify drivees). In fact clonezilla uses different tools depending on filesystem and data... on the lowest level (so for example on unlocked encrypted data it can't handle otherwise) clonezilla is really just using dd to clone everything. So cloning your disk with clonezilla, then later expanding the btrfs partition to use up the free space works is an option
But on the other hand just creating a few new partitions, then copying all data might be faster. And editing /etc/fstab with the new UUIDs while keeping everything else is no rocket science either.
The best thing: Just pick a method and do it. It's not like you can screw up it up as long if your are not stupid and accidently clone your empty new drive to your old one instead...
So to put this into perspective:
Germany has (again) spend more than 8 billion (the planned budget for 2024) purely on military equipment for Ukraine just in the first half of the year. More than most countries combined (for reference the UK loudly announced the "largest-ever military aid package" ever earlier this year... 0,5 billion in total).
And they simply can't keep this up anymore while at the same time having to cut all budgets at home to stay within constitutional debt limits (PS: No, changing the constitutional debt limit isn't an option. That would require votes from the opposition and they went apeshit obstructionist/populist the moment they were ousted).
And although I have a particularly strong opinion on what will actually happen, let's hope EU countries can finally get their shit together to create a sustainable base for Ukraine support instead of constantly relying on single countries' short term planning.
Mist, verklickt...