Re: Moving /etc/rc.conf.local to /usr/local/etc/rc.conf
- In reply to: John R. Levine: "Re: Moving /etc/rc.conf.local to /usr/local/etc/rc.conf"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 27 Jan 2024 22:36:33 UTC
> On Jan 27, 2024, at 5:31 PM, John R. Levine <johnl@iecc.com> wrote: > >> I know you can customize the rc_conf_files variable to hold a value with my files of choice, but that in itself implies customizing /etc/rc.conf to override rc_conf_files’ default value, which defeats the purpose of keeping all customizations to /usr/local/etc. > > I didn't write this stuff, I just use it. I wasn’t saying you did ;) Was just asking if you knew if there was any rationale behind the choice of supporting /etc/rc.conf.local out-of-the-box, but not /usr/local/etc/rc.conf. If there is such a rationale, then an upstream contribution to support the latter would probably not make sense. Otherwise, I’d be more than happy to send a merge request. > > The rc.conf stuff is just shell scripts so you can look at each script to see what it does. > > You will probably find there's no way around putting config stuff in /etc/rc.conf. Whenever I spin up a FreeBSD VPS, there's always a custom rc.conf with the hostname, IP address, and so forth. Sure thing, absolutely, but my point is keeping that to a minimum, and moving as much stuff as possible to /usr/local/etc. I can already do that via individual /usr/local/etc/rc.conf.d/$name configuration files, as I said before, but supporting a single /usr/local/etc/rc.conf file out-of-the-box would also be a pretty interesting option, in my opinion. > > Regards, > John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", > Please consider the environment before reading this e-mail. https://jl.ly Regards,