diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2013-02-24 19:02:18 +0100 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2013-02-24 19:02:18 +0100 |
| commit | 73d8cece72d29f0719459d6a6a0946b91d5368a2 (patch) | |
| tree | 0c21299f7aaca0163f747997957bd05cad25bd41 /man7/path_resolution.7 | |
| parent | 47297adb6e8cc25a8bc44b5dab2bdf65a9176287 (diff) | |
| download | man-pages-73d8cece72d29f0719459d6a6a0946b91d5368a2.tar.gz | |
intro.1, time.1, _syscall.2, accept.2, capget.2, clone.2, execve.2, fcntl.2, intro.2, ioctl_list.2, ioprio_set.2, kill.2, mlock.2, nanosleep.2, perf_event_open.2, select.2, stat.2, times.2, ustat.2, vfork.2, wait.2, cfree.3, dbopen.3, dlopen.3, fenv.3, fmtmsg.3, gamma.3, getaddrinfo.3, gethostbyname.3, getnameinfo.3, getspnam.3, login.3, printf.3, regex.3, stdio.3, sysconf.3, termios.3, ttyslot.3, undocumented.3, wordexp.3, console_codes.4, initrd.4, mouse.4, random.4, st.4, tty_ioctl.4, wavelan.4, charmap.5, dir_colors.5, hosts.5, termcap.5, armscii-8.7, boot.7, bootparam.7, capabilities.7, charsets.7, ddp.7, futex.7, glob.7, ipv6.7, iso_8859-1.7, iso_8859-10.7, iso_8859-11.7, iso_8859-13.7, iso_8859-14.7, iso_8859-15.7, iso_8859-16.7, iso_8859-2.7, iso_8859-3.7, iso_8859-4.7, iso_8859-5.7, iso_8859-6.7, iso_8859-7.7, iso_8859-8.7, iso_8859-9.7, koi8-r.7, koi8-u.7, man.7, numa.7, path_resolution.7, pipe.7, posixoptions.7, pthreads.7, pty.7, rtnetlink.7, signal.7, time.7, udp.7, udplite.7, unicode.7, uri.7, utf-8.7: G;lobal fix: remove unneeded double quotes in .SS headings
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man7/path_resolution.7')
| -rw-r--r-- | man7/path_resolution.7 | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/man7/path_resolution.7 b/man7/path_resolution.7 index 2b67ef6fdf..934b8c47b0 100644 --- a/man7/path_resolution.7 +++ b/man7/path_resolution.7 @@ -26,7 +26,7 @@ path_resolution \- how a pathname is resolved to a file .SH DESCRIPTION Some UNIX/Linux system calls have as parameter one or more filenames. A filename (or pathname) is resolved as follows. -.SS "Step 1: start of the resolution process" +.SS Step 1: start of the resolution process If the pathname starts with the \(aq/\(aq character, the starting lookup directory is the root directory of the calling process. @@ -56,7 +56,7 @@ system call.) Pathnames starting with a \(aq/\(aq character are called absolute pathnames. Pathnames not starting with a \(aq/\(aq are called relative pathnames. -.SS "Step 2: walk along the path" +.SS Step 2: walk along the path Set the current lookup directory to the starting lookup directory. Now, for each nonfinal component of the pathname, where a component is a substring delimited by \(aq/\(aq characters, this component is looked up @@ -105,7 +105,7 @@ exceeded ("Too many levels of symbolic links"). .\" presently: max recursion depth during symlink resolution: 5 .\" max total number of symbolic links followed: 40 .\" _POSIX_SYMLOOP_MAX is 8 -.SS "Step 3: find the final entry" +.SS Step 3: find the final entry The lookup of the final component of the pathname goes just like that of all other components, as described in the previous step, with two differences: (i) the final component need not be a @@ -117,7 +117,7 @@ we are just creating it. The details on the treatment of the final entry are described in the manual pages of the specific system calls. -.SS ". and .." +.SS . and .. By convention, every directory has the entries "." and "..", which refer to the directory itself and to its parent directory, respectively. @@ -127,7 +127,7 @@ their conventional meanings, regardless of whether they are actually present in the physical file system. One cannot walk down past the root: "/.." is the same as "/". -.SS "Mount points" +.SS Mount points After a "mount dev path" command, the pathname "path" refers to the root of the file system hierarchy on the device "dev", and no longer to whatever it referred to earlier. @@ -135,13 +135,13 @@ longer to whatever it referred to earlier. One can walk out of a mounted file system: "path/.." refers to the parent directory of "path", outside of the file system hierarchy on "dev". -.SS "Trailing slashes" +.SS Trailing slashes If a pathname ends in a \(aq/\(aq, that forces resolution of the preceding component as in Step 2: it has to exist and resolve to a directory. Otherwise a trailing \(aq/\(aq is ignored. (Or, equivalently, a pathname with a trailing \(aq/\(aq is equivalent to the pathname obtained by appending \(aq.\(aq to it.) -.SS "Final symlink" +.SS Final symlink If the last component of a pathname is a symbolic link, then it depends on the system call whether the file referred to will be the symbolic link or the result of path resolution on its contents. @@ -150,21 +150,21 @@ For example, the system call will operate on the symlink, while .BR stat (2) operates on the file pointed to by the symlink. -.SS "Length limit" +.SS Length limit There is a maximum length for pathnames. If the pathname (or some intermediate pathname obtained while resolving symbolic links) is too long, an .B ENAMETOOLONG error is returned ("Filename too long"). -.SS "Empty pathname" +.SS Empty pathname In the original UNIX, the empty pathname referred to the current directory. Nowadays POSIX decrees that an empty pathname must not be resolved successfully. Linux returns .B ENOENT in this case. -.SS "Permissions" +.SS Permissions The permission bits of a file consist of three groups of three bits, cf.\& .BR chmod (1) and @@ -200,7 +200,7 @@ instead of the effective group ID. See .BR setfsgid (2). .\" FIXME say something about file system mounted read-only ? -.SS "Bypassing permission checks: superuser and capabilities" +.SS Bypassing permission checks: superuser and capabilities On a traditional UNIX system, the superuser .RI ( root , user ID 0) is all-powerful, and bypasses all permissions restrictions |