Half of them probably will. People are like that.
Many times, I have seen people switch tech because something is missing or has changed…and they switch to something that also does not have it. Boggles my mind.
LeFantome
joined 2 years ago
It could be that /dev/sdb2 really does not exist. Or it could be mapped to another name. It is more reliable to use UUiD as others have said.
What filesystem though? Another possibility is that the required kernel module is not being loaded and the drive cannot be mounted.
Nothing that uses apt is remotely bullet-proof. It has gotten better but it is hardly difficult to break.
pacman is hard to break. APK 3 is even harder. The new moss package manager is designed to be hard to break but time will tell. APK is the best at the moment IMHO. In my view, apt is one of the most fragile.
COSMiC has made Iced and Smithay stronger. Now Niri is based on Smithay. I for one are happy they spent their time on something other than GNOME.
GNOME has been shedding market share to KDE and now COSMIC is going to take a chunk of the rest.
Sour grapes.
Unbelievably ignorant take.
Arch and its forks are, in my view, the BEST options for a daily use desktop.
FreeBSD has made a real laptop push recently and 15.1 is supposed to offer KDE out of the box.
Depending on your hardware, it is really viable now.
/tmp should be just that (temporary).
There should not be any ill effects to completely empty /tmp
Some distros put /tmp on a ram drive that gets created fresh (and empty) with each reboot.
Almost everything you care about should be in /home so back that up. Many people keep it on a separate partition or drive to make changing distros (or reinstalling the existing one) easier.
Most of your system config is in /etc so you may want to make a copy of that too.
But the proper process on Linux is not to re-install. It should not be necessary.
On top of this, part of the reasons to use containers is that you can create and destroy them at will while leaving your host tidy and stable. I use Distrobox quite a bit for this reason.
Decent point. Not every grandmother is my grandmother. And a 21 year old that has only used phones and tablets to consume content may actually be less tech literate than an older person with no screen experience that knows how to fix their car, blender, or sewing machine.
If you install a kernel from the Arch repos, DKMS will build the kernel module for you automatically as well as the initial RAM disk and boot entries. Kernel upgrades take a little longer but you do not have to do anything manually.
It will work with custom kernels too but, if you do build your own kernel, you have to make sure a couple of options are selected.
I can almost guarantee that the problem you encountered was an outdated archlinux-keyring that meant you did not have the GPG keys to validate the packages you were trying to install. It is an annoying problem that happens way too often on Arch. Things are not actually screwed up but it really looks that way if you do not know what you are looking at. One line fix if you know what to do.
It was my biggest gripe when I used Arch. I did not run into it much as I updated often but it always struck me as a really major flaw.