diff options
author | trhodes <trhodes@FreeBSD.org> | 2002-05-16 01:57:20 +0000 |
---|---|---|
committer | trhodes <trhodes@FreeBSD.org> | 2002-05-16 01:57:20 +0000 |
commit | 56036d26233ff609be6306f948bdbebc57075335 (patch) | |
tree | a6535f7145cab2b794accc91e7549be9d65f90f6 /bin/pax/pat_rep.c | |
parent | 24cc1f8e45f072238cecb4ba927e38f90d1627f5 (diff) | |
download | FreeBSD-src-56036d26233ff609be6306f948bdbebc57075335.zip FreeBSD-src-56036d26233ff609be6306f948bdbebc57075335.tar.gz |
Consistancy check s/file system/filesystem/
Reviewed by: brian
Diffstat (limited to 'bin/pax/pat_rep.c')
-rw-r--r-- | bin/pax/pat_rep.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bin/pax/pat_rep.c b/bin/pax/pat_rep.c index 0f09b99..b4998ed 100644 --- a/bin/pax/pat_rep.c +++ b/bin/pax/pat_rep.c @@ -655,7 +655,7 @@ mod_name(ARCHD *arcn) * anyway). But there are no such requirements for symlinks. On one * hand the symlink that refers to a file in the archive will have to * be modified to so it will still work at its new location in the - * file system. On the other hand a symlink that points elsewhere (and + * filesystem. On the other hand a symlink that points elsewhere (and * should continue to do so) should not be modified. There is clearly * no perfect solution here. So we handle them like hardlinks. Clearly * a replacement made by the interactive rename mapping is very likely |