opnsense-src/etc/mtree
Olivier Certner 2beba7b456
Remove remnants of portsnap(8)
This was prompted by noticing that '/var/db/portsnap' still exists on
newly-installed machines.

With this change, all mentions of portsnap(8) in the tree are gone,
except for the historical note in the AUTHORS section of manpage
phttpget(8).

locate(1) will thus start indexing again '/var/db/portsnap' on machines
where this directory still exists, which may be a good way to push
administrators to delete it.

Reviewed by:            cperciva
Approved by:            emaste (mentor)
MFC after:              3 days
Sponsored by:           The FreeBSD Foundation
Differential Revision:  https://reviews.freebsd.org/D45023

(cherry picked from commit 9b30b96c1fa4ee0dfc540878fbb3247bf92d19eb)

ObsoleteFiles.inc: Remove /var/db/portsnap

This is a followup to commit "Remove remnants of portsnap(8)"
(9b30b96c1fa4).  I wasn't aware of OLD_DIRS.

Approved by:            markj (mentor)
MFC after:              1 day
MFC with:               9b30b96c1fa4
Sponsored by:           The FreeBSD Foundation
Differential Revision:  https://reviews.freebsd.org/D45023

(cherry picked from commit 54bbcc09a72b5d7a581f51416c9e635a33c2f884)

Approved by:            markj (mentor)

(cherry picked from commit 9f06e6c990)

Approved by:            markj (mentor)
Approved by:            re (cperciva)
2024-05-09 17:18:53 +09:00
..
BSD.debug.dist Merge llvm-project main llvmorg-18-init-15088-gd14ee76181fb 2024-04-19 23:12:03 +02:00
BSD.include.dist Merge llvm-project main llvmorg-18-init-15088-gd14ee76181fb 2024-04-19 23:12:03 +02:00
BSD.lib32.dist Remove $FreeBSD$: one-line sh pattern 2023-08-16 11:55:03 -06:00
BSD.release.dist Remove $FreeBSD$: one-line sh pattern 2023-08-16 11:55:03 -06:00
BSD.root.dist Remove $FreeBSD$: one-line sh pattern 2023-08-16 11:55:03 -06:00
BSD.sendmail.dist Remove $FreeBSD$: one-line sh pattern 2023-08-16 11:55:03 -06:00
BSD.tests.dist dtrace: Add the 'oformat' libdtrace option 2024-04-15 10:05:13 -04:00
BSD.usr.dist BSD.usr.dist: remove empty /usr/libdata/gcc directory 2024-05-01 15:42:57 -03:00
BSD.var.dist Remove remnants of portsnap(8) 2024-05-09 17:18:53 +09:00
Makefile etc: remove leftover leading empty comments, blank lines 2023-08-22 13:03:28 -05:00
README etc: remove leftover leading empty comments, blank lines 2023-08-22 13:03:28 -05:00

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.