Keep in mind as you consider "changing" rather than "extending" that there are many systems with existing files, and the NetBSD way is that if you upgrade the system to a new version, then as little breakage as possible should ensue. Yes, technically you should read all the release notes, and you should merge the differences from all updated etc files to your etc, but in reality this often does not happen. So if this is more like add a new line to something like ".includedir /etc/inetd.d" which says to act is if every file in that directory was part of inetd.conf perhaps, have additional syntax so that a line that starts with some special token introduces a config stanza that is logically equivalent to a current line The big point is that the new inetd, when run with an old config file, should behave as we would have hoped, not fail to start anything, and not failing open.
Attachment:
signature.asc
Description: PGP signature