

Some people prefer to have a game mod manager working immediately, others prefer their system working for years instead of failing to boot after an update.
Some people prefer to have a game mod manager working immediately, others prefer their system working for years instead of failing to boot after an update.
Literally the first sentence
screw using someone’s personal distro
And all 3 are anonymous…
Hahahaha it really does.
I’ve decided to join their roleplaying effort, just in 1337 instead of old English.
No, dd doesn’t.
I know, I’m just pointing out some of the “hidden magic”.
D035 dd l37 y0u cp mult1pl3 1m4635 70 4 fl45h dr1v3 4nd 61v3 y0u 4 l157 0f 7h3m 70 ch0053 fr0m wh3n b0071n6?
That’s the whole point of stable distros, but people can’t distinguish “stable” from “reliable” so we get comments like “arch is really stable”.
Plasma has a cycle of releasing a bunch of new features and changes, and then squashing bugs every week when they discover them.
Debian is on a 2+ year release schedule, and the packages are frozen long before the release. So plasma might be either working fine, or be broken for 2+ years.
Fedora is semi-stable because it’s on a 4 month schedule, and AFAIK they don’t rush upgrading to new major plasma versions, so plasma works a lot better.
Generally from my experience, plasma works best on rolling distros, while it’s crap on stable ones. Stable DEs like xfce are incomparably better suited to stable distros.
It’s not just a reskin, the MX tools are really useful for beginners and non-technical people.
Currently installed using Ansible, because that’s more sensible than Bash for this imo.
What do you mean? It’s just a few lines to symlink everything for me.
Chrome and Firefox, VScode, Zoom and whatever other random crap
So chrome, Firefox, chrome, chrome, and probably more chrome
Most maintainers are volunteers, but not all volunteers are maintainers…
Besides the obvious non-package work, if you make a single pr for some random package and never again, you’re not a maintainer.
The Nix ecosystem is developed by many volunteers and a few paid developers, maintaining one of the largest open source software distributions in the world.
demanding work that we cannot expect to be done by volunteers indefinitely.
And every package is added and maintained by volunteers.
It’s an obvious vector for malware, arch by default doesn’t come with it, and users have been warned the entire time to check pkgbuild. There’s nothing fishy, it’s just that arch has enough users to be worth it to hit it.
It was either failing before grub or wasn’t in the list, I can’t remember now but I know rollbacks were not a possibility. If I remember correctly I had to reboot once after the install, then update, and then reboot once again to have the updated system boot.
This issue can happen with any distro, though rare.
I’ve used Linux for about 15 years, and that was the only time a fresh install crapped out on me.
Fedora is great, but it’s also the only distro I’ve had fail to boot after a fresh install and update.
Mint for sure. The slower release cycle is definitely better for nontechnical people, but show them how to install flatpaks from the app store.
Damn, the last time I used it I could’ve sworn it was just arch with a wizard and some custom dotfiles. Although that was like 3 years ago.
I never actually used archinstall, only manual and derivatives which were essentially arch with a wizard.
You can choose the de by clicking in the wizard
how to install arch (with btrfs and without frustration)
Download Endeavour and click through the wizard?
Sure it is…