News for hackers. Stuff that matters.
Re:Chrony: Comparison of NTP implementations by rnhmjoj on Sunday September 24, 2017 @12:04PM (#15325210)
I hate the binary logs of journald, the unnecessary complexity of stuff like systemd-hostnamed, dbus and the ignore-invalid-options policy but the init system it's actually very good.

I don't want to return to a pile bash scripts with `sleep n` to get the system to boot, even if it's a proven method.

Re:Chrony: Comparison of NTP implementations by dozzie on Sunday September 24, 2017 @12:25PM (#15325311)
This "pile bash scripts with sleep n" was at least debuggable and could be inspected and traced in different ways. With systemd, when something doesn't work as expected (which is often when you do anything that deviates even a little from standard), tough luck.
Re:Chrony: Comparison of NTP implementations by digi_owl on Sunday September 24, 2017 @12:37PM (#15325388)
The sad part is that much of the "standard" is not really standard, but what systemd thinks is "standard".

Or that they cling to "standard on paper" rather than "standard in use", and thus end up rolling back decades of real life usage in the process.

With systemd, perfect very much is the enemy of good. And both unix and Linux go where it is not by being perfect but by being good.

Re:Chrony: Comparison of NTP implementations by dozzie on Sunday September 24, 2017 @01:05PM (#15325512)
> The sad part is that much of the "standard" is not really standard, but what systemd thinks is "standard".

I didn't mean "standard" as in "POSIX 1003.1e", "SUSv3", or "RFC 3549", I meant it as in "whatever is currently most widely in use". Which actually reinforces your point.

Re:Chrony: Comparison of NTP implementations by moe on Sunday September 24, 2017 @12:15PM (#15325266)
Many other dependency/supervisor driven init systems exist (upstart, minit, daemontools, etc.). Upstart even was the Ubuntu default for a while.

One of them should be adopted and fleshed out before systemd causes even more damage.

Re:Chrony: Comparison of NTP implementations by edoceo on Sunday September 24, 2017 @06:24PM (#15326808)
Try OpenRC, really, give it a try.

Simple, sane bash-like scripts, logging like you're used to and so easy to debug, and when you need to do your own custom stuff, simple and just works.

Gentoo showed me this tool a few years ago. So happy.

For years now I've heard loud stories about systemd +1 or -1. Same arguments over and over.

Meanwhile, dozens of my servers and desktops and laptops keep humming along, I've like just never had to fuck with it.

I should buy the OpenRC team some pizza. Thank you!

Re:Chrony: Comparison of NTP implementations by ty_a on Sunday September 24, 2017 @02:54PM (#15325940)
There should be competition but no one is willing to step up to the plate. That's the real issue.
Re:Chrony: Comparison of NTP implementations by dozzie on Sunday September 24, 2017 @03:07PM (#15325995)
That's false. There are several daemon managers designed to run as PID 1, starting with upstart the parent mentioned and you silently dismissed. The problem lays elsewhere.