Systemd-resolved DNS cache poisoning

Re:Systemd-resolved DNS cache poisoning by kefka on Wednesday November 12, 2014 @09:54AM (#8595643)

Systemd is just not the Unix Way. It's some shit program that requires to be run as PID 1, and takes over the system in the forms of an octopus. And, you need some gods-awful binary program to even read their logfiles. Yes, it's like the Windows registry.

Even Debian has succumbed to Systemd.

[ Parent | on HN ]

Re:Systemd-resolved DNS cache poisoning by Someone1234 on Wednesday November 12, 2014 @10:12AM (#8595752)

I've been thinking a lot about the Windows Registry (and /etc, etc) and I've come to the conclusion that the systems which get it the most "right" is the app model (e.g. Android, iOS, Windows 8).

You see systems like Docker containers, which try to isolate a complete application and its configuration files together, and really that is just a hacky solution to the lack of inherent silo-ing within the underlying design.

While silo-ed apps have their own limitations (e.g. two "apps" using the same configurations) most of them can be overcome with tinkering for the edge cases.

I'd never design a system in 2014 with either Windows Registry (too messy, impossible to manage), or /etc (too inconsistent with itself, also often results in orphan files).

[ Parent | on HN ]

Re:Systemd-resolved DNS cache poisoning by baudehlo on Wednesday November 12, 2014 @10:26AM (#8595821)

The correct analogy would be Event Viewer, not the Registry.

[ Parent | on HN ]

Re:Systemd-resolved DNS cache poisoning by octoid on Wednesday November 12, 2014 @11:01AM (#8596123)

I am afraid sir, that comparing the system take over to the 'forms of an octopus' is most unfair to our dear Cephalopod friends.

I encourage you all to please use the more appropriate comparison : Cthulhu / Cthulhud

http://www.urbandictionary.com/define.php?term=Cthulhu%27d

[ Parent | on HN ]

Re:Systemd-resolved DNS cache poisoning by vezzy-fnord on Wednesday November 12, 2014 @09:56AM (#8595666)

Yes, it's like the Windows registry.

Nope, that would be GSettings/dconf. It's limited to GNOME, thankfully.

[ Parent | on HN ]

Re:Systemd-resolved DNS cache poisoning by custardcream on Wednesday November 12, 2014 @10:11AM (#8595749)

Actually systemd is more like DCOM which is much worse.

The registry is fucking marvellous in comparison.

[ Parent | on HN ]

Re:Systemd-resolved DNS cache poisoning by talideon on Wednesday November 12, 2014 @10:38AM (#8595917)

Nah, the equivalent of DCOM is dbus.

[ Parent | on HN ]

Re:Systemd-resolved DNS cache poisoning by custardcream on Wednesday November 12, 2014 @11:13AM (#8596222)

Which is what systemd is built on. At least on windows COM stays in user space but no, fuck it, lets use kdbus on Linux...

[ Parent | on HN ]

Re:Systemd-resolved DNS cache poisoning by talideon on Wednesday November 12, 2014 @11:42AM (#8596451)

Sure, that's what built on, and that's why the equivalence was incorrect. You'd might as well say that systemd = Linux.

[ Parent | on HN ]

Re:Systemd-resolved DNS cache poisoning by erkose on Wednesday November 12, 2014 @10:00AM (#8595686)

Systemd is a fascist.

[ Parent | on HN ]