/usr/share/doc/bup/bup-drecurse.html is in bup-doc 0.29-3.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="generator" content="pandoc" />
<meta name="author" content="Avery Pennarun apenwarr@gmail.com" />
<meta name="date" content="2017-04-01" />
<title>bup-drecurse(1) Bup debian/0.29-3</title>
<style type="text/css">code{white-space: pre;}</style>
</head>
<body>
<div id="header">
<h1 class="title">bup-drecurse(1) Bup debian/0.29-3</h1>
<h2 class="author">Avery Pennarun <a href="mailto:apenwarr@gmail.com">apenwarr@gmail.com</a></h2>
<h3 class="date">2017-04-01</h3>
</div>
<h1 id="name">NAME</h1>
<p>bup-drecurse - recursively list files in your filesystem</p>
<h1 id="synopsis">SYNOPSIS</h1>
<p>bup drecurse [-x] [-q] [--exclude <em>path</em>] [--exclude-from <em>filename</em>] [--exclude-rx <em>pattern</em>] [--exclude-rx-from <em>filename</em>] [--profile] <path></p>
<h1 id="description">DESCRIPTION</h1>
<p><code>bup drecurse</code> traverses files in the filesystem in a way similar to <code>find</code>(1). In most cases, you should use <code>find</code>(1) instead.</p>
<p>This program is useful mainly for testing the file traversal algorithm used in <code>bup-index</code>(1).</p>
<p>Note that filenames are returned in reverse alphabetical order, as in <code>bup-index</code>(1). This is important because you can't generate the hash of a parent directory until you have generated the hashes of all its children. When listing files in reverse order, the parent directory will come after its children, making this easy.</p>
<h1 id="options">OPTIONS</h1>
<dl>
<dt>-x, --xdev, --one-file-system</dt>
<dd>don't cross filesystem boundaries -- though as with tar and rsync, the mount points themselves will still be reported.
</dd>
<dt>-q, --quiet</dt>
<dd>don't print filenames as they are encountered. Useful when testing performance of the traversal algorithms.
</dd>
<dt>--exclude=<em>path</em></dt>
<dd>exclude <em>path</em> from the backup (may be repeated).
</dd>
<dt>--exclude-from=<em>filename</em></dt>
<dd>read --exclude paths from <em>filename</em>, one path per-line (may be repeated). Ignore completely empty lines.
</dd>
<dt>--exclude-rx=<em>pattern</em></dt>
<dd>exclude any path matching <em>pattern</em>. See <code>bup-index</code>(1) for details, but note that unlike index, drecurse will produce relative paths if the drecurse target is a relative path. (may be repeated).
</dd>
<dt>--exclude-rx-from=<em>filename</em></dt>
<dd>read --exclude-rx patterns from <em>filename</em>, one pattern per-line (may be repeated). Ignore completely empty lines.
</dd>
<dt>--profile</dt>
<dd>print profiling information upon completion. Useful when testing performance of the traversal algorithms.
</dd>
</dl>
<h1 id="examples">EXAMPLES</h1>
<pre><code>bup drecurse -x /</code></pre>
<h1 id="see-also">SEE ALSO</h1>
<p><code>bup-index</code>(1)</p>
<h1 id="bup">BUP</h1>
<p>Part of the <code>bup</code>(1) suite.</p>
</body>
</html>
|