>>> Clearly (?) only a single file for user parameter changes is required.
>
>>Exactly. But "/etc/rc.conf" is sourced *before* "/etc/rc.conf.d/$name",
>
>That presumably is a bug :-)
>If the various conf files are processed in the correct order, life is
>much simpler for everyone.

no, that's the intended behavior.  rc.conf is for settings.  rc.conf.d
is for overriding those settings.  rc.conf.d can also provide scoped
pieces of sh stuff that don't belong in rc.conf.  for example: here's
my /etc/rc.conf.d/ssh file:

	if [ "$sshd" = pkgsrc ]; then
		sshd=YES
		command="/usr/pkg/sbin/${name}"
		required_files="/etc/${name}_config"
		start_precmd=:
		extra_commands="reload"
	fi

which allows me to set a machine to YES, NO, or pkgsrc.  neat, eh?

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."