File Manager

003 File Manager

Current Path: /usr/src/etc/mtree

📁 ..
📄 BSD.debug.dist(1.13 KB)
📄 BSD.include.dist(3.59 KB)
📄 BSD.lib32.dist(326 B)
📄 BSD.libsoft.dist(217 B)
📄 BSD.release.dist(316 B)
📄 BSD.root.dist(1.89 KB)
📄 BSD.sendmail.dist(449 B)
📄 BSD.tests.dist(21.67 KB)
📄 BSD.usr.dist(24.51 KB)
📄 BSD.var.dist(2.2 KB)
📄 Makefile(625 B)
📄 README(2.18 KB)

Editing: 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/ *$//' >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 committed, as it 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.

003 File Manager

Editing: README

Upload File

Create Folder