I disabled KDE once, my life has only gotten better since then.

Government funds don’t spend themselves.

hmm, that goes against my experience. and I’m talking about the CPUs.

have you ever had any issues that weren’t noticeable within the first 10-15 minutes of running under load?

have you ever tried undervolting yourself?

you may never have done this kind of optimization before, but when it comes to undervolting, it becomes clear pretty quickly that the wrong settings were chosen. so let me repeat: separate load testing makes no sense for someone who just wants to play games in a cool room during the summer, it’s just a waste of time and electricity. and let’s forget about the careless re-tuning thing; we obviously all undervolt with care, precision, and a ceremonial blessing.

for the current task the stress testing is the gaming itself. so it’s a low hanging fruit here.

undervolting is your best friend

Well, best time to prompt a crapbot to draw it.

I’ve been mulling over this very idea for years, but I just haven’t gotten around to putting it into practice. Could you tell me how it works for you?

Yes, maybe, but do I want to do that? Everything’s going perfectly right now.

I have that conf: /etc/sysctl.d/01-ipv6.conf

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

But that falls under your exception. It seems to me that IPv6 causes more problems than it solves.

Unbiased investigative journalism is an oxymoron.

discussion seem like systemd is the only possible option

I haven’t met a single sane person who would claim that there are no other systems out there. For the most part, people who use systemd say that it’s the best option right now.

I’m long past the age where I try things out just for the sake of it. For me, a tool has to solve an actual problem. Runit fails that test immediately because its dependency management is too weak. Dinit looks like a better fit, but I don’t need it, because my current system works perfectly with systemd, and I have no interest in doing by hand what the distro maintainer already took care of for me.

There is no worse project in the Linux world than that.

Apply the same worries to the kernel, does your panic holds?

Thank goodness I’m not a major distro maintainer and don’t have to deal with all that shit. However, the times I did come into contact with it weren’t as bad as with upstart and sysvinit.

Let me stir up your anxiety with this simple question: that if future version of kernel introduces a breaking change or a bug that affects the whole stack?

That’s UNIX stuff.

systemd works best, scales well and causes less pain at maintaining