freebsd-skq/etc/mtree
Gregory Neil Shapiro 37a4b79385 Create a separate directory for dynamic zones which is owned by the bind
user (for creation of the zone journal file).  This is separate from the
master/ directory for security.  Give an example dynamic zone in the
sample named.conf.

Approved by:	dougb
Noticed by:	Eivind Olsen <eivind at aminor.no>
MFC after:	1 week
2004-11-04 05:24:29 +00:00
..
BIND.chroot.dist Create a separate directory for dynamic zones which is owned by the bind 2004-11-04 05:24:29 +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 Add common share/locale directories (everything used by >= 5 ports [1]) and 2004-05-31 07:34:40 +00:00
BSD.release.dist Mention the path to the README file in the header comment. 2001-06-26 13:50:33 +00:00
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 Scheduled sweep using the README guidelines. 2003-11-29 18:22:01 +00:00
BSD.usr.dist Apply README guidelines (no tabs). 2004-10-19 17:32:56 +00:00
BSD.var.dist Remove a redundant "uname=root". 2004-10-15 08:57:24 +00:00
BSD.x11-4.dist Add common share/locale directories (everything used by >= 5 ports [1]) and 2004-05-31 07:34:40 +00:00
BSD.x11.dist Reincarnate SETUID code in man(1), not compiled in by default. 2002-01-22 15:15:38 +00:00
Makefile For variables that are only checked with defined(), don't provide 2004-10-24 15:33:08 +00:00
README Sigh, this README is not a shell script. 2002-05-18 12:37:19 +00:00

$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.