Its approach to the /etc dir was great. I haven’t used it but read the documentation. Basically, all software come with default config files in /usr/lib/config or some directory like that. You create a config file in /etc only if you want to override some defaults, and if you want to reset all configuration you simply delete all files in /etc. I think it is a great system. Removes the clutter from among the user created config files and enables one to make an etc-files repo and keep track of system configuration via git, just like people do with their dot files and user configuration. But other than that, I had no reason to try it.
Its approach to the
/etcdir was great. I haven’t used it but read the documentation. Basically, all software come with default config files in/usr/lib/configor some directory like that. You create a config file in/etconly if you want to override some defaults, and if you want to reset all configuration you simply delete all files in/etc. I think it is a great system. Removes the clutter from among the user created config files and enables one to make anetc-filesrepo and keep track of system configuration via git, just like people do with their dot files and user configuration. But other than that, I had no reason to try it.Is that not the standard unix approach? Freebsd has /etc for OS, /usr/local/etc for installed apps, with config from a similar directory
even in a fresh install, my
/etcdirectory is full of config files that I haven’t created. in clear linux, it starts completely empty.