2 ms·
Having no files in /etc is considerably less discoverable. It can be handled with good documentation or example files in /usr/share/doc but it's still harder t
by ars 11y ago
Having no files in /etc is considerably less discoverable.
It can be handled with good documentation or example files in /usr/share/doc but it's still harder that way.
Of course there are downsides that this article brings up. But is the problem simply the existence of a file in /etc ? Because that doesn't seem to be a problem to me, instead the problem is upgrades that are harder because they have to merge changes.
Seems to me the solution is to use 3 way diffs like how source control system do it, and update configuration files automatically as much as possible.
- joosters 11y agoI love the discoverability of /etc files, and the ability to read & edit them with whatever tools you like. If the files only included changes to default settings, and the defaults are hidden away in program binaries, how are we to discover what settings even exist in the first place? Verbose /etc config files are human-friendly and that's a good thing. Managing updates and merging config changes is still do-able. The logic to do the merges might be more complicated, but I'd rather let the complicated stuff be handled by the upgrade tools and not forced upon the user.