News for hackers. Stuff that matters.
Re:rc.d belongs in libexec, not etc by altmind on Tuesday August 25, 2020 @03:14AM (#24268832)
and /etc/resolv.conf dont belong anywhere as it is runtime settings
Re:rc.d belongs in libexec, not etc by rndgermandude on Tuesday August 25, 2020 @05:16AM (#24269466)
My resolv.confs tend to be written once and then go untouched for months if not years.

The problem there is that distributions, be it linux or bsd, lack a proper way to distinguish between a "static" resolv.conf and a (always-)generated one.

An "easy" fix would be to mandate that if /etc/resolv.conf contains a "dynamic" key then /run/resolve.conf (or /var/run/resolv.conf or whatver) is read as well (or instead).

However, tons of stuff tries to parse resolv.conf, so it would be better to have a user-editable /etc/resolv.conf.conf and a /run/dynamic-resolve.conf and dump the result or into /etc/resolv.conf to keep compatible.

Re:rc.d belongs in libexec, not etc by progval on Tuesday August 25, 2020 @03:29AM (#24268907)
What about /run or /proc?
Re:rc.d belongs in libexec, not etc by nuxi on Tuesday August 25, 2020 @05:00AM (#24269409)
There is no /run by default on FreeBSD (only /var/run), and /proc (procfs) is being phased out since 2011.