summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbescoto <bescoto@2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109>2005-12-27 06:52:36 +0000
committerbescoto <bescoto@2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109>2005-12-27 06:52:36 +0000
commit05d7ac7b430c15676be172e3785bc7156e77274e (patch)
treeeddc17a1e46b754b333d1a55e94018306be61c29
parentd24007f21ffbb76a5a1a8f7acd30c034d5c4d564 (diff)
downloadrdiff-backup-05d7ac7b430c15676be172e3785bc7156e77274e.tar.gz
Removed obsolete mknod bug
git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup/branches/r1-0@725 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109
-rw-r--r--rdiff-backup/rdiff-backup.15
1 files changed, 0 insertions, 5 deletions
diff --git a/rdiff-backup/rdiff-backup.1 b/rdiff-backup/rdiff-backup.1
index 477e3e5..60a71d0 100644
--- a/rdiff-backup/rdiff-backup.1
+++ b/rdiff-backup/rdiff-backup.1
@@ -922,11 +922,6 @@ automatically (as from
or similar) it is probably a good idea to check the exit code.
.SH BUGS
-rdiff-backup uses the shell command
-.BR mknod (1)
-to backup device files (e.g. /dev/ttyS0), so device files won't be
-handled correctly on systems with non-standard mknod syntax.
-.PP
Files whose names are close to the maximum length (e.g. 235 chars if
the maximum is 255) may be skipped because the filenames of related
increment files would be too long.