logoalt Hacker News

hylaride • today at 3:19 PM • 2 replies • view on HN

Networking is the biggest cause of issues I've had with systemd, mostly because of the systemd maintainer's insistence on strict adherence to modern RFC's to the detriment of legacy support. This has resulted in my having to deal with gross workarounds for various issues, including this 032 issue with multiple domains: https://docs.aws.amazon.com/linux/al2023/ug/deprecated-al2.h...


Replies

eqvinox • today at 5:12 PM

> maintainer's insistence on strict adherence to modern RFC

…except when they don't and then issues like this are the result. I guess they don't consider themselves viable for a CPE device and don't "feel" like following CPE requirements.

(In itself, good to know that systemd does consider some things out of scope, maybe?)

lmz • today at 3:44 PM

That multiple domain issue doesn't seem to stem from "modern RFCs", just a decision to not be bug compatible with the previous implementation.

> Windows and other Linux operating systems treat the value as a single domain, which results in unexpected behavior.

The parent poster's suggestion to use Alpine is amusing in the context of your problem because musl libc is notorious for sticking to the spec when compared to glibc.