Return of config files to ^/etc

[John Baldwin]

On 2/19/20 7:14 AM, Will Andrews wrote:
> The new locations are actually less "arbitrary" (to use your word) than
> ^/etc, since the config files are co-located with the code that reads
> them.  This is nice for source management: there's no need to look in or
> manage other directories for related files like the default configuration.
> It is a *source* tree, after all.
> 
> Here's a question: why are config files special?  Why don't we store all
> man pages in ^/share/man/manX, instead of colocating them with their source
> files?

Yes, why are (some) config files special?  Why is rc.d still intact but
just moved to a more obscure location (libexec/rc).  Why is pam.d still
intact and not split up?  Why is stdio.h in include/?

Both the old and new arrangements are arbitrary, so why gratuitously break
existing muscle memory and setups (we've already moved the libc ones back to
etc/ in head due to breaking other tools)?

-- 
John Baldwin