summaryrefslogtreecommitdiffstats
path: root/bin/ln/symlink.7
diff options
context:
space:
mode:
authortrhodes <trhodes@FreeBSD.org>2002-08-21 17:32:44 +0000
committertrhodes <trhodes@FreeBSD.org>2002-08-21 17:32:44 +0000
commit9618da3e35435c433d8086d65af15f716ffe32ec (patch)
tree170fdd70317f0e6648584759afc92e4021ebcd92 /bin/ln/symlink.7
parent34ae8fe5374af25df8e04d804f045ed309399984 (diff)
downloadFreeBSD-src-9618da3e35435c433d8086d65af15f716ffe32ec.zip
FreeBSD-src-9618da3e35435c433d8086d65af15f716ffe32ec.tar.gz
s/filesystem/file system/ as discussed on -developers
Diffstat (limited to 'bin/ln/symlink.7')
-rw-r--r--bin/ln/symlink.76
1 files changed, 3 insertions, 3 deletions
diff --git a/bin/ln/symlink.7 b/bin/ln/symlink.7
index bfc0537..2a0a082 100644
--- a/bin/ln/symlink.7
+++ b/bin/ln/symlink.7
@@ -47,13 +47,13 @@ it is a reference to the object underlying the original file name.
Changes to a file are independent of the name used to reference the
file.
Hard links may not refer to directories and may not reference files
-on different filesystems.
+on different file systems.
A symbolic link contains the name of the file to which it is linked,
i.e. it is a pointer to another name, and not to an underlying object.
For this reason, symbolic links may reference directories and may span
-filesystems.
+file systems.
.Pp
-Because a symbolic link and its referenced object coexist in the filesystem
+Because a symbolic link and its referenced object coexist in the file system
name space, confusion can arise in distinguishing between the link itself
and the referenced object.
Historically, commands and system calls have adopted their own link
OpenPOWER on IntegriCloud