3 ms·
This is an increasingly solved problem in the post-systemd world - /etc contains local configuration, system configuration is in /usr. We (CoreOS) support you d
by mjg59 10y ago
This is an increasingly solved problem in the post-systemd world - /etc contains local configuration, system configuration is in /usr. We (CoreOS) support you doing mkfs on / in order to return to a default configuration built from the /usr config.
- teacup50 10y agoIf that's your definition, then FreeBSD and Solaris solved this without paying the systemd tax, via ZFS-based boot environments. https://www.freebsd.org/cgi/man.cgi?query=beadm&sektion=&manpath=freebsd-release-ports https://www.freebsd.org/cgi/man.cgi?query=beadm&sektion=&man... NeXt->Apple also avoided anything like systemd via a configuration system that supported inheritance across search domains (User, Local, Network, System): https://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Miscellaneous/Foundation_Constants/index.html#//apple_ref/doc/c_ref/NSSearchPathDomainMask https://developer.apple.com/library/mac/documentation/Cocoa/...
- mjg59 10y agoOh, there's certainly multiple ways to do this. My point is purely that this isn't an inherent Linux/*BSD thing - there are modern Linux distributions that have precisely this property.
- frabbit 10y agoAnd isn't it actually part of the same effort (RH Stateless Linux) which spawned systemd and ostree ?
- snuxoll 10y agoThis is something I actually like about systemd and firewalld, everything in /usr/lib/systemd/ and /usr/lib/firewalld should only be handled by your package manager, anything you customize yourself belongs in /etc/systemd/ and /etc/firewalld, and they will override the corresponding entries in the 'global' folders if you give them the same filename.