1 .\" Copyright (c) 1989, 1990, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 4. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" From: @(#)mtree.8 8.2 (Berkeley) 12/11/93
36 .Nd map a directory hierarchy
59 .Op Fl X Ar exclude-list
64 utility compares the file hierarchy rooted in the current directory against a
65 specification read from the standard input.
66 Messages are written to the standard output for any files whose
67 characteristics do not match the specifications, or which are
68 missing from either the file hierarchy or the specification.
70 The options are as follows:
73 Follow all symbolic links in the file hierarchy.
75 Do not follow symbolic links in the file hierarchy, instead consider
76 the symbolic link itself in any comparisons.
79 Modify the owner, group, permissions, and modification time of existing
80 files to match the specification and create any missing directories or
82 User, group and permissions must all be specified for missing directories
84 Corrected mismatches are not considered errors.
86 Print a specification for the file hierarchy to the standard output.
88 Ignore everything except directory type files.
90 Do not complain about files that are in the file hierarchy, but not in the
93 Indent the output 4 spaces each time a directory level is descended when
94 create a specification with the
97 This does not affect either the /set statements or the comment before each
99 It does however affect the comment before the close of each directory.
101 Do not emit pathname comments when creating a specification.
103 a comment is emitted before each directory and before the close of that
104 directory when using the
109 Do not complain when a
111 directory cannot be created because it already exists.
112 This occurs when the directory is a symbolic link.
114 Remove any files in the file hierarchy that are not described in the
119 except a status of 2 is returned if the file hierarchy did not match
122 Make some errorconditions non-fatal warnings.
124 Do not descend below mount points in the file hierarchy.
126 Read the specification from
128 instead of from the standard input.
130 If this option is specified twice, the two specifications are compared
131 to each other rather than to the file hierarchy.
132 The specifications be sorted like output generated using
134 The output format in this case is somewhat remniscent of
136 having "in first spec only", "in second spec only", and "different"
137 columns, prefixed by zero, one and two TAB characters respectively.
138 Each entry in the "different" column occupies two lines, one from each specification.
140 Add the specified (whitespace or comma separated)
142 to the current set of keywords.
144 Use the ``type'' keyword plus the specified (whitespace or comma separated)
146 instead of the current set of keywords.
148 Use the file hierarchy rooted in
150 instead of the current directory.
152 Display a single checksum to the standard error output that represents all
153 of the files for which the keyword
156 The checksum is seeded with the specified value.
157 .It Fl X Ar exclude-list
158 The specified file contains
160 patterns matching files to be excluded from
161 the specification, one to a line.
162 If the pattern contains a
164 character, it will be matched against entire pathnames (relative to
165 the starting directory); otherwise,
166 it will be matched against basenames only.
167 No comments are allowed in
173 Specifications are mostly composed of ``keywords'', i.e., strings
174 that specify values relating to files.
175 No keywords have default values, and if a keyword has no value set, no
176 checks based on it are performed.
178 Currently supported keywords are as follows:
181 The checksum of the file using the default algorithm specified by
186 The file flags as a symbolic name.
189 for information on these names.
190 If no flags are to be set the string
192 may be used to override the current default.
194 Ignore any file hierarchy below this file.
196 The file group as a numeric value.
198 The file group as a symbolic name.
200 The MD5 message digest of the file.
206 message digest of the file.
212 message digest of the file.
213 .It Cm ripemd160digest
216 message digest of the file.
218 The current file's permissions as a numeric (octal) or symbolic
221 The number of hard links the file is expected to have.
223 Make sure this file or directory exists but otherwise ignore all attributes.
225 The file is optional; do not complain about the file if it is
226 not in the file hierarchy.
228 The file owner as a numeric value.
230 The file owner as a symbolic name.
232 The size, in bytes, of the file.
234 The file the symbolic link is expected to reference.
236 The last modification time of the file, in seconds and nanoseconds.
237 The value should include a period character and exactly nine digits
240 The type of the file; may be set to any one of the following:
242 .Bl -tag -width Cm -compact
246 character special device
260 The default set of keywords are
271 There are four types of lines in a specification.
273 The first type of line sets a global value for a keyword, and consists of
274 the string ``/set'' followed by whitespace, followed by sets of keyword/value
275 pairs, separated by whitespace.
276 Keyword/value pairs consist of a keyword, followed by an equals sign
277 (``=''), followed by a value, without whitespace characters.
278 Once a keyword has been set, its value remains unchanged until either
281 The second type of line unsets keywords and consists of the string
282 ``/unset'', followed by whitespace, followed by one or more keywords,
283 separated by whitespace.
285 The third type of line is a file specification and consists of a file
286 name, followed by whitespace, followed by zero or more whitespace
287 separated keyword/value pairs.
288 The file name may be preceded by whitespace characters.
289 The file name may contain any of the standard file name matching
290 characters (``['', ``]'', ``?'' or ``*''), in which case files
291 in the hierarchy will be associated with the first pattern that
294 Each of the keyword/value pairs consist of a keyword, followed by an
295 equals sign (``=''), followed by the keyword's value, without
296 whitespace characters.
297 These values override, without changing, the global value of the
298 corresponding keyword.
300 All paths are relative.
301 Specifying a directory will cause subsequent files to be searched
302 for in that directory hierarchy.
303 Which brings us to the last type of line in a specification: a line
304 containing only the string
306 causes the current directory
307 path to ascend one level.
309 Empty lines and lines whose first non-whitespace character is a hash
310 mark (``#'') are ignored.
314 utility exits with a status of 0 on success, 1 if any error occurred,
315 and 2 if the file hierarchy did not match the specification.
316 A status of 2 is converted to a status of 0 if the
320 .Bl -tag -width /etc/mtree -compact
322 system specification directory
327 To detect system binaries that have been ``trojan horsed'', it is recommended
332 be run on the file systems, and a copy of the results stored on a different
333 machine, or, at least, in encrypted form.
334 The output file itself should be digested using the
341 should be run against the on-line specifications.
342 While it is possible for the bad guys to change the on-line specifications
343 to conform to their modified binaries, it is believed to be
344 impractical for them to create a modified specification which has
345 the same SHA-256 digest as the original.
351 options can be used in combination to create directory hierarchies
352 for distributions and other such things; the files in
354 were used to create almost all directories in this
360 style BSD.*.dist file, use
367 .Cm uname,gname,mode,nochange.
385 digest capability was added in
387 in response to the widespread use of programs which can spoof
393 digests were added in
395 as new attacks have demonstrated weaknesses in
401 Support for file flags was added in
403 and mostly comes from