> Then why bother having rc.conf in the first place?  Just wire in all 
> the defaults straight into /etc/rc and leave rc.conf strictly for 
> overriding the defaults only, and eliminate rc.conf.* entirely.

Because rc.conf contains configuration variables, whereas rc contains 
commands to execute at boot time. The configuration information stored 
in rc.conf is applicable to more than just /etc/rc. Splitting out the 
configuration into a seperate file (rc.conf) means it can be sourced by
other utility scripts, such as /etc/rc.firewall. Sourcing /etc/rc to 
pick up config info would be a disaster.

And FWIW, I'm in favour of a read-only rc.conf with machine specific 
overrides in rc.conf.local. rc.conf.site should vanish.

--lyndon

Attachment: pgpkyIExEMycO.pgp
Description: PGP signature

Reply via email to