On Thu, Jun 7, 2018, at 12:47 PM, Peter Wemm wrote: > On 6/6/18 4:06 PM, Ian Lepore wrote: > > > On Wed, 2018-06-06 at 11:33 -0700, Rodney W. Grimes wrote: > >>> > >>> On Tue, Jun 5, 2018, at 1:28 PM, Konstantin Belousov wrote: > >>>> On Wed, Jun 06, 2018 at 01:39:00AM +0700, Eugene Grosbein wrote: > >>>>> 06.06.2018 1:26, Konstantin Belousov wrote: > >>>>> > >>>>>>>> I find it often very useful to do > >>>>>>>> (cd src/etc/rc.d && make install) > >>>>>>>> Same for defaults and several other directories which in > >>>>>>>> fact > >>>>>>>> contains> > >>> non-editable content. Is this planned to > >>>>>>>> keep working ? > >>>>>>> The short answer is, no. All rc.d scripts get moved to the > >>>>>>> src > >>>>>>> of the program they start.> > >> > >>>>>>> That said, if there is a big need for this, we can see > >>>>>>> about > >>>>>>> options to keep them working.> > >> > >>>>>>> What are you trying to accomplish when you do this? Just > >>>>>>> verify > >>>>>>> the rc.d scripts match your src tree?> > > > >>>>>> I avoid mergemaster/etcupdate and whatever else. rc.d and > >>>>>> /etc/rc,> > > /etc/rc.subr /etc/rc.network are not suitable > >>>>>> to etc, they are > >>>>>> binaries> > > provided by the project not for the user > >>>>>> editing. > >>>>>> > >>>>>> When upgrading the host, esp. on HEAD, i usually refresh > >>>>>> scripts > >>>>>> by this> > > procedure and avoid any editing and implied > >>>>>> conflict resolution > >>>>>> for real> > > configs. > >>>>>> > >>>>>> Not being able to easily install clean copies of these > >>>>>> scripts > >>>>>> would> > > be very inconvenient and time consuming. > >>>>> I found that "mergemaster -iFUP" deals with unchanged files > >>>>> including mentioned rc* scripts just fine.> > That is, it > >>>>> automatically refreshes unchanged files without any > >>>>> silly questions just for change of $FreeBSD$.> > >>>> No, you missed the point. Whatever nice is the handling of > >>>> unchanged files,> use of mergemaster forces me to handle changed > >>>> files, which is exactly> what I do not want/need to do. Yes, I > >>>> update crashboxes very > >>>> often, and> I want to get all new code, including the startup > >>>> scripts, when > >>>> I update. > >>> The startup scripts will be installed as part of installworld. > >> So each installworld would wipe over the top of any localmod > >> /etc/rc.d/ and other stuff > >> that mght exist? > >> One of the reasons that etc/Makefile is detached from Installword is > >> so that > >> /etc does not get perturbuted unless specifically requested. > >> > > I don't understand the drama over this. rc.d startup scripts are > > *binaries*. Users are not expected to modify the system installed > > binaries, and if they do, it is expected that the next installworld > > will replace them with the system binaries again. > > > This is not the case. Example: /etc/rc.d/serial > > Other random examples of things installed by etc/Makefile that are > expected to be merged rather than spammed as part of an installworld: > etc/ttys > etc/inetd.conf > etc/dhclient.conf > etc/login.conf > etc/sysctl.conf
Yes, this discussion is purely about rc stuff. Regards, Brad Davis _______________________________________________ svn-src-head@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-head To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
