[kybernetyk]

Ok, I'm speaking purely from my experience and there's a big chance that I'm stupid but:

I've tried running Arch as my main OS in the last year. I needed a weekend to configure the OS and even wrote a little daemon to handle the conservative fan spin ups on my overheating Macbook Pro. After that it was great as long as it lasted.

But then the OS just died 3 times. What had I done? A simple

> pacman -Syu

was enough. Whenever there was a bigger change (a new kernel, new init system, etc.) a simple update would render my Arch installation unbootable. And to get everything to work I had to waste hours (in one case days because of re-install) to get it to work again.

That's not something I want from an OS I'm using productively.

[atondwal]

If all the initscripts and kernel updates break Arch, then you probably made a mistake or two in some conf file installing it. (eg not having /boot correctly in the fstab will break you on every kerenl update, for example)

[kybernetyk]

Maybe I did. But my point is: I need a system that just works without constant maintenance from my side. So Arch is not really for me.