Fix a bug where dump miscalculates the tape size based on -d/-s

[dump.git] / restore / restore.8.in

diff --git a/restore/restore.8.in b/restore/restore.8.in
index 8426b4659ac64164a3b4e6d29caab2b1ccc4feee..1d9234220e6415a807626bb04c6b719dcefa8e5d 100644 (file)
--- a/restore/restore.8.in
+++ b/restore/restore.8.in
@@ -25,7 +25,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.\"    $Id: restore.8.in,v 1.30 2003/03/30 15:40:39 stelian Exp $
+.\"    $Id: restore.8.in,v 1.32 2004/07/13 08:17:32 stelian Exp $
 .\"
 .TH RESTORE 8 "version __VERSION__ of __DATE__" BSD "System management commands"
 .SH NAME
@@ -102,9 +102,6 @@ restore \- restore files or file systems from backups made with dump
 [\fB\-T \fIdirectory\fR]
 [\fB\-X \fIfilelist\fR]
 [ \fIfile ... \fR]
-.PP
-(The 4.3BSD option syntax is implemented for backward compatibility but is not 
-documented here.)
 .SH DESCRIPTION
 The
 .B restore
@@ -541,6 +538,9 @@ may be an ordinary file or
 .B \-y
 Do not ask the user whether to abort the restore in the event of an error.
 Always try to skip over the bad block(s) and continue.
+.PP
+(The 4.3BSD option syntax is implemented for backward compatibility but is not 
+documented here.)
 .SH DIAGNOSTICS
 Complains if it gets a read error. If 
 .B y
@@ -728,6 +728,16 @@ inode. Although this behaviour is not really a bug, it has proven itself
 to be confusing for many users, so it is recommended to answer 'no', 
 unless you're performing a full restore and you do want to restore the
 permissions on '/'.
+.PP
+It should be underlined that because it runs in user code,
+.B restore
+, when run with the
+.B \-C
+option, sees the files as the kernel presents them, whereas
+.B dump
+sees all the files on a given filesystem. In particular, this 
+can cause some confusion when comparing a dumped filesystem a part
+of which is hidden by a filesystem mounted on top of it.
 .SH AUTHOR
 The
 .B dump/restore