correct documentation on -s option

somewhere mentioned as --size, but the option is really just -s
fixes #100
This commit is contained in:
Jaromil 2014-01-12 23:39:59 +01:00
parent f9805731f1
commit 325633d2fb
2 changed files with 6 additions and 6 deletions

View File

@ -30,8 +30,8 @@ harddisk and its key file on a USB stick.
.IP "dig" .IP "dig"
Generates a file that can be used as a tomb and will occupy as much 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 space as its desired initial size, the unlocked \fI.tomb\fR file can
then be locked using a \fIkey\fR. It takes a mandatory option which is then be locked using a \fIkey\fR. It takes a mandatory \fI-s\fR option which is
the \fI--size\fR in megabytes (MiB). Tombs are digged using the size in megabytes (MiB). Tombs are digged using
low-quality random data (/dev/urandom). low-quality random data (/dev/urandom).
.B .B
@ -127,7 +127,7 @@ key and the second and last argument the tomb file.
.B .B
.IP "resize" .IP "resize"
Increase the size of a tomb file to the amount specified by the Increase the size of a tomb file to the amount specified by the
\fI--size\fR option in megabytes (MiB). Full access to the tomb using \fI-s\fR option, which is the new size in megabytes (MiB). Full access to the tomb using
a key (\fI-k\fR) and its password is requires. Tombs can only grow and a key (\fI-k\fR) and its password is requires. Tombs can only grow and
can never be made smaller. This command makes use of the cryptsetup can never be made smaller. This command makes use of the cryptsetup
resize feature and the resize2fs command: its much more practical than resize feature and the resize2fs command: its much more practical than

6
tomb
View File

@ -320,7 +320,7 @@ Syntax: tomb [options] command [arguments]
Commands: Commands:
// Creation: // Creation:
dig create a new empty TOMB file of --size in MB dig create a new empty TOMB file of size -s in MB
forge create a new KEY file and set its password forge create a new KEY file and set its password
lock installs a lock on a TOMB to use it with KEY lock installs a lock on a TOMB to use it with KEY
@ -334,7 +334,7 @@ Commands:
EOF EOF
if [ "$RESIZER" = 1 ]; then if [ "$RESIZER" = 1 ]; then
cat <<EOF cat <<EOF
resize resize a TOMB to a new --size (can only grow) resize resize a TOMB to a new size -s (can only grow)
EOF EOF
fi fi
cat <<EOF cat <<EOF
@ -1117,7 +1117,7 @@ dig_tomb() {
# require the specification of the size of the tomb (-s) in MB # require the specification of the size of the tomb (-s) in MB
tombsize="`option_value -s`" tombsize="`option_value -s`"
[ $tombsize ] || die "Size argument missing, use --size" [ $tombsize ] || die "Size argument missing, use -s"
[[ $tombsize != <-> ]] && die "Size argument is not an integer" [[ $tombsize != <-> ]] && die "Size argument is not an integer"