They were bought by IBM a few years back, but even aside from that they’re a corporation and they care about making money above all else.
It looks like Red Hat is doing its damnedest to consolidate as much power for themselves within the Linux ecosystem.
I don’t think the incessant Fedora shilling is unrelated.
It seems like there isn’t much criticism of the company or their tactics, and I’m curious if any of you think that should change.
I mean, systemd-networkd and systemd-timesyncd are both completely independent and are not required by systemd. I use connman and chronyd on my arch box and systemd gives not one fuck.
There’s still some totally valid concern to be had over how bundled a lot of this stuff is, but it’s not all one big blob.
@Badabinski @just_another_person @rumschlumpel @propitiouspanda Yes but they are becoming the defaults on many distros. In particular systemd-resolvd is an issue because it enforces the 512 byte limit on txt records. The problem with doing this is many large sites have spf records longer than 512 bytes and fail to break them up into separate txt records, so if you enforce this limit and they initiate mail from one of the truncated hosts, it gets rejected. This is not good and so I’ve worked around this by disabling networkd-resolvd and installed bind9 instead. I’ve actually had no problem with timesync but why re-invent all the wheels? To me it seems Poettering is a control freak and wants to take over my systems.