On Saturday, August 29, 2020 1:00:17 AM MST Samuel Sieb wrote: > On 8/28/20 9:40 PM, John M. Harris Jr wrote: > > > Please don't invent a new logic, especially the one that systemd does. > > This makes it very difficult to figure out where in the world the > > configuration file for a given program is. With systemd, sure, it's not > > so bad, as the > > System defaults go in /usr/share/<app>. Admin overrides go in /etc.
If you're going to put defaults anywhere, /etc is the most logical place. When admins want to override, they'll modify the files that are there. See, for example, /etc/resolv.conf, the file used to tell the system resolver what DNS servers to use. By default, it's generated by your installer or by NetworkManager. When modified, it's now using "admin overrides". > > command will tell you where the unit file is. There's no such command for, > > for example, chronyd, httpd or any other program that itself isn't using > > such a convoluted configuration system. Even systemd wouldn't work if you > > blew away / etc. > > > It should. If not, that's where they want to get to. What is the actual benefit of this? Needlessly breaking existing configuration, making it impossible to cleanly upgrade systems, or write logic that takes into account the existing configuration of a given program? If you blow away /etc/, you will have a well and truly broken system. If you want to start a configuration from scratch, re-install. There's nothing wrong with that approach, and it works very well. This has been the case for nearly three decades now. -- John M. Harris, Jr. _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
