freebsd-dev

History

Mark Johnston e505460228 Import the netdump client code. This is a component of a system which lets the kernel dump core to a remote host after a panic, rather than to a local storage device. The server component is available in the ports tree. netdump is particularly useful on diskless systems. The netdump(4) man page contains some details describing the protocol. Support for configuring netdump will be added to dumpon(8) in a future commit. To use netdump, the kernel must have been compiled with the NETDUMP option. The initial revision of netdump was written by Darrell Anderson and was integrated into Sandvine's OS, from which this version was derived. Reviewed by: bdrewery, cem (earlier versions), julian, sbruno MFC after: 1 month X-MFC note: use a spare field in struct ifnet Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D15253		2018-05-06 00:38:29 +00:00
..
BSD.debug.dist	Update clang versioned dir in mtree files.	2017-12-20 20:28:40 +00:00
BSD.include.dist	Import the netdump client code.	2018-05-06 00:38:29 +00:00
BSD.lib32.dist	Handle lib32 files during delete-old* when MK_LIB32=no.	2015-10-20 20:35:34 +00:00
BSD.libsoft.dist	Add libsoft to the tree, just like lib32.	2016-01-03 04:32:05 +00:00
BSD.release.dist
BSD.root.dist	Move /boot/overlays to /boot/dtb/overlays	2018-03-19 16:16:12 +00:00
BSD.sendmail.dist
BSD.tests.dist	Properly do a deep copy of the ioctls capability array for fget_cap().	2018-04-17 18:07:40 +00:00
BSD.usr.dist	Introduce dwatch(1) as a tool for making DTrace more useful	2018-03-06 23:44:19 +00:00
BSD.var.dist	tabs -> spaces in etc/mtree	2017-01-05 02:47:56 +00:00
Makefile	Unconditionally install etc/mtree/BSD.debug.dist again	2017-07-25 00:28:23 +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/ *$//' >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.