From fb3ffcec038cad121fa6166551c2ddb7b3d07fb3 Mon Sep 17 00:00:00 2001
From: Jaromil <jaromil@dyne.org>
Date: Mon, 25 Jan 2021 15:14:31 +0100
Subject: [PATCH] manpage mention of fallocate(1) for faster dig

---
 doc/tomb.1 | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/doc/tomb.1 b/doc/tomb.1
index cc51256..c5bf359 100644
--- a/doc/tomb.1
+++ b/doc/tomb.1
@@ -32,7 +32,10 @@ Generates a file that can be used as a tomb and will occupy as much
 space as its desired initial size, the unlocked \fI.tomb\fR file can
 then be locked using a \fIkey\fR. It takes a mandatory \fI-s\fR option
 which is the size in megabytes (MiB). Tombs are digged using random
-data gathered from a non-blocking source (/dev/urandom).
+data gathered from a non-blocking source (/dev/urandom). For very
+large tombs this may take up too much time and entropy, then it is
+possible to use \fIfallocate(1)\fR being aware it does not pre-fill
+with random data, decreasing the tomb's security.
 
 .B
 .IP "forge"