chiark
/
gitweb
/
~ianmdlvl
/
vbig.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
c9d8b41
)
Typo fixes to man page.
author
Richard Kettlewell
<rjk@greenend.org.uk>
Sat, 22 Feb 2014 09:11:11 +0000
(09:11 +0000)
committer
Richard Kettlewell
<rjk@greenend.org.uk>
Sat, 22 Feb 2014 09:11:11 +0000
(09:11 +0000)
vbig.1
patch
|
blob
|
history
diff --git
a/vbig.1
b/vbig.1
index feb4192619569ca3cf63d2c3a89b2af8df492100..134caae80b0f4d3831667bb398b56f1f9b715b7d 100644
(file)
--- a/
vbig.1
+++ b/
vbig.1
@@
-38,9
+38,9
@@
the device's size. Ideally, if you have privilege to do so, you
would also specify \fB-f\fR (to flush the operating system disk
cache between the write and read). Also you probably want \fB-p\fR.
.PP
would also specify \fB-f\fR (to flush the operating system disk
cache between the write and read). Also you probably want \fB-p\fR.
.PP
-\f
B
PATH\fR can refer to an ordinary file on a mounted file system,
+\f
I
PATH\fR can refer to an ordinary file on a mounted file system,
which vbig will create or truncate as necessary, or a block device.
which vbig will create or truncate as necessary, or a block device.
-Note that if it
s a file
vbig won't delete it after it's done. Also,
+Note that if it
's a file,
vbig won't delete it after it's done. Also,
be careful when specifying a block device - don't accidentally
overwrite a filesystem you care about! vbig doesn't do sanity checks
and is as dangerous as \fBdd\fR.
be careful when specifying a block device - don't accidentally
overwrite a filesystem you care about! vbig doesn't do sanity checks
and is as dangerous as \fBdd\fR.
@@
-48,7
+48,7
@@
and is as dangerous as \fBdd\fR.
\fISIZE\fR may end with \fBK\fR, \fBM\fR or \fBG\fR to select (binary)
kilobytes, megabytes or gigabytes.
The size is mandatory when creating a file but optional when verifying
\fISIZE\fR may end with \fBK\fR, \fBM\fR or \fBG\fR to select (binary)
kilobytes, megabytes or gigabytes.
The size is mandatory when creating a file but optional when verifying
-it, unless \-\-entire is specified. If \f
B
SIZE\fR not specified when
+it, unless \-\-entire is specified. If \f
I
SIZE\fR not specified when
writing-then-verifying, it is as if \fB\-\-entire\fR was specified.
.PP
If no seed or seed file is specified:
writing-then-verifying, it is as if \fB\-\-entire\fR was specified.
.PP
If no seed or seed file is specified: