3 ms·
Knowing little about Arch Linux, I dismissed it entirely, even though a good sysadmin friend uses it exclusively on his laptop. In my personal life, I first in
by jlgaddis 13y ago
Knowing little about Arch Linux, I dismissed it entirely, even though a good sysadmin friend uses it exclusively on his laptop.
In my personal life, I first installed Slackware in 1995 but had converted to Debian by 1997 and I've used that almost exclusively until the last two years or so (I have one RHEL6 and one FreeBSD server). I have, of course, used RHEL and Ubuntu previously in my professional life.
About six months ago, I installed Arch Linux on a new Thinkpad W530. I didn't intend to really use it, I just wanted to see what the fuss was about. It's stuck around and I'm still running it and I haven't had the first problem with it.
I'm not gonna be converting everything over to it, obviously, but it works for me on this laptop (which I do almost 100% of my work on).
YMMV but IWFM.
- clarkm 13y agoWell, I hope you're subscribed to the announce mailing list then. Because breaking changes that require manual intervention do occur, and if you don't deal with them in a timely manner you'll be SOL. Waiting until the last minute to port all my init scripts to systemd was definitely not a good idea.
- chadwickthebold 13y agoYeah, Arch is a great distro for some specific use cases. I loved it when I was in college and had 3+ hours every other week to get my packages un-borked after some update, but nowadays I just don't have the time... Great distro for bleeding edge stuff, though!
- nly 13y agoThey do occur but they're rare. I remember the move from sysvinit to systemd taking about 10 minutes, and I have a 3 year old Arch install that has never outright broken on me after an update. Frankly I remember going through more pain every 6 months from in early Ubuntu days (although that's a lot better now also).