From owner-freebsd-current  Sun Mar 19 17:15:04 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA03309 for current-outgoing; Sun, 19 Mar 1995 17:15:04 -0800
Received: (from pst@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA03293; Sun, 19 Mar 1995 17:15:03 -0800
Date: Sun, 19 Mar 1995 17:15:03 -0800
From: Paul Traina <pst>
Message-Id: <199503200115.RAA03293@freefall.cdrom.com>
To: wollman
Subject: /etc/rc named change
Cc: current
Sender: current-owner@FreeBSD.org
Precedence: bulk

I think that the change in boot file location for named is gratuitous.
The world expects named to look for /etc/named.boot and when you changed
it, you screwed everyone who runs a nameserver with their boot file as
/etc/named.boot.

Lots of folks don't want to worry about their named stuff getting overwritten
by their OS vendor, so they keep there files in /usr/local/etc/namedb or
some such location and fix up /etc/named.boot to do the right thing.

By moving the start file with no warning, you've made things break in a
silent way (I didn't know my nameserver wasn't serving my domain for the
last 18 hours because it was busy using the bloody default files from the
distribution.)

I think a better choice would be to leave the distribution crud in /etc/namedb
as it currently is,  but have the make distribution script create a symlink
between /etc/named.boot and /etc/namedb/named.boot if no /etc/named.boot
file is present.

Paul