msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2012-05-01 04:22+0900\n"
-"PO-Revision-Date: 2012-05-01 05:56+0900\n"
+"PO-Revision-Date: 2012-05-04 05:38+0900\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
#. type: Plain text
#: build/C/man3/fopencookie.3:27
msgid "fopencookie - opening a custom stream"
-msgstr "fopencookie - opening a custom stream"
+msgstr ""
#. type: Plain text
#: build/C/man3/fopencookie.3:34
"() is used to implement B<fmemopen>(3), which provides a stream interface "
"to data that is stored in a buffer in memory."
msgstr ""
-"The B<fopencookie>() function allows the programmer to create a custom "
-"implementation for a standard I/O stream. This implementation can store the "
-"stream's data at a location of its own choosing; for example, B<fopencookie>"
-"() is used to implement B<fmemopen>(3), which provides a stream interface "
-"to data that is stored in a buffer in memory."
#. type: Plain text
#: build/C/man3/fopencookie.3:49
msgid "In order to create a custom stream the programmer must:"
-msgstr "In order to create a custom stream the programmer must:"
+msgstr ""
#. type: IP
#: build/C/man3/fopencookie.3:49 build/C/man3/fopencookie.3:52
"Implement four \"hook\" functions that are used internally by the standard I/"
"O library when performing I/O on the stream."
msgstr ""
-"Implement four \"hook\" functions that are used internally by the standard I/"
-"O library when performing I/O on the stream."
#. type: Plain text
#: build/C/man3/fopencookie.3:63
"()), but automatically supplies the cookie as the first argument when "
"calling the hook functions."
msgstr ""
-"Define a \"cookie\" data type, a structure that provides bookkeeping "
-"information (e.g., where to store data) used by the aforementioned hook "
-"functions. The standard I/O package knows nothing about the contents of "
-"this cookie (thus it is typed as I<void\\ *> when passed to B<fopencookie>"
-"()), but automatically supplies the cookie as the first argument when "
-"calling the hook functions."
#. type: Plain text
#: build/C/man3/fopencookie.3:68
"Call B<fopencookie>() to open a new stream and associate the cookie and "
"hook functions with that stream."
msgstr ""
-"Call B<fopencookie>() to open a new stream and associate the cookie and "
-"hook functions with that stream."
#. type: Plain text
#: build/C/man3/fopencookie.3:76
"opens a new stream and returns a pointer to a I<FILE> object that is used to "
"operate on that stream."
msgstr ""
-"The B<fopencookie>() function serves a purpose similar to B<fopen>(3): it "
-"opens a new stream and returns a pointer to a I<FILE> object that is used to "
-"operate on that stream."
#. type: Plain text
#: build/C/man3/fopencookie.3:83
"argument when the standard I/O library invokes any of the hook functions "
"described below."
msgstr ""
-"The I<cookie> argument is a pointer to the caller's cookie structure that is "
-"to be associated with the new stream. This pointer is supplied as the first "
-"argument when the standard I/O library invokes any of the hook functions "
-"described below."
#. type: Plain text
#: build/C/man3/fopencookie.3:99
"following modes are supported: I<r>, I<w>, I<a>, I<r+>, I<w+>, and I<a+>. "
"See B<fopen>(3) for details."
msgstr ""
-"The I<mode> argument serves the same purpose as for B<fopen>(3). The "
-"following modes are supported: I<r>, I<w>, I<a>, I<r+>, I<w+>, and I<a+>. "
-"See B<fopen>(3) for details."
#. type: Plain text
#: build/C/man3/fopencookie.3:105
"to the programmer-defined hook functions that are used to implement this "
"stream. The structure is defined as follows"
msgstr ""
-"The I<io_funcs> argument is a structure that contains four fields pointing "
-"to the programmer-defined hook functions that are used to implement this "
-"stream. The structure is defined as follows"
#. type: Plain text
#: build/C/man3/fopencookie.3:114
#. type: Plain text
#: build/C/man3/fopencookie.3:118
msgid "The four fields are as follows:"
-msgstr "The four fields are as follows:"
+msgstr ""
#. type: TP
#: build/C/man3/fopencookie.3:118
"This function implements read operations for the stream. When called, it "
"receives three arguments:"
msgstr ""
-"This function implements read operations for the stream. When called, it "
-"receives three arguments:"
#. type: Plain text
#: build/C/man3/fopencookie.3:124
"I<buf>, 0 on end of file, or -1 on error. The I<read> function should "
"update the stream offset appropriately."
msgstr ""
-"The I<buf> and I<size> arguments are, respectively, a buffer into which "
-"input data can be placed and the size of that buffer. As its function "
-"result, the I<read> function should return the number of bytes copied into "
-"I<buf>, 0 on end of file, or -1 on error. The I<read> function should "
-"update the stream offset appropriately."
#. type: Plain text
#: build/C/man3/fopencookie.3:144
"If I<*read> is a NULL pointer, then reads from the custom stream always "
"return end of file."
msgstr ""
-"If I<*read> is a NULL pointer, then reads from the custom stream always "
-"return end of file."
#. type: TP
#: build/C/man3/fopencookie.3:144
"This function implements write operations for the stream. When called, it "
"receives three arguments:"
msgstr ""
-"This function implements write operations for the stream. When called, it "
-"receives three arguments:"
#. type: Plain text
#: build/C/man3/fopencookie.3:150
"or -1 on error. The I<write> function should update the stream offset "
"appropriately."
msgstr ""
-"The I<buf> and I<size> arguments are, respectively, a buffer of data to be "
-"output to the stream and the size of that buffer. As its function result, "
-"the I<write> function should return the number of bytes copied from I<buf>, "
-"or -1 on error. The I<write> function should update the stream offset "
-"appropriately."
#. type: Plain text
#: build/C/man3/fopencookie.3:170
msgid "If I<*write> is a NULL pointer, then output to the stream is discarded."
msgstr ""
-"If I<*write> is a NULL pointer, then output to the stream is discarded."
#. type: TP
#: build/C/man3/fopencookie.3:170
"This function implements seek operations on the stream. When called, it "
"receives three arguments:"
msgstr ""
-"This function implements seek operations on the stream. When called, it "
-"receives three arguments:"
#. type: Plain text
#: build/C/man3/fopencookie.3:176
"The I<*offset> argument specifies the new file offset depending on which of "
"the following three values is supplied in I<whence>:"
msgstr ""
-"The I<*offset> argument specifies the new file offset depending on which of "
-"the following three values is supplied in I<whence>:"
#. type: TP
#: build/C/man3/fopencookie.3:183 build/C/man2/lseek.2:65
"The stream offset should be set I<*offset> bytes from the start of the "
"stream."
msgstr ""
-"The stream offset should be set I<*offset> bytes from the start of the "
-"stream."
#. type: TP
#: build/C/man3/fopencookie.3:188 build/C/man2/lseek.2:70
#. type: Plain text
#: build/C/man3/fopencookie.3:192
msgid "I<*offset> should be added to the current stream offset."
-msgstr "I<*offset> should be added to the current stream offset."
+msgstr ""
#. type: TP
#: build/C/man3/fopencookie.3:192 build/C/man2/lseek.2:75
msgid ""
"The stream offset should be set to the size of the stream plus I<*offset>."
msgstr ""
-"The stream offset should be set to the size of the stream plus I<*offset>."
#. type: Plain text
#: build/C/man3/fopencookie.3:203
"Before returning, the I<seek> function should update I<*offset> to indicate "
"the new stream offset."
msgstr ""
-"Before returning, the I<seek> function should update I<*offset> to indicate "
-"the new stream offset."
#. type: Plain text
#: build/C/man3/fopencookie.3:207
"As its function result, the I<seek> function should return 0 on success, and "
"-1 on error."
msgstr ""
-"As its function result, the I<seek> function should return 0 on success, and "
-"-1 on error."
#. type: Plain text
#: build/C/man3/fopencookie.3:212
"If I<*seek> is a NULL pointer, then it is not possible to perform seek "
"operations on the stream."
msgstr ""
-"If I<*seek> is a NULL pointer, then it is not possible to perform seek "
-"operations on the stream."
#. type: TP
#: build/C/man3/fopencookie.3:212
"freeing buffers allocated for the stream. When called, it receives one "
"argument:"
msgstr ""
-"This function closes the stream. The hook function can do things such as "
-"freeing buffers allocated for the stream. When called, it receives one "
-"argument:"
#. type: Plain text
#: build/C/man3/fopencookie.3:220
"The I<cookie> argument is the cookie that the programmer supplied when "
"calling B<fopencookie>()."
msgstr ""
-"The I<cookie> argument is the cookie that the programmer supplied when "
-"calling B<fopencookie>()."
#. type: Plain text
#: build/C/man3/fopencookie.3:231
"As its function result, the I<close> function should return 0 on success, "
"and B<EOF> on error."
msgstr ""
-"As its function result, the I<close> function should return 0 on success, "
-"and B<EOF> on error."
#. type: Plain text
#: build/C/man3/fopencookie.3:235
"If I<*close> is NULL, then no special action is performed when the stream is "
"closed."
msgstr ""
-"If I<*close> is NULL, then no special action is performed when the stream is "
-"closed."
#. .SH ERRORS
#. It's not clear if errno ever gets set...
"On success B<fopencookie>() returns a pointer to the new stream. On error, "
"NULL is returned."
msgstr ""
-"On success B<fopencookie>() returns a pointer to the new stream. On error, "
-"NULL is returned."
#. type: Plain text
#: build/C/man3/fopencookie.3:244
msgid "This function is a nonstandard GNU extension."
-msgstr "This function is a nonstandard GNU extension."
+msgstr ""
#. type: Plain text
#: build/C/man3/fopencookie.3:253
"reading two out of every five characters and writing them to standard "
"output. The following shell session demonstrates the use of the program:"
msgstr ""
-"The program below implements a custom stream whose functionality is similar "
-"(but not identical) to that available via B<fmemopen>(3). It implements a "
-"stream whose data is stored in a memory buffer. The program writes its "
-"command-line arguments to the stream, and then seeks through the stream "
-"reading two out of every five characters and writing them to standard "
-"output. The following shell session demonstrates the use of the program:"
#. type: Plain text
#: build/C/man3/fopencookie.3:261
"cookie that already has an open stream; closing a stream that has already "
"been closed)."
msgstr ""
-"Note that a more general version of the program below could be improved to "
-"more robustly handle various error situations (e.g., opening a stream with a "
-"cookie that already has an open stream; closing a stream that has already "
-"been closed)."
#. type: Plain text
#: build/C/man3/fopencookie.3:277
#. type: Plain text
#: build/C/man7/symlink.7:38
msgid "symlink - symbolic link handling"
-msgstr "symlink - symbolic link handling"
+msgstr ""
#. type: SH
#: build/C/man7/symlink.7:38
#, no-wrap
msgid "SYMBOLIC LINK HANDLING"
-msgstr "SYMBOLIC LINK HANDLING"
+msgstr ""
#. type: Plain text
#: build/C/man7/symlink.7:42
"Symbolic links are files that act as pointers to other files. To understand "
"their behavior, you must first understand how hard links work."
msgstr ""
-"Symbolic links are files that act as pointers to other files. To understand "
-"their behavior, you must first understand how hard links work."
#. type: Plain text
#: build/C/man7/symlink.7:58
"refer to files on different file systems (because i-node numbers are not "
"unique across file systems)."
msgstr ""
-"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<i-"
-"node number>, where an i-node number is an index into the i-node table, "
-"which contains metadata about all files on a file system. See B<stat>(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 file system tree, which would confuse many programs) and may not "
-"refer to files on different file systems (because i-node numbers are not "
-"unique across file systems)."
#. type: Plain text
#: build/C/man7/symlink.7:65
"underlying object. For this reason, symbolic links may refer to directories "
"and may cross file system boundaries."
msgstr ""
-"A symbolic link is a special type of file whose contents are a string that "
-"is the pathname another file, the file to which the link refers. 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 file system boundaries."
#. type: Plain text
#: build/C/man7/symlink.7:71
"should exist. A symbolic link that refers to a pathname that does not exist "
"is said to be a I<dangling link>."
msgstr ""
-"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<dangling link>."
#. type: Plain text
#: build/C/man7/symlink.7:83
"applications also conform to these rules, so that the user interface can be "
"as consistent as possible."
msgstr ""
-"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. 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."
#. type: SS
#: build/C/man7/symlink.7:83
#, no-wrap
msgid "Symbolic link ownership, permissions, and timestamps"
-msgstr "Symbolic link ownership, permissions, and timestamps"
+msgstr ""
#. type: Plain text
#: build/C/man7/symlink.7:91
"is when the link is being removed or renamed in a directory that has the "
"sticky bit set (see B<stat>(2))."
msgstr ""
-"The owner and group of an existing symbolic link can be changed using "
-"B<lchown>(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<stat>(2))."
#. type: Plain text
#: build/C/man7/symlink.7:97
"The last access and last modification timestamps of a symbolic link can be "
"changed using B<utimensat>(2) or B<lutimes>(3)."
msgstr ""
-"The last access and last modification timestamps of a symbolic link can be "
-"changed using B<utimensat>(2) or B<lutimes>(3)."
#. Linux does not currently implement an lchmod(2).
#. The
"the permissions are always 0777 (read, write, and execute for all user "
"categories), and can't be changed."
msgstr ""
-"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."
#. type: SS
#: build/C/man7/symlink.7:116
#, no-wrap
msgid "Handling of symbolic links by system calls and commands"
-msgstr "Handling of symbolic links by system calls and commands"
+msgstr ""
#. type: Plain text
#: build/C/man7/symlink.7:131
"(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 ""
-"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<follow> 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.)"
#. type: Plain text
#: build/C/man7/symlink.7:134
"There are three separate areas that need to be discussed. They are as "
"follows:"
msgstr ""
-"There are three separate areas that need to be discussed. They are as "
-"follows:"
#. type: IP
#: build/C/man7/symlink.7:134
#. type: Plain text
#: build/C/man7/symlink.7:136
msgid "Symbolic links used as filename arguments for system calls."
-msgstr "Symbolic links used as filename arguments for system calls."
+msgstr ""
#. type: IP
#: build/C/man7/symlink.7:136
"Symbolic links specified as command-line arguments to utilities that are not "
"traversing a file tree."
msgstr ""
-"Symbolic links specified as command-line arguments to utilities that are not "
-"traversing a file tree."
#. type: IP
#: build/C/man7/symlink.7:139
"(either specified on the command line or encountered as part of the file "
"hierarchy walk)."
msgstr ""
-"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)."
#. type: SS
#: build/C/man7/symlink.7:143
#, no-wrap
msgid "System calls"
-msgstr "System calls"
+msgstr ""
#. type: Plain text
#: build/C/man7/symlink.7:146
msgid ""
"The first area is symbolic links used as filename arguments for system calls."
msgstr ""
-"The first area is symbolic links used as filename arguments for system calls."
#. type: Plain text
#: build/C/man7/symlink.7:156
"I<afile>, the system call I<open(\"slink\" ...\\&)> would return a file "
"descriptor referring to the file I<afile>."
msgstr ""
-"Except as noted below, all system calls follow symbolic links. For example, "
-"if there were a symbolic link I<slink> which pointed to a file named "
-"I<afile>, the system call I<open(\"slink\" ...\\&)> would return a file "
-"descriptor referring to the file I<afile>."
#. Maybe one day: .BR fchownat (2)
#. type: Plain text
"compiler options.) The upcoming POSIX.1 revision changes the specification "
"to allow either behavior in an implementation."
msgstr ""
-"Various system calls do not follow links, and operate on the symbolic link "
-"itself. They are: B<lchown>(2), B<lgetxattr>(2), B<llistxattr>(2), "
-"B<lremovexattr>(2), B<lsetxattr>(2), B<lstat>(2), B<readlink>(2), B<rename>"
-"(2), B<rmdir>(2), and B<unlink>(2). Certain other system calls optionally "
-"follow symbolic links. They are: B<faccessat>(2), B<fchownat>(2), B<fstatat>"
-"(2), B<linkat>(2), B<open>(2), B<openat>(2), and B<utimensat>(2); see their "
-"manual pages for details. Because B<remove>(3) is an alias for B<unlink>"
-"(2), that library function also does not follow symbolic links. When "
-"B<rmdir>(2) is applied to a symbolic link, it fails with the error "
-"B<ENOTDIR>. The B<link>(2) warrants special discussion. POSIX.1-2001 "
-"specifies that B<link>(2) should dereference I<oldpath> 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."
#. type: SS
#: build/C/man7/symlink.7:206
#, no-wrap
msgid "Commands not traversing a file tree"
-msgstr "Commands not traversing a file tree"
+msgstr ""
#. type: Plain text
#: build/C/man7/symlink.7:209
"The second area is symbolic links, specified as command-line filename "
"arguments, to commands which are not traversing a file tree."
msgstr ""
-"The second area is symbolic links, specified as command-line filename "
-"arguments, to commands which are not traversing a file tree."
#. type: Plain text
#: build/C/man7/symlink.7:220
"pointed to a file named I<afile>, the command I<cat slink> would display the "
"contents of the file I<afile>."
msgstr ""
-"Except as noted below, commands follow symbolic links named as command-line "
-"arguments. For example, if there were a symbolic link I<slink> which "
-"pointed to a file named I<afile>, the command I<cat slink> would display the "
-"contents of the file I<afile>."
#. type: Plain text
#: build/C/man7/symlink.7:228
"in this rule, while the command I<chown\\ -R file>, which performs a tree "
"traversal, is not. (The latter is described in the third area, below.)"
msgstr ""
-"It is important to realize that this rule includes commands which may "
-"optionally traverse file trees, e.g., the command I<chown file> is included "
-"in this rule, while the command I<chown\\ -R file>, which performs a tree "
-"traversal, is not. (The latter is described in the third area, below.)"
#. type: Plain text
#: build/C/man7/symlink.7:246
"to by I<slink>, while I<chown\\ -h root slink> would change the ownership of "
"I<slink> itself."
msgstr ""
-"If it is explicitly intended that the command operate on the symbolic link "
-"instead of following the symbolic link, e.g., it is desired that I<chown "
-"slink> change the ownership of the file that I<slink> is, whether it is a "
-"symbolic link or not, the I<-h> option should be used. In the above "
-"example, I<chown root slink> would change the ownership of the file referred "
-"to by I<slink>, while I<chown\\ -h root slink> would change the ownership of "
-"I<slink> itself."
#. type: Plain text
#: build/C/man7/symlink.7:248
msgid "There are some exceptions to this rule:"
-msgstr "There are some exceptions to this rule:"
+msgstr ""
#. type: Plain text
#: build/C/man7/symlink.7:258
"another directory may very well cause it to stop working, since the path may "
"no longer be correct.)"
msgstr ""
-"The B<mv>(1) and B<rm>(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.)"
#. type: Plain text
#: build/C/man7/symlink.7:288
"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 B<ls>(1) command is also an exception to this rule. For compatibility "
-"with historic systems (when B<ls>(1) is not doing a tree walk, i.e., the I<-"
-"R> option is not specified), the B<ls>(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<ls>(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.)"
#. The 4.4BSD system differs from historical 4BSD systems in that the
#. .BR chown (1)
"B<file>(1) command does follow symbolic links named as argument if the I<-"
"L> option is specified."
msgstr ""
-"The B<file>(1) command is also an exception to this rule. The B<file>(1) "
-"command does not follow symbolic links named as argument by default. The "
-"B<file>(1) command does follow symbolic links named as argument if the I<-"
-"L> option is specified."
#. type: SS
#: build/C/man7/symlink.7:306
#, no-wrap
msgid "Commands traversing a file tree"
-msgstr "Commands traversing a file tree"
+msgstr ""
#. type: Plain text
#: build/C/man7/symlink.7:319
"B<chgrp>(1), B<chmod>(1), B<chown>(1), B<cp>(1), B<du>(1), B<find>(1), B<ls>"
"(1), B<pax>(1), B<rm>(1), and B<tar>(1)."
msgstr ""
-"The following commands either optionally or always traverse file trees: "
-"B<chgrp>(1), B<chmod>(1), B<chown>(1), B<cp>(1), B<du>(1), B<find>(1), B<ls>"
-"(1), B<pax>(1), B<rm>(1), and B<tar>(1)."
#. type: Plain text
#: build/C/man7/symlink.7:323
"symbolic links encountered during the file tree traversal and symbolic links "
"listed as command-line arguments."
msgstr ""
-"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."
#. type: Plain text
#: build/C/man7/symlink.7:328
"directories. Operations that apply to symbolic links are performed on the "
"links themselves, but otherwise the links are ignored."
msgstr ""
-"The I<first rule> 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."
#. type: Plain text
#: build/C/man7/symlink.7:340
"symbolic links may be removed. In no case will B<rm>(1) affect the file "
"referred to by I<slink>."
msgstr ""
-"The command I<rm\\ -r slink directory> will remove I<slink>, as well as any "
-"symbolic links encountered in the tree traversal of I<directory>, because "
-"symbolic links may be removed. In no case will B<rm>(1) affect the file "
-"referred to by I<slink>."
#. type: Plain text
#: build/C/man7/symlink.7:345
"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 ""
-"The I<second rule> 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)."
#. type: Plain text
#: build/C/man7/symlink.7:348
"Certain conventions are (should be) followed as consistently as possible by "
"commands that perform file tree walks:"
msgstr ""
-"Certain conventions are (should be) followed as consistently as possible by "
-"commands that perform file tree walks:"
#. type: Plain text
#: build/C/man7/symlink.7:361
"not always do file tree traversals, the I<-H> flag will be ignored if the I<-"
"R> flag is not also specified.)"
msgstr ""
-"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.)"
#. type: Plain text
#: build/C/man7/symlink.7:377
"if the user had specified the name of the file to which the symbolic link "
"pointed."
msgstr ""
-"For example, the command I<chown\\ -HR user slink> will traverse the file "
-"hierarchy rooted in the file pointed to by I<slink>. 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."
#. type: Plain text
#: build/C/man7/symlink.7:391
"tree traversals, the I<-L> flag will be ignored if the I<-R> flag is not "
"also specified.)"
msgstr ""
-"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.)"
#. type: Plain text
#: build/C/man7/symlink.7:406
"tree that B<chown> traverses, they will be treated in the same fashion as "
"I<slink>."
msgstr ""
-"For example, the command I<chown\\ -LR user slink> will change the owner of "
-"the file referred to by I<slink>. If I<slink> refers to a directory, "
-"B<chown> 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<chown> traverses, they will be treated in the same fashion as "
-"I<slink>."
#. type: Plain text
#: build/C/man7/symlink.7:413
"P> (for \"physical\") flag. This flag is intended to make the entire name "
"space look like the physical name space."
msgstr ""
-"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."
#. type: Plain text
#: build/C/man7/symlink.7:431
"intended to permit you to alias commands to behave one way or the other, and "
"then override that behavior on the command line."
msgstr ""
-"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."
#. type: Plain text
#: build/C/man7/symlink.7:437
msgid "The B<ls>(1) and B<rm>(1) commands have exceptions to these rules:"
-msgstr "The B<ls>(1) and B<rm>(1) commands have exceptions to these rules:"
+msgstr ""
#. type: Plain text
#: build/C/man7/symlink.7:450
"references, and therefore never follows a symbolic link. The B<rm>(1) "
"command does not support the I<-H>, I<-L>, or I<-P> options."
msgstr ""
-"The B<rm>(1) command operates on the symbolic link, and not the file it "
-"references, and therefore never follows a symbolic link. The B<rm>(1) "
-"command does not support the I<-H>, I<-L>, or I<-P> options."
#. type: Plain text
#: build/C/man7/symlink.7:470
"regardless of their type, whether specified on the command line or "
"encountered in the tree walk."
msgstr ""
-"To maintain compatibility with historic systems, the B<ls>(1) command acts "
-"a little differently. If you do not specify the I<-F>, I<-d> or I<-l> "
-"options, B<ls>(1) will follow symbolic links specified on the command "
-"line. If the I<-L> flag is specified, B<ls>(1) follows all symbolic links, "
-"regardless of their type, whether specified on the command line or "
-"encountered in the tree walk."
#. type: Plain text
#: build/C/man7/symlink.7:488
"B<symlink>(2), B<unlink>(2), B<utimensat>(2), B<lutimes>(3), "
"B<path_resolution>(7)"
msgstr ""
-"B<chgrp>(1), B<chmod>(1), B<find>(1), B<ln>(1), B<ls>(1), B<mv>(1), B<rm>"
-"(1), B<lchown>(2), B<link>(2), B<lstat>(2), B<readlink>(2), B<rename>(2), "
-"B<symlink>(2), B<unlink>(2), B<utimensat>(2), B<lutimes>(3), "
-"B<path_resolution>(7)"
+"B<chgrp>(1), B<chmod>(1), B<find>(1), B<ln>(1), B<ls>(1), B<mv>(1),\n"
+"B<rm>(1), B<lchown>(2), B<link>(2), B<lstat>(2), B<readlink>(2),\n"
+"B<rename>(2), B<symlink>(2), B<unlink>(2), B<utimensat>(2),\n"
+"B<lutimes>(3), B<path_resolution>(7)"
#. type: TH
#: build/C/man3/tempnam.3:23
OSDN Git Service
