marianarlt wroteHave fun with a very stable system (with occasional breaks from being Arch to begin with [let's be honest here, you don't go rolling distro for the stability factor] :P)
A kid destroyed my Windows partition in 2013. I booted into the Linux partition, tried to repair it and failed.
After that I asked myself, why do I need repair or reinstall Windows instead of just using Linux? Emacs, Chrome, Firefox and Conkeror(a keyboard driven browser) work the same(or better) as Windows. Many development tools in Linux are MUCH better than Windows. And drivers(horrible stories in early days) for wifi and card work out of box. So I just use Linux only.
In fact, I can't use Windows "efficiently" again after I discovered tiling window manager.
Another good news is no one can use my computer again.
This Linux distribution was Ubuntu 12.04. And it is still Ubuntu 12.04. Why I do not upgrade my system? I cann't remember the exact reasons.
Maybe I'm seeking a non-systemd distribution. Ubuntu 12.04 uses upstart. It's not clear which one it will use in next TLS.
Maybe I'm just lazy.
The system itself is stable. But the world isn't. More and more secure protocols deprecate SSL in favour of TLS. More and more websites(gmail, github, gitlab/framagit, etc.) don't support old browsers.
I have learned, the hard way, that there is no stable(unchanged) system if I want to use it to interact with the changing world. Only large changes occasionally or small changes frequently.
As a developer, I suffers from outdated softwares and I'm not so scared when something breaks. So rolling release mode make more sense to me.
marianarlt wroteI've personally become less aggressive towards being against systemd
While I'm seeking and waiting non-systemd distributions, more and more major distributions adopt it. So I migrated one of my laptop and some servers to arch one month ago and tried to live with it:
- manage my services using my favorite supervisor
- start supervisor by rc.local(to avoid wasting time to learn unit files)
- write small wrappers for shutdown, reboot, poweroff, ...
systemd works until it doesn't.
I just wish it won't fail me too quickly before I get familiar with arch. The fact is, it does, in the beginning.
journald use 100M memory after boot. It's 20% of the total memory on a $5 vultr instance. It's almost the
100% memory used by processes after boot. It's insane.
After a quick google search I gave up. I don't know how to fix it, or it could be fix at all.
I don't want to invest my time to learn this bloatware which treats users like idiots(The most responses from developers are "you measure your memory usage wrong").
As consequence, make system
comprehensible is not a goal of them: "You are not capable to manage your system, so we do it for you."
So I gave up living with it and gave obarun a try. Thanks for your installation guide.