> 
> > It's put there, as an example file and as a hint to where the files
> > might live.  On the NetBSD nameservers i've run, what i do
> > is ln -s namedb/named.boot /etc/named.boot .
> 
> One might, however, argue for moving /etc/namedb to eg. /var/db/namedb
> or some such.

From the 4.4 manual set heir(7) manual page:
/etc/	system configuration files and scripts
/var/	multi-purpose log, temporary, transient, and spool files

	db/	miscellaneous automatically generated system-specific
		database files

I can not see moving *any* type of configuration stuff to /var, I believe
it was the intent of CSRG when doing the /var the way they did every thing
under it is to be program, not human generated.  And looking at the manual
page it appears that everything in there meats this criteria.

I have seen many proposals to move ``configuration'' type data into var,
but IMHO think this would just be defeating the original purpose.  Note
that this purpose is *different* than what some other vendors have done
with /var (ie, diskless type support).

Some people also seem to want to do this to create a read only /, which
is a fine idea in itself, but I surely would not want my precious /etc
files stored on one of the most likely partitions to have file corruption
after a crash there is.  I value my /etc more than that :-)).  

-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                   Custom computers for FreeBSD

------------------------------------------------------------------------------