Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/etc/defaults/Makefile

26 lines
673 B
Makefile
Raw Normal View History

Include npf_boot rc.d scripts which loads an interim config early in boot. By default /etc/default/npf.boot.conf which can be overriden by /etc/npf.boot.conf.
2019-04-10 03:32:15 +03:00
# $NetBSD: Makefile,v 1.7 2019/04/10 00:32:15 sevan Exp $
move default config files from /etc/default -> /etc/defaults, to be consistent with what FreeBSD uses /etc/defaults for and since SVR4 uses /etc/default for another purpose. as discussed on tech-userlevel, and no objections were made.
2000-10-01 09:46:03 +04:00
Modify etc/defaults/Makefile so that architectures can specify an additional rc.conf file. This one should reside under etc/etc.${MACHINE}/, and will get automatically appended to etc/defaults/rc.conf at build time if present. This is used by i386 and amd64 to append a small MD rc.conf(5) configuration at the end of the defaults/rc.conf file, so that powerd(8) can be started by default when we are running in a Xen environment. This is needed to support save/restore functions for domains. From all the alternatives proposed to fix that issue (from /etc/rc.conf parsing in postinstall to etc/defaults/rc.conf arch-hooks) I believe this one will appease everyone because it: - does not touch etc/defaults/rc.conf template file, - patches it at build time for MD hooks only when required, - does not need to parse/modify a user-specified file like /etc/rc.conf (which is a complex, error-prone operation), - only enables powerd(8) by default when conditions are met (Xen environment) while still allowing root to shoot himself in the foot if he wants to override this manually in /etc/rc.conf. See also http://mail-index.netbsd.org/tech-userlevel/2011/07/25/msg005246.html
2011-08-22 22:54:05 +04:00
.include <bsd.own.mk>
Include npf_boot rc.d scripts which loads an interim config early in boot. By default /etc/default/npf.boot.conf which can be overriden by /etc/npf.boot.conf.
2019-04-10 03:32:15 +03:00
CONFIGFILES= daily.conf monthly.conf npf.boot.conf pkgpath.conf \
security.conf weekly.conf
move default config files from /etc/default -> /etc/defaults, to be consistent with what FreeBSD uses /etc/defaults for and since SVR4 uses /etc/default for another purpose. as discussed on tech-userlevel, and no objections were made.
2000-10-01 09:46:03 +04:00
FILESDIR= /etc/defaults
FILESMODE= ${NONBINMODE}
Modify etc/defaults/Makefile so that architectures can specify an additional rc.conf file. This one should reside under etc/etc.${MACHINE}/, and will get automatically appended to etc/defaults/rc.conf at build time if present. This is used by i386 and amd64 to append a small MD rc.conf(5) configuration at the end of the defaults/rc.conf file, so that powerd(8) can be started by default when we are running in a Xen environment. This is needed to support save/restore functions for domains. From all the alternatives proposed to fix that issue (from /etc/rc.conf parsing in postinstall to etc/defaults/rc.conf arch-hooks) I believe this one will appease everyone because it: - does not touch etc/defaults/rc.conf template file, - patches it at build time for MD hooks only when required, - does not need to parse/modify a user-specified file like /etc/rc.conf (which is a complex, error-prone operation), - only enables powerd(8) by default when conditions are met (Xen environment) while still allowing root to shoot himself in the foot if he wants to override this manually in /etc/rc.conf. See also http://mail-index.netbsd.org/tech-userlevel/2011/07/25/msg005246.html
2011-08-22 22:54:05 +04:00
# Manage arch-specific rc.conf(5) file
CONFIGFILES+= rc_conf
FILESNAME_rc_conf= rc.conf
FILESBUILD_rc_conf= yes
Arch-specific rc.conf files are not really autonomous rc.conf files, they are appended to the end of etc/defaults/rc.conf. So rename them to rc.conf.append for clarity, as suggested by mrg@. Adapt Makefile accordingly.
2011-08-23 00:48:38 +04:00
# If present, rc.conf.append is added to the end of the default rc.conf file
Modify etc/defaults/Makefile so that architectures can specify an additional rc.conf file. This one should reside under etc/etc.${MACHINE}/, and will get automatically appended to etc/defaults/rc.conf at build time if present. This is used by i386 and amd64 to append a small MD rc.conf(5) configuration at the end of the defaults/rc.conf file, so that powerd(8) can be started by default when we are running in a Xen environment. This is needed to support save/restore functions for domains. From all the alternatives proposed to fix that issue (from /etc/rc.conf parsing in postinstall to etc/defaults/rc.conf arch-hooks) I believe this one will appease everyone because it: - does not touch etc/defaults/rc.conf template file, - patches it at build time for MD hooks only when required, - does not need to parse/modify a user-specified file like /etc/rc.conf (which is a complex, error-prone operation), - only enables powerd(8) by default when conditions are met (Xen environment) while still allowing root to shoot himself in the foot if he wants to override this manually in /etc/rc.conf. See also http://mail-index.netbsd.org/tech-userlevel/2011/07/25/msg005246.html
2011-08-22 22:54:05 +04:00
RCCONF_SRCS= ${.CURDIR}/rc.conf
Arch-specific rc.conf files are not really autonomous rc.conf files, they are appended to the end of etc/defaults/rc.conf. So rename them to rc.conf.append for clarity, as suggested by mrg@. Adapt Makefile accordingly.
2011-08-23 00:48:38 +04:00
.if exists(../etc.${MACHINE}/rc.conf.append)
RCCONF_SRCS+= ${.CURDIR}/../etc.${MACHINE}/rc.conf.append
Modify etc/defaults/Makefile so that architectures can specify an additional rc.conf file. This one should reside under etc/etc.${MACHINE}/, and will get automatically appended to etc/defaults/rc.conf at build time if present. This is used by i386 and amd64 to append a small MD rc.conf(5) configuration at the end of the defaults/rc.conf file, so that powerd(8) can be started by default when we are running in a Xen environment. This is needed to support save/restore functions for domains. From all the alternatives proposed to fix that issue (from /etc/rc.conf parsing in postinstall to etc/defaults/rc.conf arch-hooks) I believe this one will appease everyone because it: - does not touch etc/defaults/rc.conf template file, - patches it at build time for MD hooks only when required, - does not need to parse/modify a user-specified file like /etc/rc.conf (which is a complex, error-prone operation), - only enables powerd(8) by default when conditions are met (Xen environment) while still allowing root to shoot himself in the foot if he wants to override this manually in /etc/rc.conf. See also http://mail-index.netbsd.org/tech-userlevel/2011/07/25/msg005246.html
2011-08-22 22:54:05 +04:00
.endif
rc_conf: ${RCCONF_SRCS}
${_MKTARGET_CREATE}
${TOOL_CAT} ${RCCONF_SRCS} > ${.TARGET}
move default config files from /etc/default -> /etc/defaults, to be consistent with what FreeBSD uses /etc/defaults for and since SVR4 uses /etc/default for another purpose. as discussed on tech-userlevel, and no objections were made.
2000-10-01 09:46:03 +04:00
.include <bsd.prog.mk>