this post was submitted on 06 Jun 2025
48 points (84.3% liked)

Linux

7654 readers
298 users here now

A community for everything relating to the GNU/Linux operating system

Also check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
Ategon@programming.dev
anzo@programming.dev
dwraf_of_ignorance@programming.dev
48
Should we be wary of Red Hat? (lemmy.cafe)
submitted 23 hours ago by propitiouspanda@lemmy.cafe to c/linux@programming.dev
71 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] nanook@friendica.eskimo.com 2 points 10 hours ago

@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.