News for hackers. Stuff that matters.
Re:BSD vs. Linux (2005) by mjg59 on Tuesday July 05, 2016 @01:41AM (#12034588)
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.
Re:BSD vs. Linux (2005) by teacup50 on Tuesday July 05, 2016 @01:53AM (#12034625)
If 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=&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/...

Re:BSD vs. Linux (2005) by mjg59 on Tuesday July 05, 2016 @02:14AM (#12034692)
Oh, 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.
Re:BSD vs. Linux (2005) by frabbit on Tuesday July 05, 2016 @02:20PM (#12038397)
And isn't it actually part of the same effort (RH Stateless Linux) which spawned systemd and ostree ?
Re:BSD vs. Linux (2005) by snuxoll on Tuesday July 05, 2016 @03:20AM (#12034876)
This 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.