summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2006-09-18 16:34:27 +0000
committerPaul Eggert <eggert@cs.ucla.edu>2006-09-18 16:34:27 +0000
commit87353aebd86689802e8dafd195891e88c28ba37c (patch)
tree6ebf28ee19a2a852a463f64f13832d9a380dbd50
parent5a73ad8c6345a1ea096867539461ba949e5491d3 (diff)
downloadcoreutils-87353aebd86689802e8dafd195891e88c28ba37c.tar.xz
* tests/ls/stat-vs-dirent: Fix quoting problem in diagnostic
indicating flaw in kernel. Reword to say that the flaw isn't serious for coreutils, since the flaw does affect ls -i.
-rw-r--r--ChangeLog4
-rwxr-xr-xtests/ls/stat-vs-dirent10
2 files changed, 8 insertions, 6 deletions
diff --git a/ChangeLog b/ChangeLog
index d6d88b4eb..eef235e2f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
2006-09-18 Paul Eggert <eggert@cs.ucla.edu>
+ * tests/ls/stat-vs-dirent: Fix quoting problem in diagnostic
+ indicating flaw in kernel. Reword to say that the flaw isn't
+ serious for coreutils, since the flaw does affect ls -i.
+
* tests/chgrp/basic: Fix bug in test case exposed by building on
Solaris 8 in a setgid directory. The test case incorrectly
assumed that 'symlink' would be in group $g1.
diff --git a/tests/ls/stat-vs-dirent b/tests/ls/stat-vs-dirent
index eab3a69e5..d5d418d65 100755
--- a/tests/ls/stat-vs-dirent
+++ b/tests/ls/stat-vs-dirent
@@ -60,12 +60,10 @@ while :; do
# We know from experience that there may be mismatches on some
# buggy file systems, at mount points.
if test "$d_ino" != "$st_ino"; then
- echo "$0: test failed: $t/$file: d_ino($d_ino) != st_ino($st_ino)" 1>&2
- echo "$0: This may indicate a flaw in your kernel or" \
- "file system implementation." 1>&2
- echo "$0: This flaw won't impact coreutils, but it may well"
- "affect other tools,"
- echo "$0: so you should report it to your operating system vendor." 1>&2
+ echo "$0: test failed: $t/$file: d_ino($d_ino) != st_ino($st_ino)
+ This may indicate a flaw in your kernel or file system implementation.
+ The flaw isn't serious for coreutils, but it might break other tools,
+ so you should report it to your operating system vendor." 1>&2
# This test fails too often, and we don't want to be distracted
# with reports, since the code that could be affected by the losing