#, fuzzy msgid "" msgstr "" "Project-Id-Version: man-pages-l10n VERSION\n" "POT-Creation-Date: 2014-07-17 17:57+0900\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. type: TH #: man-pages/man7/symlink.7:37 #, no-wrap msgid "SYMLINK" msgstr "" #. type: TH #: man-pages/man7/symlink.7:37 #, no-wrap msgid "2014-04-06" msgstr "" #. type: TH #: man-pages/man7/symlink.7:37 #, no-wrap msgid "Linux" msgstr "" #. type: TH #: man-pages/man7/symlink.7:37 #, no-wrap msgid "Linux Programmer's Manual" msgstr "" #. type: SH #: man-pages/man7/symlink.7:38 #, no-wrap msgid "NAME" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:40 msgid "symlink - symbolic link handling" msgstr "" #. type: SH #: man-pages/man7/symlink.7:40 #, no-wrap msgid "DESCRIPTION" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:44 msgid "" "Symbolic links are files that act as pointers to other files. To understand " "their behavior, you must first understand how hard links work." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:60 msgid "" "A hard link to a file is indistinguishable from the original file because it " "is a reference to the object underlying the original filename. (To be " "precise: each of the hard links to a file is a reference to the same I, where an i-node number is an index into the i-node table, " "which contains metadata about all files on a filesystem. See B(2).) " "Changes to a file are independent of the name used to reference the file. " "Hard links may not refer to directories (to prevent the possibility of loops " "within the filesystem tree, which would confuse many programs) and may not " "refer to files on different filesystems (because i-node numbers are not " "unique across filesystems)." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:69 msgid "" "A symbolic link is a special type of file whose contents are a string that " "is the pathname of another file, the file to which the link refers. (The " "contents of a symbolic link can be read using B(2).) In other " "words, a symbolic link is a pointer to another name, and not to an " "underlying object. For this reason, symbolic links may refer to directories " "and may cross filesystem boundaries." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:75 msgid "" "There is no requirement that the pathname referred to by a symbolic link " "should exist. A symbolic link that refers to a pathname that does not exist " "is said to be a I." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:87 msgid "" "Because a symbolic link and its referenced object coexist in the filesystem " "name space, confusion can arise in distinguishing between the link itself " "and the referenced object. On historical systems, commands and system calls " "adopted their own link-following conventions in a somewhat ad-hoc fashion. " "Rules for a more uniform approach, as they are implemented on Linux and " "other systems, are outlined here. It is important that site-local " "applications also conform to these rules, so that the user interface can be " "as consistent as possible." msgstr "" #. type: SS #: man-pages/man7/symlink.7:87 #, no-wrap msgid "Symbolic link ownership, permissions, and timestamps" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:95 msgid "" "The owner and group of an existing symbolic link can be changed using " "B(2). The only time that the ownership of a symbolic link matters " "is when the link is being removed or renamed in a directory that has the " "sticky bit set (see B(2))." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:101 msgid "" "The last access and last modification timestamps of a symbolic link can be " "changed using B(2) or B(3)." msgstr "" #. Linux does not currently implement an lchmod(2). #. The #. 4.4BSD #. system differs from historical #. 4BSD #. systems in that the system call #. .BR chown (2) #. has been changed to follow symbolic links. #. The #. .BR lchown (2) #. system call was added later when the limitations of the new #. .BR chown (2) #. became apparent. #. type: Plain text #: man-pages/man7/symlink.7:120 msgid "" "On Linux, the permissions of a symbolic link are not used in any operations; " "the permissions are always 0777 (read, write, and execute for all user " "categories), and can't be changed." msgstr "" #. type: SS #: man-pages/man7/symlink.7:120 #, no-wrap msgid "Obtaining a file descriptor that refers to a symbolic link" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:138 msgid "" "Using the combination of the B and B flags to B(2) " " yields a file descriptor that can be passed as the I argument in " "system calls such as B(2), B(2), B(2), " "B(2), and B(2), in order to operate on the symbolic link " "itself (rather than the file to which it refers)." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:154 msgid "" "By default (i.e., if the B flag is not specified), if " "B(2) is applied to a symbolic link, it yields a handle " "for the symbolic link (rather than the file to which it refers). One can " "then obtain a file descriptor for the symbolic link (rather than the file to " "which it refers) by specifying the B flag in a subsequent call to " "B(2). Again, that file descriptor can be used in the " "aforementioned system calls to operate on the symbolic link itself." msgstr "" #. type: SS #: man-pages/man7/symlink.7:154 #, no-wrap msgid "Handling of symbolic links by system calls and commands" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:169 msgid "" "Symbolic links are handled either by operating on the link itself, or by " "operating on the object referred to by the link. In the latter case, an " "application or system call is said to I the link. Symbolic links " "may refer to other symbolic links, in which case the links are dereferenced " "until an object that is not a symbolic link is found, a symbolic link that " "refers to a file which does not exist is found, or a loop is detected. " "(Loop detection is done by placing an upper limit on the number of links " "that may be followed, and an error results if this limit is exceeded.)" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:172 msgid "" "There are three separate areas that need to be discussed. They are as " "follows:" msgstr "" #. type: IP #: man-pages/man7/symlink.7:172 #, no-wrap msgid "1." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:174 msgid "Symbolic links used as filename arguments for system calls." msgstr "" #. type: IP #: man-pages/man7/symlink.7:174 #, no-wrap msgid "2." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:177 msgid "" "Symbolic links specified as command-line arguments to utilities that are not " "traversing a file tree." msgstr "" #. type: IP #: man-pages/man7/symlink.7:177 #, no-wrap msgid "3." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:181 msgid "" "Symbolic links encountered by utilities that are traversing a file tree " "(either specified on the command line or encountered as part of the file " "hierarchy walk)." msgstr "" #. type: SS #: man-pages/man7/symlink.7:181 #, no-wrap msgid "System calls" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:184 msgid "" "The first area is symbolic links used as filename arguments for system calls." "" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:194 msgid "" "Except as noted below, all system calls follow symbolic links. For example, " "if there were a symbolic link I which pointed to a file named " "I, the system call I would return a file " "descriptor referring to the file I." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:209 msgid "" "Various system calls do not follow links, and operate on the symbolic link " "itself. They are: B(2), B(2), B(2), " "B(2), B(2), B(2), B(2), " "B(2), B(2), and B(2)." msgstr "" #. Maybe one day: .BR fchownat (2) #. type: Plain text #: man-pages/man7/symlink.7:233 msgid "" "Certain other system calls optionally follow symbolic links. They are: " "B(2), B(2), B(2), B(2), " "B(2), B(2), B(2), B(2), " "and B(2); see their manual pages for details. Because " "B(3) is an alias for B(2), that library function also does " "not follow symbolic links. When B(2) is applied to a symbolic link, " "it fails with the error B." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:248 msgid "" "The B(2) warrants special discussion. POSIX.1-2001 specifies that " "B(2) should dereference I if it is a symbolic link. " "However, Linux does not do this. (By default Solaris is the same, but the " "POSIX.1-2001 specified behavior can be obtained with suitable compiler " "options.) The upcoming POSIX.1 revision changes the specification to allow " "either behavior in an implementation." msgstr "" #. type: SS #: man-pages/man7/symlink.7:248 #, no-wrap msgid "Commands not traversing a file tree" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:251 msgid "" "The second area is symbolic links, specified as command-line filename " "arguments, to commands which are not traversing a file tree." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:262 msgid "" "Except as noted below, commands follow symbolic links named as command-line " "arguments. For example, if there were a symbolic link I which " "pointed to a file named I, the command I would display the " "contents of the file I." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:270 msgid "" "It is important to realize that this rule includes commands which may " "optionally traverse file trees; for example, the command I is " "included in this rule, while the command I, which performs " "a tree traversal, is not. (The latter is described in the third area, below." ")" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:288 msgid "" "If it is explicitly intended that the command operate on the symbolic link " "instead of following the symbolic link\\(emfor example, it is desired that " "I change the ownership of the file that I is, whether it " "is a symbolic link or not\\(emthe I<-h> option should be used. In the above " "example, I would change the ownership of the file referred " "to by I, while I would change the ownership of " "I itself." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:290 msgid "There are some exceptions to this rule:" msgstr "" #. type: IP #: man-pages/man7/symlink.7:290 man-pages/man7/symlink.7:300 man-pages/man7/symlink.7:330 man-pages/man7/symlink.7:390 man-pages/man7/symlink.7:419 man-pages/man7/symlink.7:448 man-pages/man7/symlink.7:479 man-pages/man7/symlink.7:492 #, no-wrap msgid "*" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:300 msgid "" "The B(1) and B(1) commands do not follow symbolic links named as " "arguments, but respectively attempt to rename and delete them. (Note, if " "the symbolic link references a file via a relative path, moving it to " "another directory may very well cause it to stop working, since the path may " "no longer be correct.)" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:330 msgid "" "The B(1) command is also an exception to this rule. For compatibility " "with historic systems (when B(1) is not doing a tree walk\\(emthat is, " "I<-R> option is not specified), the B(1) command follows symbolic links " "named as arguments if the I<-H> or I<-L> option is specified, or if the I<-" "F>, I<-d>, or I<-l> options are not specified. (The B(1) command is " "the only command where the I<-H> and I<-L> options affect its behavior even " "though it is not doing a walk of a file tree.)" msgstr "" #. The 4.4BSD system differs from historical 4BSD systems in that the #. .BR chown (1) #. and #. .BR chgrp (1) #. commands follow symbolic links specified on the command line. #. type: Plain text #: man-pages/man7/symlink.7:348 msgid "" "The B(1) command is also an exception to this rule. The B(1) " "command does not follow symbolic links named as argument by default. The " "B(1) command does follow symbolic links named as argument if the I<-" "L> option is specified." msgstr "" #. type: SS #: man-pages/man7/symlink.7:348 #, no-wrap msgid "Commands traversing a file tree" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:361 msgid "" "The following commands either optionally or always traverse file trees: " "B(1), B(1), B(1), B(1), B(1), B(1), " "B(1), B(1), B(1), and B(1)." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:365 msgid "" "It is important to realize that the following rules apply equally to " "symbolic links encountered during the file tree traversal and symbolic links " "listed as command-line arguments." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:370 msgid "" "The I applies to symbolic links that reference files other than " "directories. Operations that apply to symbolic links are performed on the " "links themselves, but otherwise the links are ignored." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:382 msgid "" "The command I will remove I, as well as any " "symbolic links encountered in the tree traversal of I, because " "symbolic links may be removed. In no case will B(1) affect the file " "referred to by I." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:387 msgid "" "The I applies to symbolic links that refer to directories. " "Symbolic links that refer to directories are never followed by default. " "This is often referred to as a \"physical\" walk, as opposed to a " "\"logical\" walk (where symbolic links the refer to directories are " "followed)." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:390 msgid "" "Certain conventions are (should be) followed as consistently as possible by " "commands that perform file tree walks:" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:403 msgid "" "A command can be made to follow any symbolic links named on the command " "line, regardless of the type of file they reference, by specifying the I<-H> " "(for \"half-logical\") flag. This flag is intended to make the command-line " "name space look like the logical name space. (Note, for commands that do " "not always do file tree traversals, the I<-H> flag will be ignored if the I<-" "R> flag is not also specified.)" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:419 msgid "" "For example, the command I will traverse the file " "hierarchy rooted in the file pointed to by I. Note, the I<-H> is not " "the same as the previously discussed I<-h> flag. The I<-H> flag causes " "symbolic links specified on the command line to be dereferenced for the " "purposes of both the action to be performed and the tree walk, and it is as " "if the user had specified the name of the file to which the symbolic link " "pointed." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:433 msgid "" "A command can be made to follow any symbolic links named on the command " "line, as well as any symbolic links encountered during the traversal, " "regardless of the type of file they reference, by specifying the I<-L> (for " "\"logical\") flag. This flag is intended to make the entire name space look " "like the logical name space. (Note, for commands that do not always do file " "tree traversals, the I<-L> flag will be ignored if the I<-R> flag is not " "also specified.)" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:448 msgid "" "For example, the command I will change the owner of " "the file referred to by I. If I refers to a directory, " "B will traverse the file hierarchy rooted in the directory that it " "references. In addition, if any symbolic links are encountered in any file " "tree that B traverses, they will be treated in the same fashion as " "I." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:455 msgid "" "A command can be made to provide the default behavior by specifying the I<-" "P> (for \"physical\") flag. This flag is intended to make the entire name " "space look like the physical name space." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:473 msgid "" "For commands that do not by default do file tree traversals, the I<-H>, I<-" "L>, and I<-P> flags are ignored if the I<-R> flag is not also specified. In " "addition, you may specify the I<-H>, I<-L>, and I<-P> options more than " "once; the last one specified determines the command's behavior. This is " "intended to permit you to alias commands to behave one way or the other, and " "then override that behavior on the command line." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:479 msgid "The B(1) and B(1) commands have exceptions to these rules:" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:492 msgid "" "The B(1) command operates on the symbolic link, and not the file it " "references, and therefore never follows a symbolic link. The B(1) " "command does not support the I<-H>, I<-L>, or I<-P> options." msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:512 msgid "" "To maintain compatibility with historic systems, the B(1) command acts " "a little differently. If you do not specify the I<-F>, I<-d> or I<-l> " "options, B(1) will follow symbolic links specified on the command line. " " If the I<-L> flag is specified, B(1) follows all symbolic links, " "regardless of their type, whether specified on the command line or " "encountered in the tree walk." msgstr "" #. type: SH #: man-pages/man7/symlink.7:512 #, no-wrap msgid "SEE ALSO" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:530 msgid "" "B(1), B(1), B(1), B(1), B(1), B(1), " "B(1), B(2), B(2), B(2), B(2), " "B(2), B(2), B(2), B(2), B(3), " "B(7)" msgstr "" #. type: SH #: man-pages/man7/symlink.7:530 #, no-wrap msgid "COLOPHON" msgstr "" #. type: Plain text #: man-pages/man7/symlink.7:538 msgid "" "This page is part of release 3.70 of the Linux I project. A " "description of the project, information about reporting bugs, and the latest " "version of this page, can be found at \\%http://www.kernel.org/doc/man-pages/" "." msgstr ""