What I don't like from the new "rc.conf" approach is the name "rc.conf" ;-). I think that the old "sysconfig" should come back. Then, there would be a /etc/defaults/sysconfig (R/O), and a /etc/sysconfig (storing the site-specific config). These files would contain _only_ variable assignments. The /etc/rc.conf script would be R/O too; it would read /etc/defaults/sysconfig and /etc/sysconfig in turn.
Furthermore, both "sysconfig"s could be splitted into several files (net, nfs, time, console, isdn, etc.). In this case, another directory should be created under /etc (named "siteconfig", for example), which would be the site-specific counterpart of /etc/defaults. My 0.02 euro, -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:j...@we.lc.ehu.es Universidad del País Vasco | mailto:j...@es.freebsd.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
