Re:Systemd, 10 years later: a historical and technical retro...
by creshal on Tuesday August 06, 2024 @05:44PM
(#41175715)
Now for the weird part: Redhat wrote both NM and sd-nd, and decided what servers really need is NM by default, and getting a server to actually use sd-nd is like pulling teeth on RHEL. Completely baffling.
[ Parent
| on HN ]
Re:Systemd, 10 years later: a historical and technical retro...
by ChocolateGod on Tuesday August 06, 2024 @06:06PM
(#41175911)
NetworkManager can read old style sysconfig network configuration, which is still used to this very day even if Red Hat wishes you wouldn't, and you really shouldn't.
Re:Systemd, 10 years later: a historical and technical retro...
by sophacles on Tuesday August 06, 2024 @06:02PM
(#41175872)
I don't know why Redhat would do that, but I've never used RHEL - I quit the redhat and derivatives in the 90's due to rpm hell, and never looked back.
Re:Systemd, 10 years later: a historical and technical retro...
by creshal on Wednesday August 07, 2024 @02:30AM
(#41178755)
A new job forced me to get intimately familiar with how fractally dysfunctional RHEL and derivatives still are, and the only thing more baffling than Redhat's self-sabotaging decision making process is why anyone would voluntarily use it.
I hope we can finish the Debian migration soon.