Date: Fri, 21 Jun 2019 14:39:34 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: Xin LI <delphij@gmail.com> Cc: Conrad Meyer <cem@freebsd.org>, "src-committers@freebsd.org" <src-committers@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org> Subject: Re: svn commit: r349256 - head/libexec/rc/rc.d Message-ID: <tkrat.0a317df2dfe56424@FreeBSD.org> In-Reply-To: <CAGMYy3shArmDCEkwA_QH3Yf7FFciuJ%2Bpvd%2BX10s_Jn%2BSmziVvQ@mail.gmail.com> References: <201906210237.x5L2bt8I012721@repo.freebsd.org> <CAGMYy3shArmDCEkwA_QH3Yf7FFciuJ%2Bpvd%2BX10s_Jn%2BSmziVvQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 Jun, Xin LI wrote: > But ultimately, I think the real design question here that needs to be > solved would probably be "Why are piling up multiple layers of workarounds > around motd? Does it even need to be located in /etc?" The contents is > meant to be updated every time when there is a kernel change, and to that > extent it seems to be more appropriate for /var/run and generated at boot > from a template located somewhere in /etc. The benefit of this approach is > that you would have one less file to merge for each etcupdate/mergemaster > (or at least only need to do it when some customization is made), and there > is no need to worry about write durability. +1 This is something that has bothered me for a long time. It should be possible to run with a read-only /etc (obviously with some functional limitations).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?tkrat.0a317df2dfe56424>