And cause a lot of unnecessary reading and writing, which on an SSD is not a good idea, and especially not for people who’ve already used up almost all of their storage space.
If I had known pacman was still running in the background, I wouldn’t have rebooted.
Not pacman, but the pamac daemon — yes, it utilizes a daemon at the backend.
It was a very easy situation to avoid… if you have the right knowledge, which I didn’t at the time and you can’t expect everyone to read everything about an OS before using it.
I hate to have to say it, but with Arch and Arch-derivative distributions like Manjaro, yes, you do have to put in the effort.
Manjaro is not a kitchen sink appliance the way some other distributions — like Ubuntu and derivatives — attempt to be. It’s aIso not a distribution aimed at refugees from the Windows world.
For that matter, GNU/Linux has never been about providing a safe haven for ex-Windows users or an alternative to Windows. It’s an alternative to proprietary UNIX. And Manjaro concretely — as well as Arch and other Arch-derivatives — is a distribution for people interested in GNU/Linux itself, and willing to learn and get their hands dirty. And needless to say, this comes with a certain requirement for responsibility.
Let me pour it into a metaphor. If you’ve been using Microsoft Windows, then you’ve been driving a 2-wheel-drive pickup truck with an automatic transmission. Using GNU/Linux on the other hand is like driving a medium-to-heavy-duty lorry with a 16-speed or 18-speed unsynchronized range-and-splitter transmission, and a driven tandem rear axle with three manually locking differentials.
Nobody’s telling you you’re not allowed to drive it, but you’ll still need to learn to do so first. You will not succeed if you don’t learn. And no, that doesn’t mean you have to become a mechanic or an engineer. But you do have to at least understand the machinery involved.
And that, then, is why I wrote this a while ago… ![]()