100%. I’ve got servers running arch for the past 5 years or so and they’re the most stable systems I’ve got. I got so tired of the painful upgrade paths on “stable” distros so decided to switch a server to a rolling release.
After I found arch got security patches into the repos faster than the stable distros could backport, I decided to switch them all over.
I’m even a mad man and have them self update with a script that checks informant (or something, can’t actually remember) for installed packages against news. If no installed packages are found in news, it continues with the scheduled update.
Especially when customizing the kernel is the default experience with Gentoo, reducing the theoretical attack surface even more if you know what you’re doing.
If you want to have at least some thrill, use testing repos.
I had to fix GitLab two (2) times due to the main package not being linked against testing libraries (it took 10 seconds to ln -s the new to the old version), and had one breakage due to dovecot revamping their whole config system, but publishing no example/useful docs.
100%. I’ve got servers running arch for the past 5 years or so and they’re the most stable systems I’ve got. I got so tired of the painful upgrade paths on “stable” distros so decided to switch a server to a rolling release.
After I found arch got security patches into the repos faster than the stable distros could backport, I decided to switch them all over.
I’m even a mad man and have them self update with a script that checks informant (or something, can’t actually remember) for installed packages against news. If no installed packages are found in news, it continues with the scheduled update.
It’s glorious.
I fully endorse gentoo and arch in prod
Especially when customizing the kernel is the default experience with Gentoo, reducing the theoretical attack surface even more if you know what you’re doing.
I was too lazy for scripting the update to check the news and just get a mail when the update has issues… or should get one.
In reality I check if the email process still works once every blue moon because I didn’t get one from a failed update in years.
If you want to have at least some thrill, use testing repos. I had to fix GitLab two (2) times due to the main package not being linked against testing libraries (it took 10 seconds to ln -s the new to the old version), and had one breakage due to dovecot revamping their whole config system, but publishing no example/useful docs.