summaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorEric Blake <eblake@redhat.com>2010-03-17 09:31:44 -0600
committerEric Blake <eblake@redhat.com>2010-03-18 15:41:59 -0600
commitda2f6378884b16a19ccf7b75b74ddfe1a2f27f71 (patch)
treee9ab008b28be093a57ede26073835c82b396039f /src
parentcab29edcf1f4f124d92a61e17623d6613487dbe7 (diff)
downloadcoreutils-da2f6378884b16a19ccf7b75b74ddfe1a2f27f71.tar.xz
rm: tweak wording about loss of data warning
* src/rm.c (usage): Update wording to make two points more apparent: undelete is not trivial, and partial recovery should be a consideration factor in deciding whether rm is secure enough. Initially suggested by Reuben Thomas.
Diffstat (limited to 'src')
-rw-r--r--src/rm.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/rm.c b/src/rm.c
index d9a1f8bf6..42f0a5795 100644
--- a/src/rm.c
+++ b/src/rm.c
@@ -176,9 +176,9 @@ use one of these commands:\n\
program_name, program_name);
fputs (_("\
\n\
-Note that if you use rm to remove a file, it is usually possible to recover\n\
-the contents of that file. If you want more assurance that the contents are\n\
-truly unrecoverable, consider using shred.\n\
+Note that if you use rm to remove a file, it might be possible to recover\n\
+some of its contents, given sufficient expertise and/or time. For greater\n\
+assurance that the contents are truly unrecoverable, consider using shred.\n\
"), stdout);
emit_ancillary_info ();
}