freebsd

mirror of https://git.FreeBSD.org/src.git synced 2024-12-13 10:02:38 +00:00

History

Doug Barton 8f1bb3891d Create a named chroot directory structure in /var/named, and use it by default when named is enabled. Also, improve our default directory layout by creating /var/named/etc/namedb/{master\|slave} directories, and use the former for the generated localhost* files. Rather than using pax to copy device entries, mount devfs in the chroot directory. There may be some corner cases where things need to be adjusted, but overall this structure has been well tested on a production network, and should serve the needs of the vast majority of users. UPDATING has instructions on how to do the conversion for those with existing configurations.		2004-09-28 09:46:00 +00:00
..
BIND.chroot.dist	Create a named chroot directory structure in /var/named, and use it	2004-09-28 09:46:00 +00:00
BIND.include.dist	Seperate out the optional parts of the include tree that are	2004-09-27 08:16:29 +00:00
BSD.include.dist	Remove the directories that are now only installed when the user	2004-09-27 08:18:43 +00:00
BSD.local.dist
BSD.release.dist
BSD.root.dist	Create a named chroot directory structure in /var/named, and use it	2004-09-28 09:46:00 +00:00
BSD.sendmail.dist
BSD.usr.dist	Install the documentation for bind9, and remove the /usr/share/doc/bind	2004-09-25 00:42:38 +00:00
BSD.var.dist	Create a named chroot directory structure in /var/named, and use it	2004-09-28 09:46:00 +00:00
BSD.x11-4.dist
BSD.x11.dist
Makefile	Hook the BIND.* files up to the build.	2004-09-27 08:17:51 +00:00
README

README

$FreeBSD$

Note: If you modify these files, please keep hier(7) updated!

These files are used to create empty file hierarchies for building the
system into.  Some notes about working with them are placed here to try
and keep them in good working order.

    a)  The files use 4 space indentation, and other than in the header
        comments, should not contain any tabs.  An indentation of 4 is
        preferable to the standard indentation of 8 because the indentation
        of levels in these files can become quite deep causing the line to
        overflow 80 characters.

        This also matches with the files generated when using the
        mtree -c option, which was implemented that way for the same reason.

    b)  Only directories should be listed here.

    c)  The listing should be kept in filename sorted order.

    d)  Sanity checking changes to these files can be done by following
        this procedure (the sed -e is ugly, but fixing mtree -c to
        not emit the trailing white space would be even uglier):

            mkdir /tmp/MTREE
            mtree -deU -f BSD.X.dist -p /tmp/MTREE
            mtree -cdin -k uname,gname,mode -p /tmp/MTREE | \
		sed -e 's/ *$//' | tail +5 >BSD.X.new
            diff -u BSD.X.dist BSD.X.new
            rm -r /tmp/MTREE

        Note that you will get some differences about /set lines,
        and uname= gname= on certain directory areas, mainly man page
        sections.  This is caused by mtree not having a look ahead
        mechanism for making better selections for these as it
        traverses the hierarchy.

        The BSD.X.new file should NOT be commited, will be missing the
        correct header, and important keywords like ``nochange''.  Simply
        use the diff for a sanity check to make sure things are in the
        correct order and correctly indented.

    e)  Further sanity checking of the system builds with DESTDIR=/someplace
        are more complicated, but can often catch missing entries in these
        files.  I tend to run this more complete sanity check shortly after
        the target date for a new release is announced.

        If you want details on it bug me about it via email to
        rgrimes@FreeBSD.org.