diff options
| author | Jim Meyering <jim@meyering.net> | 2005-06-19 08:34:49 +0000 |
|---|---|---|
| committer | Jim Meyering <jim@meyering.net> | 2005-06-19 08:34:49 +0000 |
| commit | 980b9fc89312060cb834996d2144316fadba2c80 (patch) | |
| tree | a567be099e23152ae84f83dd40c6d35cbb959a2a /src | |
| parent | c6f9b7c7c8a7f7e8a3d4444eba876374ce6a446d (diff) | |
| download | coreutils-980b9fc89312060cb834996d2144316fadba2c80.tar.xz | |
(usage): Use `file system', not `filesystem'.
Diffstat (limited to 'src')
| -rw-r--r-- | src/shred.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/shred.c b/src/shred.c index 90e47d7f0..3348ff4f7 100644 --- a/src/shred.c +++ b/src/shred.c @@ -190,7 +190,7 @@ CAUTION: Note that shred relies on a very important assumption:\n\ that the file system overwrites data in place. This is the traditional\n\ way to do things, but many modern file system designs do not satisfy this\n\ assumption. The following are examples of file systems on which shred is\n\ -not effective, or is not guaranteed to be effective in all filesystem modes:\n\ +not effective, or is not guaranteed to be effective in all file system modes:\n\ \n\ "), stdout); fputs (_("\ @@ -209,7 +209,7 @@ not effective, or is not guaranteed to be effective in all filesystem modes:\n\ \n\ * compressed file systems\n\ \n\ -In the case of ext3 filesystems, the above disclaimer applies\n\ +In the case of ext3 file systems, the above disclaimer applies\n\ (and shred is thus of limited effectiveness) only in data=journal mode,\n\ which journals file data in addition to just metadata. In both the\n\ data=ordered (default) and data=writeback modes, shred works as usual.\n\ |