160
My experience with Arch
(sh.itjust.works)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
The reason people say that Arch is unstable is that you are expected to read the news on the website before every update or else your system is liable to be broken -- and sometimes it will break in spite of that. Oh, and the expectation is that you'll be updating multiple times per week, and if you don't, you will soon be in a situation where to install any package you must update your entire system.
Most other distros place no such expectations on the user.
One time I did not update an arch system for something like 6 months... You can't immagine the troubles I needed to go through to get it into a working state.
I have had multiple systems with no updates for a year.
The biggest pain is always that the keyring is out of date and it does not want to install packages signed with newer keys. Once you have dealt with that once or twice, it is quick and easy to resolve and the rest of the update generally just works.
Yes, the keyring is a pain, also because I like to manually check all the keys. But then what often happens is that lots of configuration options have changed and you have to go through bunch of software to find out which exact package is now misconfigured and makes your system not work as it should.