2 ms·
Why respond in this dishonest manner? When I left Arch I had been using it for over 10 years. I probably still understand it better than you do. Is your supp
by celticmusic 7y ago
Why respond in this dishonest manner? When I left Arch I had been using it for over 10 years. I probably still understand it better than you do.
Is your supposition that a "misconfiguration" just "happened" randomly over night?
No, it's a rolling release distribution, software on it will break randomly on updates. You need to read their FAQ, even their official document will tell you this happens and it's not their responsibility due to the rolling release nature of the distribution.
- fao_ 7y agoMy main computer was an arch box for about 7 years (I moved computers after 3 years, hence why my other comment says 4, I just remembered my old tower from around 2014 that also runs arch). In that time, the only breaking updates that occurred always had clear solutions on the homepage, with something you could paste in and fix. I stopped using it because systemd randomly hung on boot, for no clear reason (even after debugging it and trying to speed up boot), but I've had that with several other systemd-related distributions, too.
- jolmg 7y agoWhat's dishonest about it? I'm trying to understand the issues that you mean, and the need to configure before getting to work is what I understood you to mean as broken. I'm not talking about misconfiguration; that's different. You emphasized that if you couldn't get straight to work then it was broken. When I can't get straight to work, it's because I need to configure something. I'm using "configure" to mean any sort of maintenance on the machine itself that doesn't involve "real work". If that's not it, then I've no clue anymore about what you mean as broken.
- celticmusic 7y agono one else in this conversation has the same "misunderstanding" that you do. Go ask them for clarification.