Merge conflicts to the main branch? I've never even heard of an org where it's OK to force-push to main. That's wild! And a huge red flag, that ought to be fixed at priority zero. Wow.
My understanding is /etc/redhat-release needs to be there because some (dumb) blob drivers specifically check that file to see if you're running a compatible RHEL system before it'll even attempt to install.
At a previous job, we had a wrapper script that swapped the file out before attempting to launch Dell software installers/firmware updaters, because they sometimes checked for hardcoded exact strings like that in there, and errored out, and whether or not it did that varied back and forth over the years.
In my past experience as a sysadmin, some vendors will only release drivers (as binary blobs) for RHEL. EMC PowerPath comes to mind, granted that's kind of a moot point now that the FOSS kernel MPIO drivers are good enough, but I'm sure there's other such examples that exist to this day.
It's not too surprising when you realize that Fedora is really just a testbed for future RHEL iterations, once the packages involved have been field-tested and hardened. It's similar to how Debian branches progress (unstable -> test -> stable).
True, but it always comes off as sounding a bit pretentious to me since the social norm (as far back as I can remember) has been to simply refer to it as "math".
It was much, much earlier than that - analog car or suitcase phones were well known before digital arrived. It was a trope in 80s movies or TV to have someone use one since it meant they were rich and/or important.
My assumption is that the nomenclature came from buying one from the phone company. There were other radios around but they weren’t interoperable with the phone network.
I have, and last time I looked it deviated from Ruby in entirely pointless ways that makes it fairly uninteresting to me. I get they want it to be its own language, but it'd have been far more interesting to me if it stayed as close as possible wherever it could.
