On Sun, 21 Mar 1999, Jordan K. Hubbard wrote:
> Index: netstart
> ===================================================================
> RCS file: /home/ncvs/src/etc/netstart,v
> retrieving revision 1.53
> diff -u -u -r1.53 netstart
> --- netstart 1999/02/10 18:08:16 1.53
> +++ netstart 1999/03/22 01:54:16
> @@ -12,8 +12,11 @@
> # If there is a global system configuration file, suck it in.
> if [ -f /etc/defaults/rc.conf ]; then
> . /etc/defaults/rc.conf
> -elif [ -f /etc/rc.conf ]; then
> - . /etc/rc.conf
> + for i in ${rc_conf_files}; do
> + if [ -f $i ]; then
> + . $i
> + fi
> + done
> fi
There is a problem with this approach.
/etc/defaults/rc.conf defines ${rc_conf_files}
However, I have no chance to override it before it is used.
When I wrote my comment about "code" in rc.conf, I was
actually thinking about /etc/defaults/rc.conf and the
recursion loop that that creates when someone copies it to
/etc/rc.conf.
You can, and IMHO should, make the defaults strictly variables.
However, I fear that you need a bit more logic to allow the
overriding of ${rc_conf_files}.
To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-current" in the body of the message
