Re: svn commit: r334617 - in head: . etc
On Thu, Jun 7, 2018, at 10:59 PM, Bryan Drewery wrote: > > > On Jun 4, 2018, at 11:17, Brad Davis wrote: > > > > Author: brd > > Date: Mon Jun 4 15:17:24 2018 > > New Revision: 334617 > > URL: https://svnweb.freebsd.org/changeset/base/334617 > > > > Log: > > Move /sys symlink creating out of etc/Makefile. > > > > This is prep for etc/Makefile going away. > > > > Approved by:bapt (mentor) > > > > Modified: > > head/Makefile.inc1 > > head/etc/Makefile > > > > Aside from other objections, I don’t think /Makefile nor > /Makefile.inc1> should “own” anything on the system and should only drive the > build or> other general targets for users to interact with. Please put this > into> something like /hier or better yet the existing directory > handling that> stuff /etc. (so a revert since simply moving everything to it > via a > rename or rewrite seems silly) I agree, I started creating a hier/ last night. Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Thu, Jun 7, 2018, at 10:38 PM, Bryan Drewery wrote: > > > > On Jun 5, 2018, at 16:43, Brad Davis wrote: > > > > > > On Tue, Jun 5, 2018, at 1:07 PM, Renato Botelho wrote: > > > On 05/06/18 15:26, Konstantin Belousov wrote: > > > > On Tue, Jun 05, 2018 at 12:13:05PM -0600, Brad Davis wrote: > > > >> On Tue, Jun 5, 2018, at 10:46 AM, 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. > > > > > > If I understood what Brad is saying, each rc.d script will be > > > installed> > > by the application it belongs to. So when it's installing > > > SSH it > > > will> > > also install /etc/rc.d/sshd and you will not need to deal with > > > rc.d> > > files on mergemaster anymore. > > > > > > Is it correct, Brad? > > > > Correct. > > > > This makes no sense. Many rc scripts, and other config files, have no> > “owner” outside of etc/... > > Please don’t kill etc/Makefile. This is going to be very > painful to deal> with downstream. I was wrong. We moved startup scripts under sbin/init. So this would be easy to merge. Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
> On Jun 7, 2018, at 03:29, Alexey Dokuchaev wrote: > >> On Wed, Jun 06, 2018 at 01:02:25PM -0600, Brad Davis wrote: >>> On Wed, Jun 6, 2018, at 12:33 PM, Rodney W. Grimes wrote: >>> ... >>> 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. >> >> Yes, this is by design. >> >> If people need custom tweaks for that stuff they should be upstreamed or >> moved into /usr/local/etc/rc.d as a custom startup script. > > This is rather questionable design to me. I don't consider my scripts > as binaries and like them in /etc/rc.d/ and managed via mergemaster -Fi. > Everything was perfectly fine with it. What exactly the problem you're > trying to solve here? For me the biggest selling point of FreeBSD has always been how configurable and customizable it has been (without modifying src). Especially the rc files and patterns of .local in /etc. > > ./danfe > ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
> On Jun 4, 2018, at 11:17, Brad Davis wrote:
>
> Author: brd
> Date: Mon Jun 4 15:17:24 2018
> New Revision: 334617
> URL: https://svnweb.freebsd.org/changeset/base/334617
>
> Log:
> Move /sys symlink creating out of etc/Makefile.
>
> This is prep for etc/Makefile going away.
>
> Approved by:bapt (mentor)
>
> Modified:
> head/Makefile.inc1
> head/etc/Makefile
>
Aside from other objections, I don’t think /Makefile nor /Makefile.inc1 should
“own” anything on the system and should only drive the build or other general
targets for users to interact with. Please put this into something like /hier
or better yet the existing directory handling that stuff /etc. (so a revert
since simply moving everything to it via a rename or rewrite seems silly)
> Modified: head/Makefile.inc1
> ==
> --- head/Makefile.inc1Mon Jun 4 14:56:02 2018(r334616)
> +++ head/Makefile.inc1Mon Jun 4 15:17:24 2018(r334617)
> @@ -1239,6 +1239,7 @@ distributeworld installworld stageworld: _installcheck
>METALOG=${METALOG} ${IMAKE_INSTALL} ${IMAKE_MTREE} \
>DISTBASE=/base DESTDIR=${DESTDIR}/${DISTDIR}/base \
>LOCAL_MTREE=${LOCAL_MTREE:Q} distrib-dirs
> +${INSTALL_SYMLINK} usr/src/sys ${DESTDIR}/sys
> .endif
>${_+_}cd ${.CURDIR}; ${IMAKE} re${.TARGET:S/world$//}; \
>${IMAKEENV} rm -rf ${INSTALLTMP}
>
> Modified: head/etc/Makefile
> ==
> --- head/etc/MakefileMon Jun 4 14:56:02 2018(r334616)
> +++ head/etc/MakefileMon Jun 4 15:17:24 2018(r334617)
> @@ -386,7 +386,6 @@ distrib-dirs: ${MTREES:N/*} distrib-cleanup .PHONY
>${METALOG.add} ; \
>done; true
> .endif
> -${INSTALL_SYMLINK} usr/src/sys ${DESTDIR}/sys
> .if ${MK_NLS} != "no"
>set - `grep "^[a-zA-Z]" ${.CURDIR}/nls.alias`; \
>while [ $$# -gt 0 ] ; do \
>
___
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
> On Jun 6, 2018, at 16:35, Rodney W. Grimes > wrote: > > >> On Wed, Jun 6, 2018, at 12:33 PM, 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. >> >> Yes, this is by design. > > This is going to have a great amount of push back, and this is by your NEW > design, > the existing design does not cause this pain. > This is my position as well. Some people may not like or agree that rc scripts are user modifiable but they are and have been “forever”. The fact that tools like mergemaster have handled merging of them, “forever”, makes this a huge POLA violation to suddenly be replacing them. I don’t see any benefits at all except to pissoff users. Some of these planned changes for etc feel over zealous and under thought out or discussed. Whatever people think about these topics we must consider POLA and not regressing people’s workflows for no benefit other than draconian ideals about what a user is allowed to modify. >> >> If people need custom tweaks for that stuff they should be upstreamed or >> moved into /usr/local/etc/rc.d as a custom startup script. > > I doubt very much this is a practical solution. I have changes that I doubt > belong in FreeBSD, and are not restricted to etc/rc.d. And from reading > this thread thus far so do others. > > > -- > Rod Grimes rgri...@freebsd.org > ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
> On Jun 5, 2018, at 16:43, Brad Davis wrote: > > > On Tue, Jun 5, 2018, at 1:07 PM, Renato Botelho wrote: > > On 05/06/18 15:26, Konstantin Belousov wrote: > > > On Tue, Jun 05, 2018 at 12:13:05PM -0600, Brad Davis wrote: > > >> On Tue, Jun 5, 2018, at 10:46 AM, 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. > > > > If I understood what Brad is saying, each rc.d script will be installed > > by the application it belongs to. So when it's installing SSH it will > > also install /etc/rc.d/sshd and you will not need to deal with rc.d > > files on mergemaster anymore. > > > > Is it correct, Brad? > > Correct. > This makes no sense. Many rc scripts, and other config files, have no “owner” outside of etc/... Please don’t kill etc/Makefile. This is going to be very painful to deal with downstream. > > Regards, > Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
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 -Peter ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
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-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Fri, Jun 08, 2018 at 01:39:21AM +0700, Eugene Grosbein wrote: > 07.06.2018 22:35, Brooks Davis wrote: > > You see, my point is that you can never know beforehand of all > challenges a sysadmin faces in fields. > And there should be really good reason to break things that work before. > Like, solving some significant issue we have with current setup. Do we > have such? > >>> > >>> This is not affected by my changes, you can install *additional* things > >>> in /etc/rc.d and they won't be touched just as today. > >> > >> Do we have any convention on naming such custom additional scripts > >> installed in /etc/rc.d > >> locally so that installworld would never overwrite them silently? > > > > script-domain.tld is almost certainly safe. > > That is, "script.local" should always be fine? That's fine. In practice anything with a '.' is going to be safe because such scripts can't have name= which is our internal convention. -- Brooks signature.asc Description: PGP signature
Re: svn commit: r334617 - in head: . etc
On Thu, Jun 07, 2018 at 10:17:44PM +0700, Eugene Grosbein wrote: > 07.06.2018 22:00, Brad Davis wrote: > > >> You see, my point is that you can never know beforehand of all > >> challenges a sysadmin faces in fields. > >> And there should be really good reason to break things that work before. > >> Like, solving some significant issue we have with current setup. Do we > >> have such? > > > > This is not affected by my changes, you can install *additional* things in > > /etc/rc.d and they won't be touched just as today. > > Do we have any convention on naming such custom additional scripts installed > in /etc/rc.d > locally so that installworld would never overwrite them silently? script-domain.tld is almost certainly safe. -- Brooks signature.asc Description: PGP signature
Re: svn commit: r334617 - in head: . etc
07.06.2018 22:35, Brooks Davis wrote: You see, my point is that you can never know beforehand of all challenges a sysadmin faces in fields. And there should be really good reason to break things that work before. Like, solving some significant issue we have with current setup. Do we have such? >>> >>> This is not affected by my changes, you can install *additional* things in >>> /etc/rc.d and they won't be touched just as today. >> >> Do we have any convention on naming such custom additional scripts installed >> in /etc/rc.d >> locally so that installworld would never overwrite them silently? > > script-domain.tld is almost certainly safe. That is, "script.local" should always be fine? That's fine. ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Thu, 7 Jun 2018 07:33:29 + Alexey Dokuchaev wrote: > On Wed, Jun 06, 2018 at 11:27:20PM +0300, Konstantin Belousov wrote: > > On Wed, Jun 06, 2018 at 02:06:48PM -0600, Ian Lepore wrote: > > > ... > > > I don't understand the drama over this. rc.d startup scripts are > > > *binaries*. > > No, they are not, they are scripts. > > > I proposed to move them somewhere, e.g. to /sbin/rc* or to /libexec/rc*. > > Please don't. Our huge selling point (vs. most GNU/Linux distros) is that > everything is *not* spread across the entire hier(7) like butter on bread. > > ./danfe Our huge selling point is startup scripts in /etc/rc.d ? Damn, we sucks at marketing ... -- Emmanuel Vadot ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
07.06.2018 22:00, Brad Davis wrote: >> You see, my point is that you can never know beforehand of all >> challenges a sysadmin faces in fields. >> And there should be really good reason to break things that work before. >> Like, solving some significant issue we have with current setup. Do we >> have such? > > This is not affected by my changes, you can install *additional* things in > /etc/rc.d and they won't be touched just as today. Do we have any convention on naming such custom additional scripts installed in /etc/rc.d locally so that installworld would never overwrite them silently? Addition of custom code to /etc/rc.d/serial guarantees that currently it won't and mergemaster deals with possible conflicts. ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Thu, Jun 7, 2018, at 8:46 AM, Eugene Grosbein wrote: > 07.06.2018 20:17, Brad Davis wrote: > > >>> I don't understand the drama over this. rc.d startup scripts are > >>> *binaries*. > >> > >> This is plain wrong. Example: before introduction of rcNG we had /etc/ > >> rc.serial > >> supposed to be user-modified to contain local settings for serial ports > >> (uncluding USB serial). > >> Now it is moved to /etc/rc.d/serial largely unchanged and is still > >> supposed to be user-modified. > > > > We can change this script to advise the user to copy it to > > /usr/local/etc/rc.d. > > Yes, we could. However, /usr/local/etc/rc.d has its limitations > comparing to /etc/rc.d: > it is not possible to run a script from /usr/local/etc/rc.d before > FILESYSTEMS > early/late divider that is critical if one needs to query local UPS over > serial port > to ensure its battery has enough energy (say, above 5%) to delay fs > mounts until it charges enough. > For example, statically linked "apctest" utility placed to /root/bin/ > does that just fine > with some small scripting. > > You see, my point is that you can never know beforehand of all > challenges a sysadmin faces in fields. > And there should be really good reason to break things that work before. > Like, solving some significant issue we have with current setup. Do we > have such? This is not affected by my changes, you can install *additional* things in /etc/rc.d and they won't be touched just as today. We can also make the rc subsystem more flexible to handle more things.. Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
07.06.2018 20:17, Brad Davis wrote: >>> I don't understand the drama over this. rc.d startup scripts are >>> *binaries*. >> >> This is plain wrong. Example: before introduction of rcNG we had /etc/ >> rc.serial >> supposed to be user-modified to contain local settings for serial ports >> (uncluding USB serial). >> Now it is moved to /etc/rc.d/serial largely unchanged and is still >> supposed to be user-modified. > > We can change this script to advise the user to copy it to > /usr/local/etc/rc.d. Yes, we could. However, /usr/local/etc/rc.d has its limitations comparing to /etc/rc.d: it is not possible to run a script from /usr/local/etc/rc.d before FILESYSTEMS early/late divider that is critical if one needs to query local UPS over serial port to ensure its battery has enough energy (say, above 5%) to delay fs mounts until it charges enough. For example, statically linked "apctest" utility placed to /root/bin/ does that just fine with some small scripting. You see, my point is that you can never know beforehand of all challenges a sysadmin faces in fields. And there should be really good reason to break things that work before. Like, solving some significant issue we have with current setup. Do we have such? Eugene ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Thu, Jun 7, 2018, at 1:29 AM, Alexey Dokuchaev wrote: > On Wed, Jun 06, 2018 at 01:02:25PM -0600, Brad Davis wrote: > > On Wed, Jun 6, 2018, at 12:33 PM, Rodney W. Grimes wrote: > > > ... > > > 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. > > > > Yes, this is by design. > > > > If people need custom tweaks for that stuff they should be upstreamed or > > moved into /usr/local/etc/rc.d as a custom startup script. > > This is rather questionable design to me. I don't consider my scripts > as binaries and like them in /etc/rc.d/ and managed via mergemaster -Fi. > Everything was perfectly fine with it. What exactly the problem you're > trying to solve here? But they are provided by the system and should not be modified in place. Hence the suggestion to move them out of /etc. Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Wed, Jun 6, 2018, at 6:20 PM, Eugene Grosbein wrote: > 07.06.2018 3:06, Ian Lepore wrote: > > > I don't understand the drama over this. rc.d startup scripts are > > *binaries*. > > This is plain wrong. Example: before introduction of rcNG we had /etc/ > rc.serial > supposed to be user-modified to contain local settings for serial ports > (uncluding USB serial). > Now it is moved to /etc/rc.d/serial largely unchanged and is still > supposed to be user-modified. We can change this script to advise the user to copy it to /usr/local/etc/rc.d. Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Wed, Jun 6, 2018, at 2:35 PM, Rodney W. Grimes wrote: > > > On Wed, Jun 6, 2018, at 12:33 PM, 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. > > > > Yes, this is by design. > > This is going to have a great amount of push back, and this is by your > NEW design, > the existing design does not cause this pain. > > > > > If people need custom tweaks for that stuff they should be upstreamed or > > moved into /usr/local/etc/rc.d as a custom startup script. > > I doubt very much this is a practical solution. I have changes that I doubt > belong in FreeBSD, and are not restricted to etc/rc.d. And from reading > this thread thus far so do others. I think we could extend the rc system to handle cases like this, but without details we cannot have a productive conversation. Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
[ CC list trimmed, was too long ] On Thu, Jun 07, 2018 at 01:16:01PM +0200, Emmanuel Vadot wrote: > On Thu, 7 Jun 2018 07:33:29 + > Alexey Dokuchaev wrote: > > On Wed, Jun 06, 2018 at 11:27:20PM +0300, Konstantin Belousov wrote: > > > I proposed to move them somewhere, e.g. to /sbin/rc* or to /libexec/rc*. > > > > Please don't. Our huge selling point (vs. most GNU/Linux distros) is > > that everything is *not* spread across the entire hier(7) like butter > > on bread. > > Our huge selling point is startup scripts in /etc/rc.d ? Damn, we suck > at marketing ... Please don't twist my words. I was talking about coherent, nicely put together configuration mechanisms and /etc layout in particular. This is contrast with GNU/Linux, where I typically have to traverse through gazillion of compatibility symlinks before stumbling upon 30-byte shim saying "implemented in systemd now". ./danfe ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Wed, Jun 06, 2018 at 11:27:20PM +0300, Konstantin Belousov wrote: > On Wed, Jun 06, 2018 at 02:06:48PM -0600, Ian Lepore wrote: > > ... > > I don't understand the drama over this. rc.d startup scripts are > > *binaries*. No, they are not, they are scripts. > I proposed to move them somewhere, e.g. to /sbin/rc* or to /libexec/rc*. Please don't. Our huge selling point (vs. most GNU/Linux distros) is that everything is *not* spread across the entire hier(7) like butter on bread. ./danfe ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Wed, Jun 06, 2018 at 11:27:20PM +0300, Konstantin Belousov wrote: > On Wed, Jun 06, 2018 at 02:06:48PM -0600, 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. > > I agree with this, but the scripts are installed into /etc. > > I proposed to move them somewhere, e.g. to /sbin/rc* or to /libexec/rc*. > If moved first, then the proposed change would be much more logical and > probably easier to fit into the workflows of FreeBSD consumers. IMHO would be a good idea! Bapt signature.asc Description: PGP signature
Re: svn commit: r334617 - in head: . etc
On Wed, Jun 06, 2018 at 01:02:25PM -0600, Brad Davis wrote: > On Wed, Jun 6, 2018, at 12:33 PM, Rodney W. Grimes wrote: > > ... > > 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. > > Yes, this is by design. > > If people need custom tweaks for that stuff they should be upstreamed or > moved into /usr/local/etc/rc.d as a custom startup script. This is rather questionable design to me. I don't consider my scripts as binaries and like them in /etc/rc.d/ and managed via mergemaster -Fi. Everything was perfectly fine with it. What exactly the problem you're trying to solve here? ./danfe ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
07.06.2018 7:27, Ian Lepore wrote: >>> I don't understand the drama over this. rc.d startup scripts are >>> *binaries*. >> This is plain wrong. Example: before introduction of rcNG we had >> /etc/rc.serial >> supposed to be user-modified to contain local settings for serial >> ports (uncluding USB serial). >> Now it is moved to /etc/rc.d/serial largely unchanged and is still >> supposed to be user-modified. >> > > You're holding up mostly-obsolete badly-written script as the example > of why nothing can ever change? I have not said nothing can ever change :-) Just that scripts are not binaries at all. And discussed move will break things without working alternative proposal. ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Thu, 2018-06-07 at 07:20 +0700, Eugene Grosbein wrote: > 07.06.2018 3:06, Ian Lepore wrote: > > > > > I don't understand the drama over this. rc.d startup scripts are > > *binaries*. > This is plain wrong. Example: before introduction of rcNG we had > /etc/rc.serial > supposed to be user-modified to contain local settings for serial > ports (uncluding USB serial). > Now it is moved to /etc/rc.d/serial largely unchanged and is still > supposed to be user-modified. > You're holding up mostly-obsolete badly-written script as the example of why nothing can ever change? -- Ian ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
07.06.2018 3:06, Ian Lepore wrote: > I don't understand the drama over this. rc.d startup scripts are > *binaries*. This is plain wrong. Example: before introduction of rcNG we had /etc/rc.serial supposed to be user-modified to contain local settings for serial ports (uncluding USB serial). Now it is moved to /etc/rc.d/serial largely unchanged and is still supposed to be user-modified. ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
> On Wed, Jun 6, 2018, at 12:33 PM, 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. > > Yes, this is by design. This is going to have a great amount of push back, and this is by your NEW design, the existing design does not cause this pain. > > If people need custom tweaks for that stuff they should be upstreamed or > moved into /usr/local/etc/rc.d as a custom startup script. I doubt very much this is a practical solution. I have changes that I doubt belong in FreeBSD, and are not restricted to etc/rc.d. And from reading this thread thus far so do others. -- Rod Grimes rgri...@freebsd.org ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Wed, Jun 06, 2018 at 02:06:48PM -0600, 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. I agree with this, but the scripts are installed into /etc. I proposed to move them somewhere, e.g. to /sbin/rc* or to /libexec/rc*. If moved first, then the proposed change would be much more logical and probably easier to fit into the workflows of FreeBSD consumers. ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
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. -- Ian ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
In message <1528231489.2440725.1397620864.5987B9ED@webmail.messagingengi ne.com> , Brad Davis writes: > This is a multi-part message in MIME format. > > --_--=_152823148924407253 > Content-Transfer-Encoding: 7bit > Content-Type: text/plain; charset="utf-8" > > > 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 workin > g ? > > > >> > > > >> 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 resol > ution > > > > 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 r > efreshes 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, whi > ch 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. Shouldn't this be worked out in a phab review first? -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Wed, Jun 6, 2018, at 12:33 PM, 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. Yes, this is by design. If people need custom tweaks for that stuff they should be upstreamed or moved into /usr/local/etc/rc.d as a custom startup script. Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
> > 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. -- Rod Grimes rgri...@freebsd.org ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Wed, Jun 6, 2018, at 2:25 AM, Stefan Esser wrote: > Am 05.06.18 um 22:43 schrieb Brad Davis: > > > > On Tue, Jun 5, 2018, at 1:07 PM, Renato Botelho wrote: > >> On 05/06/18 15:26, Konstantin Belousov wrote: > >> > On Tue, Jun 05, 2018 at 12:13:05PM -0600, Brad Davis wrote: > >> >> On Tue, Jun 5, 2018, at 10:46 AM, 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. > >> > >> If I understood what Brad is saying, each rc.d script will be installed > >> by the application it belongs to. So when it's installing SSH it will > >> also install /etc/rc.d/sshd and you will not need to deal with rc.d > >> files on mergemaster anymore. > >> > >> Is it correct, Brad? > > > > Correct. > I have for a long time (decades?) applied local changes to files in src/etc > which (very seldom) may need a conflict resolution, and which make sure that > /etc is populated with files that match my needs. > > It is easy to change a file in /etc until it works as desired and then copy > it to src/etc, where it is subject to updating via SVN, but still reflects > my preferences. > > With the move to source directories it will be necessary to modify rc files > and other configuration file defaults (e.g. ttys) in a number of places. > > E.g., mergemaster will try to remove the shells installed from ports from > /etc/shells on each run and quite a number of other files will either never > be automatically updated (by excluding them from mergemaster runs) or on > every invocation of mergemaster, unless patched in their respective source > directories spread over the whole source tree. > > This is a BIG step backwards from my PoV, since src/etc currently is the > equivalent of FreeBSD's concept of using /etc/rc.conf for configuration of > all applicable system settings. Having sources of all files that are going > to be installed in /etc (when a new system is setup or by mergemaster) is > equivalent in the sense that the location where changes have to be applied > is confined to just one directory, src/etc (and a few architecture dependent > sub-directories). You should really consider moving to etcupdate, as it uses 3-way merge and make this much easier. Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
Am 05.06.18 um 22:43 schrieb Brad Davis: > > On Tue, Jun 5, 2018, at 1:07 PM, Renato Botelho wrote: >> On 05/06/18 15:26, Konstantin Belousov wrote: >> > On Tue, Jun 05, 2018 at 12:13:05PM -0600, Brad Davis wrote: >> >> On Tue, Jun 5, 2018, at 10:46 AM, 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. >> >> If I understood what Brad is saying, each rc.d script will be installed >> by the application it belongs to. So when it's installing SSH it will >> also install /etc/rc.d/sshd and you will not need to deal with rc.d >> files on mergemaster anymore. >> >> Is it correct, Brad? > > Correct. I have for a long time (decades?) applied local changes to files in src/etc which (very seldom) may need a conflict resolution, and which make sure that /etc is populated with files that match my needs. It is easy to change a file in /etc until it works as desired and then copy it to src/etc, where it is subject to updating via SVN, but still reflects my preferences. With the move to source directories it will be necessary to modify rc files and other configuration file defaults (e.g. ttys) in a number of places. E.g., mergemaster will try to remove the shells installed from ports from /etc/shells on each run and quite a number of other files will either never be automatically updated (by excluding them from mergemaster runs) or on every invocation of mergemaster, unless patched in their respective source directories spread over the whole source tree. This is a BIG step backwards from my PoV, since src/etc currently is the equivalent of FreeBSD's concept of using /etc/rc.conf for configuration of all applicable system settings. Having sources of all files that are going to be installed in /etc (when a new system is setup or by mergemaster) is equivalent in the sense that the location where changes have to be applied is confined to just one directory, src/etc (and a few architecture dependent sub-directories). Regards, STefan ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
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. Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Tue, Jun 5, 2018, at 1:07 PM, Renato Botelho wrote: > On 05/06/18 15:26, Konstantin Belousov wrote: > > On Tue, Jun 05, 2018 at 12:13:05PM -0600, Brad Davis wrote: > >> On Tue, Jun 5, 2018, at 10:46 AM, 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. > > If I understood what Brad is saying, each rc.d script will be > installed> by the application it belongs to. So when it's installing SSH it > will> also install /etc/rc.d/sshd and you will not need to deal with rc.d > files on mergemaster anymore. > > Is it correct, Brad? Correct. Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
06.06.2018 2:28, Konstantin Belousov wrote: >> 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. "Changed" means "local copy changed by hands", not "changed in the repository". "mergemaster -iFUP" installs all new changes from the repo without questions for files untouched locally since last invocation of such mergemaster, so you get what you want :-) ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
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. ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On 05/06/18 15:26, Konstantin Belousov wrote: > On Tue, Jun 05, 2018 at 12:13:05PM -0600, Brad Davis wrote: >> On Tue, Jun 5, 2018, at 10:46 AM, 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. If I understood what Brad is saying, each rc.d script will be installed by the application it belongs to. So when it's installing SSH it will also install /etc/rc.d/sshd and you will not need to deal with rc.d files on mergemaster anymore. Is it correct, Brad? -- Renato Botelho ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
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$. ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Tue, Jun 05, 2018 at 12:13:05PM -0600, Brad Davis wrote: > On Tue, Jun 5, 2018, at 10:46 AM, 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. ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Tue, Jun 5, 2018, at 10:46 AM, Konstantin Belousov wrote: > On Tue, Jun 05, 2018 at 09:24:02AM -0600, Brad Davis wrote: > > On Tue, Jun 5, 2018, at 7:00 AM, Alexander Leidinger wrote: > > > > > > Quoting Brad Davis (from Mon, 04 Jun 2018 12:55:50 > > > -0600): > > > > > > > On Mon, Jun 4, 2018, at 12:47 PM, Rodney W. Grimes wrote: > > > >> [ Charset UTF-8 unsupported, converting... ] > > > >> > On Mon, Jun 4, 2018, at 10:57 AM, Rodney W. Grimes wrote: > > > >> > > > On Mon, Jun 4, 2018, at 9:29 AM, Rodney W. Grimes wrote: > > > > > > >> > > > > I believe there are also other external consumers of this. > > > >> > > > > > > >> > > > Such as? > > > >> > > > > > >> > > Iirc some of the make release stuff calls into here, but that > > > >> > > may of changed to use src/Makefile targets. distrib-dirs comes > > > >> > > to mind. > > > >> > > > > >> > Sure, but those can go away or be updated as needed.. > > > >> > > > >> So again, no plan yet? > > > > > > > > Most of them are gone, I am still in progress on some of it. See > > > > the github branch above. > > > > > > > > My testing is all done by building release VMs and comparing them > > > > against a VM built from the last merge from HEAD. So I will update > > > > the release stuff as I go. It is my responsibility to keep the > > > > release stuff working as I change these. > > > > > > Have you checked mergemaster? IIRC it uses the distribution target. > > > > Yup, this does not affect the distribution target. > > 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? Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Tue, Jun 05, 2018 at 09:24:02AM -0600, Brad Davis wrote: > On Tue, Jun 5, 2018, at 7:00 AM, Alexander Leidinger wrote: > > > > Quoting Brad Davis (from Mon, 04 Jun 2018 12:55:50 > > -0600): > > > > > On Mon, Jun 4, 2018, at 12:47 PM, Rodney W. Grimes wrote: > > >> [ Charset UTF-8 unsupported, converting... ] > > >> > On Mon, Jun 4, 2018, at 10:57 AM, Rodney W. Grimes wrote: > > >> > > > On Mon, Jun 4, 2018, at 9:29 AM, Rodney W. Grimes wrote: > > > > >> > > > > I believe there are also other external consumers of this. > > >> > > > > > >> > > > Such as? > > >> > > > > >> > > Iirc some of the make release stuff calls into here, but that > > >> > > may of changed to use src/Makefile targets. distrib-dirs comes > > >> > > to mind. > > >> > > > >> > Sure, but those can go away or be updated as needed.. > > >> > > >> So again, no plan yet? > > > > > > Most of them are gone, I am still in progress on some of it. See > > > the github branch above. > > > > > > My testing is all done by building release VMs and comparing them > > > against a VM built from the last merge from HEAD. So I will update > > > the release stuff as I go. It is my responsibility to keep the > > > release stuff working as I change these. > > > > Have you checked mergemaster? IIRC it uses the distribution target. > > Yup, this does not affect the distribution target. 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 ? ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Tue, Jun 5, 2018, at 7:00 AM, Alexander Leidinger wrote: > > Quoting Brad Davis (from Mon, 04 Jun 2018 12:55:50 -0600): > > > On Mon, Jun 4, 2018, at 12:47 PM, Rodney W. Grimes wrote: > >> [ Charset UTF-8 unsupported, converting... ] > >> > On Mon, Jun 4, 2018, at 10:57 AM, Rodney W. Grimes wrote: > >> > > > On Mon, Jun 4, 2018, at 9:29 AM, Rodney W. Grimes wrote: > > >> > > > > I believe there are also other external consumers of this. > >> > > > > >> > > > Such as? > >> > > > >> > > Iirc some of the make release stuff calls into here, but that > >> > > may of changed to use src/Makefile targets. distrib-dirs comes > >> > > to mind. > >> > > >> > Sure, but those can go away or be updated as needed.. > >> > >> So again, no plan yet? > > > > Most of them are gone, I am still in progress on some of it. See > > the github branch above. > > > > My testing is all done by building release VMs and comparing them > > against a VM built from the last merge from HEAD. So I will update > > the release stuff as I go. It is my responsibility to keep the > > release stuff working as I change these. > > Have you checked mergemaster? IIRC it uses the distribution target. Yup, this does not affect the distribution target. Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
Quoting Brad Davis (from Mon, 04 Jun 2018 12:55:50 -0600): On Mon, Jun 4, 2018, at 12:47 PM, Rodney W. Grimes wrote: [ Charset UTF-8 unsupported, converting... ] > On Mon, Jun 4, 2018, at 10:57 AM, Rodney W. Grimes wrote: > > > On Mon, Jun 4, 2018, at 9:29 AM, Rodney W. Grimes wrote: > > > > I believe there are also other external consumers of this. > > > > > > Such as? > > > > Iirc some of the make release stuff calls into here, but that > > may of changed to use src/Makefile targets. distrib-dirs comes > > to mind. > > Sure, but those can go away or be updated as needed.. So again, no plan yet? Most of them are gone, I am still in progress on some of it. See the github branch above. My testing is all done by building release VMs and comparing them against a VM built from the last merge from HEAD. So I will update the release stuff as I go. It is my responsibility to keep the release stuff working as I change these. Have you checked mergemaster? IIRC it uses the distribution target. Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF pgpef93PHwsd7.pgp Description: Digitale PGP-Signatur
Re: svn commit: r334617 - in head: . etc
On Mon, Jun 4, 2018, at 12:47 PM, Rodney W. Grimes wrote: > [ Charset UTF-8 unsupported, converting... ] > > On Mon, Jun 4, 2018, at 10:57 AM, Rodney W. Grimes wrote: > > > > On Mon, Jun 4, 2018, at 9:29 AM, Rodney W. Grimes wrote: > > > > > [ Charset UTF-8 unsupported, converting... ] > > > > > > On Mon, Jun 4, 2018 at 10:17 AM, Brad Davis > > > > > > wrote: > > > > > > > Author: brd > > > > > > > Date: Mon Jun 4 15:17:24 2018 > > > > > > > New Revision: 334617 > > > > > > > URL: https://svnweb.freebsd.org/changeset/base/334617 > > > > > > > > > > > > > > Log: > > > > > > > Move /sys symlink creating out of etc/Makefile. > > > > > > > > > > > > > > This is prep for etc/Makefile going away. > > > > > > > > > > > > > > Approved by: bapt (mentor) > > > > > > > > > > > > > > > > > > > Woah, woah, woah, woah. =) May I ask what your plan for etc/Makefile > > > > > > is? Some of the NO_ROOT stuff there seems to be terribly broken and > > > > > > needs to be fixed; this was on my 'some day to fix' list. > > > > > > > > > > Yes please, much more information here. I use some of the targets > > > > > in src/etc/Makefile such as distribution: > > > > > > > > All the config files need to be pushed back next to the source they > > > > belong to. > > > > > > That is fine, but there is stuff other than config files, how do you plan > > > to handle that? > > > > Moving them as appropriate just like the above.. > > So another words you have no plan yet? It is largely done here: https://github.com/brd/freebsd/tree/etc-DIR/etc I am working on stragglers.. > > > > What do you use these targets for? > > > > > > Building custom installation sets, building nfs shares. > > > > OK, what commands specifically are you calling in etc/ directly and why? > > I said in my first reply specifically distribution: > > > > > I would expect the targets in the root of the src tree would handle that > > stuff for you? > > hierarchy: may But why do you run them yourself? > > > > > I believe there are also other external consumers of this. > > > > > > > > Such as? > > > > > > Iirc some of the make release stuff calls into here, but that > > > may of changed to use src/Makefile targets. distrib-dirs comes > > > to mind. > > > > Sure, but those can go away or be updated as needed.. > > So again, no plan yet? Most of them are gone, I am still in progress on some of it. See the github branch above. My testing is all done by building release VMs and comparing them against a VM built from the last merge from HEAD. So I will update the release stuff as I go. It is my responsibility to keep the release stuff working as I change these. Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
[ Charset UTF-8 unsupported, converting... ] > On Mon, Jun 4, 2018, at 10:57 AM, Rodney W. Grimes wrote: > > > On Mon, Jun 4, 2018, at 9:29 AM, Rodney W. Grimes wrote: > > > > [ Charset UTF-8 unsupported, converting... ] > > > > > On Mon, Jun 4, 2018 at 10:17 AM, Brad Davis wrote: > > > > > > Author: brd > > > > > > Date: Mon Jun 4 15:17:24 2018 > > > > > > New Revision: 334617 > > > > > > URL: https://svnweb.freebsd.org/changeset/base/334617 > > > > > > > > > > > > Log: > > > > > > Move /sys symlink creating out of etc/Makefile. > > > > > > > > > > > > This is prep for etc/Makefile going away. > > > > > > > > > > > > Approved by: bapt (mentor) > > > > > > > > > > > > > > > > Woah, woah, woah, woah. =) May I ask what your plan for etc/Makefile > > > > > is? Some of the NO_ROOT stuff there seems to be terribly broken and > > > > > needs to be fixed; this was on my 'some day to fix' list. > > > > > > > > Yes please, much more information here. I use some of the targets > > > > in src/etc/Makefile such as distribution: > > > > > > All the config files need to be pushed back next to the source they > > > belong to. > > > > That is fine, but there is stuff other than config files, how do you plan > > to handle that? > > Moving them as appropriate just like the above.. So another words you have no plan yet? > > > What do you use these targets for? > > > > Building custom installation sets, building nfs shares. > > OK, what commands specifically are you calling in etc/ directly and why? I said in my first reply specifically distribution: > > I would expect the targets in the root of the src tree would handle that > stuff for you? hierarchy: may > > > > I believe there are also other external consumers of this. > > > > > > Such as? > > > > Iirc some of the make release stuff calls into here, but that > > may of changed to use src/Makefile targets. distrib-dirs comes > > to mind. > > Sure, but those can go away or be updated as needed.. So again, no plan yet? > Regards, > Brad Davis -- Rod Grimes rgri...@freebsd.org ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Mon, Jun 4, 2018, at 10:57 AM, Rodney W. Grimes wrote: > > On Mon, Jun 4, 2018, at 9:29 AM, Rodney W. Grimes wrote: > > > [ Charset UTF-8 unsupported, converting... ] > > > > On Mon, Jun 4, 2018 at 10:17 AM, Brad Davis wrote: > > > > > Author: brd > > > > > Date: Mon Jun 4 15:17:24 2018 > > > > > New Revision: 334617 > > > > > URL: https://svnweb.freebsd.org/changeset/base/334617 > > > > > > > > > > Log: > > > > > Move /sys symlink creating out of etc/Makefile. > > > > > > > > > > This is prep for etc/Makefile going away. > > > > > > > > > > Approved by: bapt (mentor) > > > > > > > > > > > > > Woah, woah, woah, woah. =) May I ask what your plan for etc/Makefile > > > > is? Some of the NO_ROOT stuff there seems to be terribly broken and > > > > needs to be fixed; this was on my 'some day to fix' list. > > > > > > Yes please, much more information here. I use some of the targets > > > in src/etc/Makefile such as distribution: > > > > All the config files need to be pushed back next to the source they belong > > to. > > That is fine, but there is stuff other than config files, how do you plan > to handle that? Moving them as appropriate just like the above.. > > What do you use these targets for? > > Building custom installation sets, building nfs shares. OK, what commands specifically are you calling in etc/ directly and why? I would expect the targets in the root of the src tree would handle that stuff for you? > > > I believe there are also other external consumers of this. > > > > Such as? > > Iirc some of the make release stuff calls into here, but that > may of changed to use src/Makefile targets. distrib-dirs comes > to mind. Sure, but those can go away or be updated as needed.. Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
> On Mon, Jun 4, 2018, at 9:29 AM, Rodney W. Grimes wrote: > > [ Charset UTF-8 unsupported, converting... ] > > > On Mon, Jun 4, 2018 at 10:17 AM, Brad Davis wrote: > > > > Author: brd > > > > Date: Mon Jun 4 15:17:24 2018 > > > > New Revision: 334617 > > > > URL: https://svnweb.freebsd.org/changeset/base/334617 > > > > > > > > Log: > > > > Move /sys symlink creating out of etc/Makefile. > > > > > > > > This is prep for etc/Makefile going away. > > > > > > > > Approved by: bapt (mentor) > > > > > > > > > > Woah, woah, woah, woah. =) May I ask what your plan for etc/Makefile > > > is? Some of the NO_ROOT stuff there seems to be terribly broken and > > > needs to be fixed; this was on my 'some day to fix' list. > > > > Yes please, much more information here. I use some of the targets > > in src/etc/Makefile such as distribution: > > All the config files need to be pushed back next to the source they belong to. That is fine, but there is stuff other than config files, how do you plan to handle that? > What do you use these targets for? Building custom installation sets, building nfs shares. > > > I believe there are also other external consumers of this. > > Such as? Iirc some of the make release stuff calls into here, but that may of changed to use src/Makefile targets. distrib-dirs comes to mind. -- Rod Grimes rgri...@freebsd.org ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Mon, Jun 4, 2018, at 9:29 AM, Rodney W. Grimes wrote: > [ Charset UTF-8 unsupported, converting... ] > > On Mon, Jun 4, 2018 at 10:17 AM, Brad Davis wrote: > > > Author: brd > > > Date: Mon Jun 4 15:17:24 2018 > > > New Revision: 334617 > > > URL: https://svnweb.freebsd.org/changeset/base/334617 > > > > > > Log: > > > Move /sys symlink creating out of etc/Makefile. > > > > > > This is prep for etc/Makefile going away. > > > > > > Approved by: bapt (mentor) > > > > > > > Woah, woah, woah, woah. =) May I ask what your plan for etc/Makefile > > is? Some of the NO_ROOT stuff there seems to be terribly broken and > > needs to be fixed; this was on my 'some day to fix' list. > > Yes please, much more information here. I use some of the targets > in src/etc/Makefile such as distribution: All the config files need to be pushed back next to the source they belong to. What do you use these targets for? > I believe there are also other external consumers of this. Such as? Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Mon, Jun 4, 2018, at 9:22 AM, Kyle Evans wrote: > On Mon, Jun 4, 2018 at 10:17 AM, Brad Davis wrote: > > Author: brd > > Date: Mon Jun 4 15:17:24 2018 > > New Revision: 334617 > > URL: https://svnweb.freebsd.org/changeset/base/334617 > > > > Log: > > Move /sys symlink creating out of etc/Makefile. > > > > This is prep for etc/Makefile going away. > > > > Approved by: bapt (mentor) > > > > Woah, woah, woah, woah. =) May I ask what your plan for etc/Makefile > is? Some of the NO_ROOT stuff there seems to be terribly broken and > needs to be fixed; this was on my 'some day to fix' list. It goes away in favor of using CONFS= and push the config files back to where the src lives for the particular config file. So I would guess that this will fix the NO_ROOT stuff you are referring to, or at least move it to a central location (share/mk/) Regards, Brad Davis ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
[ Charset UTF-8 unsupported, converting... ] > On Mon, Jun 4, 2018 at 10:17 AM, Brad Davis wrote: > > Author: brd > > Date: Mon Jun 4 15:17:24 2018 > > New Revision: 334617 > > URL: https://svnweb.freebsd.org/changeset/base/334617 > > > > Log: > > Move /sys symlink creating out of etc/Makefile. > > > > This is prep for etc/Makefile going away. > > > > Approved by: bapt (mentor) > > > > Woah, woah, woah, woah. =) May I ask what your plan for etc/Makefile > is? Some of the NO_ROOT stuff there seems to be terribly broken and > needs to be fixed; this was on my 'some day to fix' list. Yes please, much more information here. I use some of the targets in src/etc/Makefile such as distribution: I believe there are also other external consumers of this. -- Rod Grimes rgri...@freebsd.org ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
Re: svn commit: r334617 - in head: . etc
On Mon, Jun 4, 2018 at 10:17 AM, Brad Davis wrote: > Author: brd > Date: Mon Jun 4 15:17:24 2018 > New Revision: 334617 > URL: https://svnweb.freebsd.org/changeset/base/334617 > > Log: > Move /sys symlink creating out of etc/Makefile. > > This is prep for etc/Makefile going away. > > Approved by: bapt (mentor) > Woah, woah, woah, woah. =) May I ask what your plan for etc/Makefile is? Some of the NO_ROOT stuff there seems to be terribly broken and needs to be fixed; this was on my 'some day to fix' list. ___ svn-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
