(split) Import translated manuals from JM CVS Repository.

[linuxjm/LDP_man-pages.git] / draft / man7 / man-pages.7

.\" (C) Copyright 1992-1999 Rickard E. Faith and David A. Wheeler
.\" (faith@cs.unc.edu and dwheeler@ida.org)
.\" and (C) Copyright 2007 Michael Kerrisk <mtk.manpages@gmail.com>
.\"
.\" Permission is granted to make and distribute verbatim copies of this
.\" manual provided the copyright notice and this permission notice are
.\" preserved on all copies.
.\"
.\" Permission is granted to copy and distribute modified versions of this
.\" manual under the conditions for verbatim copying, provided that the
.\" entire resulting derived work is distributed under the terms of a
.\" permission notice identical to this one.
.\"
.\" Since the Linux kernel and libraries are constantly changing, this
.\" manual page may be incorrect or out-of-date.  The author(s) assume no
.\" responsibility for errors or omissions, or for damages resulting from
.\" the use of the information contained herein.  The author(s) may not
.\" have taken the same level of care in the production of this manual,
.\" which is licensed free of charge, as they might when working
.\" professionally.
.\"
.\" Formatted or processed versions of this manual, if unaccompanied by
.\" the source, must acknowledge the copyright and authors of this work.
.\"
.\" 2007-05-30 created by mtk, using text from old man.7 plus
.\" rewrites and additional text.
.\"
.\" Japanese Version Copyright (c) 2007  Akihiro MOTOKI
.\"         all rights reserved.
.\" Translated 2007-06-13, Akihiro MOTOKI <amotoki@dd.iij4u.or.jp>, LDP v2.54
.\" Updated 2007-07-04, Akihiro MOTOKI <amotoki@dd.iij4u.or.jp>, LDP v2.59
.\" Updated 2007-09-03, Akihiro MOTOKI <amotoki@dd.iij4u.or.jp>, LDP v2.64
.\" Updated 2008-08-09, Akihiro MOTOKI <amotoki@dd.iij4u.or.jp>, LDP v3.05
.\" 
.TH MAN-PAGES 7 2008-10-28 "Linux" "Linux Programmer's Manual"
.\"O .SH NAME
.SH ̾Á°
.\"O man-pages \- conventions for writing Linux man pages
man-pages \- Linux ¤Î man ¥Ú¡¼¥¸¤ò½ñ¤¯ºÝ¤Î·è¤Þ¤ê»ö
.\"O .SH SYNOPSIS
.SH ½ñ¼°
.B man
.RI [ section ]
.I title
.\"O .SH DESCRIPTION
.SH ÀâÌÀ
.\"O This page describes the conventions that should be employed
.\"O when writing man pages for the Linux \fIman-pages\fP project,
.\"O which comprises Sections 2, 3, 4, 5, and 7 of the Linux manual pages.
.\"O The conventions described on this page may also be useful
.\"O for authors writing man pages for other projects.
¤³¤Î¥Ú¡¼¥¸¤Ç¤Ï¡¢
Linux \fIman-pages\fP ¥×¥í¥¸¥§¥¯¥È¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò½ñ¤¯ºÝ¤Ë
½¾¤¦¤Ù¤­·è¤Þ¤ê»ö¤Ë¤Ä¤¤¤ÆÀâÌÀ¤¹¤ë¡£
Linux \fIman-pages\fP ¤Ï Linux ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Î
¥»¥¯¥·¥ç¥ó 2, 3, 4, 5, 7 ¤«¤é¹½À®¤µ¤ì¤Æ¤¤¤ë¡£
¤³¤Î¥Ú¡¼¥¸¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ë·è¤Þ¤ê»ö¤Ï¡¢Â¾¤Î¥×¥í¥¸¥§¥¯¥È¤Î
¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò½ñ¤¯ºî¼Ô¤Ë¤âÌòΩ¤Ä¤³¤È¤À¤í¤¦¡£
.\"O .SS Sections of the Manual Pages
.SS ¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Î¥»¥¯¥·¥ç¥ó
.PP
.\"O The manual Sections are traditionally defined as follows:
¥Þ¥Ë¥å¥¢¥ë¤Î¥»¥¯¥·¥ç¥ó¤Ï¡¢½¬´·Åª¤Ë°Ê²¼¤Î¤è¤¦¤ÊÄêµÁ¤¬ÍѤ¤¤é¤ì¤Æ¤¤¤ë:
.TP 10
.\"O .B 1 Commands (Programs)
.\"O Those commands that can be executed by the user from within
.\"O a shell.
.B 1 ¥³¥Þ¥ó¥É (¥×¥í¥°¥é¥à)
¥·¥§¥ë¤ÎÃ椫¤é¥æ¡¼¥¶¤¬¼Â¹Ô¤Ç¤­¤ë¥³¥Þ¥ó¥É¡£
.TP
.\"O .B 2 System calls
.\"O Those functions which must be performed by the kernel.
.B 2 ¥·¥¹¥Æ¥à¥³¡¼¥ë
¥«¡¼¥Í¥ë¤¬½èÍý¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤´Ø¿ô¡£
.TP
.\"O .B 3 Library calls
.\"O Most of the
.\"O .I libc
.\"O functions.
.B 3 ¥é¥¤¥Ö¥é¥ê¥³¡¼¥ë
.I libc
¤Î´Ø¿ô¤ÎÂçÉôʬ¡£
.TP
.\"O .B 4 Special files (devices)
.\"O Files found in
.\"O .IR /dev .
.B 4 ¥¹¥Ú¥·¥ã¥ë¥Õ¥¡¥¤¥ë (¥Ç¥Ð¥¤¥¹)
.I /dev
°Ê²¼¤Ë¤¢¤ë¥Õ¥¡¥¤¥ë¡£
.TP
.\"O .B 5 File formats and conventions
.\"O The format for
.\"O .I /etc/passwd
.\"O and other human-readable files.
.B 5 ¥Õ¥¡¥¤¥ë¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤Èµ¬Ìó
.I /etc/passwd
¤Ê¤É¤Î¿Í¤¬Æɤá¤ë¥Õ¥¡¥¤¥ë¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¡£
.TP
.\"O .B 6 Games
.B 6 ¥²¡¼¥à
.TP
.\"O .B 7 Conventions and miscellaneous
.\"O Overviews of various topics, conventions and protocols,
.\"O character set standards, and miscellaneous other things.
.B 7 Ìó«»ö¤½¤Î¾
ÍÍ¡¹¤Ê»öÊÁ¤Î³µÍס¢´·½¬¡¢¥×¥í¥È¥³¥ë¡¢Ê¸»ú½¸¹ç¤Îµ¬³Ê¡¢¤½¤Î¾»¨Â¿¤Ê¤³¤È¡£
.TP
.\"O .B 8 System management commands
.\"O Commands like
.\"O .BR mount (8),
.\"O many of which only root can execute.
.B 8 ¥·¥¹¥Æ¥à´ÉÍý¥³¥Þ¥ó¥É
.BR mount (8)
¤Î¤è¤¦¤Ê root ¤Î¤ß¤¬¼Â¹Ô²Äǽ¤Ê¥³¥Þ¥ó¥É¡£
.\" .TP
.\"O .\" .B 9 Kernel routines
.\"O .\" This is an obsolete manual section.
.\"O .\" Once it was thought a good idea to document the Linux kernel here,
.\"O .\" but in fact very little has been documented, and the documentation
.\"O .\" that exists is outdated already.
.\"O .\" There are better sources of
.\"O .\" information for kernel developers.
.\" .B 9 ¥«¡¼¥Í¥ë¥ë¡¼¥Á¥ó
.\" ¤³¤Î¥Þ¥Ë¥å¥¢¥ë¥»¥¯¥·¥ç¥ó¤ÏÇѻߤµ¤ì¤¿¡£
.\" ¤«¤Ä¤Æ¤Ï¤³¤³¤Ë Linux ¥«¡¼¥Í¥ë¤Î¥É¥­¥å¥á¥ó¥È¤òÃÖ¤¯¤Î¤¬Îɤ¤¤³¤È¤À¤È
.\" ¹Í¤¨¤é¤ì¤Æ¤¤¤¿¡£¤·¤«¤·¡¢Ê¸½ñ²½¤µ¤ì¤¿¤â¤Î¤ÏÈó¾ï¤Ë¾¯¤Ê¤¯¡¢
.\" ¤Þ¤¿¤½¤ì¤é¤â¤¹¤Ç¤Ë¸Å¤¤¤â¤Î¤È¤Ê¤Ã¤Æ¤·¤Þ¤Ã¤¿¡£
.\" ¥«¡¼¥Í¥ë³«È¯¼Ô¤Ë¤È¤Ã¤Æ¡¢¤â¤Ã¤È¤è¤¤¾ðÊ󸻤¬Â¾¤Ë¤¢¤ë¤À¤í¤¦¡£
.\"O .SS Macro package
.SS ¥Þ¥¯¥í¥Ñ¥Ã¥±¡¼¥¸
.\"O New manual pages should be marked up using the
.\"O .B groff an.tmac
.\"O package described in
.\"O .BR man (7).
.\"O This choice is mainly for consistency: the vast majority of
.\"O existing Linux manual pages are marked up using these macros.
¿·¤·¤¤¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ï
.BR man (7)
¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ë
.B groff an.tmac
¥Ñ¥Ã¥±¡¼¥¸¤ò»È¤Ã¤Æµ­½Ò¤¹¤Ù¤­¤Ç¤¢¤ë¡£
¤³¤ÎÊý¿Ë¤Ï°ì´ÓÀ­¤Î³ÎÊݤ¬¼ç¤ÊÍýͳ¤Ç¤¢¤ë¡£´û¸¤Î Linux ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸
¤Î°µÅÝŪ¿¿ô¤¬¤³¤ì¤é¤Î¥Þ¥¯¥í¤ò»È¤Ã¤Æµ­½Ò¤µ¤ì¤Æ¤¤¤ë¡£
.\"O .SS Conventions for source file layout
.SS ¥½¡¼¥¹¥Õ¥¡¥¤¥ë¤ÎÇÛÃ֤˴ؤ¹¤ë·è¤Þ¤ê»ö
.\"O Please limit source code line length to no more than about 75 characters
.\"O wherever possible.
.\"O This helps avoid line-wrapping in some mail clients when patches are
.\"O submitted inline.
¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Î¥½¡¼¥¹¥³¡¼¥É¤Î 1¹Ô¤ÎŤµ¤Ï
²Äǽ¤Ê¸Â¤ê 75ʸ»ú¤ò±Û¤¨¤Ê¤¤¤è¤¦¤Ë¤·¤Æ¤Û¤·¤¤¡£
¤³¤¦¤¹¤ë¤³¤È¤Ç¡¢¥Ñ¥Ã¥Á¤ò¥á¡¼¥ëËÜʸ¤ËºÜ¤»¤ÆÁ÷¤ë¾ì¹ç¤Ë¡¢
¥á¡¼¥ë¥¯¥é¥¤¥¢¥ó¥È¤Ë¤è¤ë¹ÔÀÞ¤êÊÖ¤·¤ò²óÈò¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¡£

.\"O New sentences should be started on new lines.
.\"O This makes it easier to see the effect of patches,
.\"O which often operate at the level of individual sentences.
¿·¤·¤¤Ê¸¤Ï¹ÔƬ¤«¤é³«»Ï¤¹¤ë¡£
¤³¤ì¤Ë¤è¤ê¡¢¥Ñ¥Ã¥Á¤ÎÆâÍƤò³Îǧ¤·¤ä¤¹¤¯¤Ê¤ë¡£
¥Ñ¥Ã¥Á¤Ïʸñ°Ì¤Ç¤¢¤ë¤³¤È¤¬Â¿¤¤¤«¤é¤Ç¤¢¤ë¡£
.\"O .SS Title line
.SS ¥¿¥¤¥È¥ë¹Ô
.\"O The first command in a man page should be a \fBTH\fP command:
man ¥Ú¡¼¥¸¤ÎºÇ½é¤Î¹Ô¤Ï \fBTH\fP ¥³¥Þ¥ó¥É¤Ë¤¹¤Ù¤­¤Ç¤¢¤ë¡£
.RS
.sp
.B \&.TH
.I "title section date source manual"
.sp
.RE
.\"O where:
¸Ä¡¹¤ÎÀâÌÀ:
.RS
.TP 10
.I title
.\"O The title of the man page, written in all caps (e.g.,
.\"O .IR MAN-PAGES ).
man ¥Ú¡¼¥¸¤Î¥¿¥¤¥È¥ë¡£Á´ÉôÂçʸ»ú¤Çµ­ºÜ¤¹¤ë (Îã:
.IR MAN-PAGES )¡£
.TP
.I section
.\"O The section number in which the man page should be placed (e.g.,
.\"O .IR 7 ).
man ¥Ú¡¼¥¸¤¬Â°¤¹¤ë¥»¥¯¥·¥ç¥óÈÖ¹æ (Îã:
.IR 7 )¡£
.TP
.I date
.\"O The date of the last revision \(em remember to change this every time a
.\"O change is made to the man page,
.\"O since this is the most general way of doing version control.
.\"O Dates should be written in the form YYYY-MM-DD.
ºÇ¿·¤Î¥ê¥Ó¥¸¥ç¥ó¤ÎÆüÉÕ \(em man ¥Ú¡¼¥¸¤ËÊѹ¹¤ò²Ã¤¨¤¿¤È¤­¤Ë¤Ï
ɬ¤º¤³¤ì¤òÊѹ¹¤¹¤ë¤³¤È¡£
¤³¤ì¤¬ºÇ¤â°ìÈÌŪ¤Ê¥Ð¡¼¥¸¥ç¥ó´ÉÍýÊýË¡¤Ç¤¢¤ë¡£
ÆüÉÕ¤Ï YYYY-MM-DD ¤Î·Á¼°¤Çµ­ºÜ¤¹¤Ù¤­¤Ç¤¢¤ë¡£
.TP
.I source
.\"O The source of the command, function, or system call.
¥³¥Þ¥ó¥É¡¢´Ø¿ô¡¢¥·¥¹¥Æ¥à¥³¡¼¥ë¤Î½Ð¼«¡£

.\"O For those few \fIman-pages\fP pages in Sections 1 and 8,
.\"O probably you just want to write
.\"O .IR GNU .
¿ô¾¯¤Ê¤¤¥»¥¯¥·¥ç¥ó 1 ¤È 8 ¤Î¥Ú¡¼¥¸¤Î¾ì¹ç¡¢¤ª¤½¤é¤¯Ã±¤Ë
.I GNU
¤È¤À¤±½ñ¤¯¤³¤È¤¬Â¿¤¤¤À¤í¤¦¡£

.\"O For system calls, just write
.\"O .IR "Linux" .
.\"O (An earlier practice was to write the version number
.\"O of the kernel from which the manual page was being written/checked.
.\"O However, this was never done consistently, and so was
.\"O probably worse than including no version number.
.\"O Henceforth, avoid including a version number.)
¥·¥¹¥Æ¥à¥³¡¼¥ë¤Î¾ì¹ç¡¢Ã±¤Ë
.I "Linux"
¤È¤À¤±½ñ¤¯¡£
(°ÊÁ°¤Î´·½¬¤Ç¤Ï¡¢¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤òµ­ºÜ¤·¤¿/ÆâÍƤò³Îǧ¤·¤¿¥«¡¼¥Í¥ë¤Î
¥Ð¡¼¥¸¥ç¥óÈÖ¹æ¤òµ­ºÜ¤·¤Æ¤¤¤¿¡£¤·¤«¤·¡¢¥Ð¡¼¥¸¥ç¥óÈֹ椬¼ÂºÝ¤ÎÆâÍƤÈ
°ìÃפ·¤Æ¤¤¤ë¤³¤È¤Ï¤Ê¤¯¡¢¤½¤Î¤¿¤á¥Ð¡¼¥¸¥ç¥óÈֹ椬¤Ê¤¤¤è¤ê¤â
¤ª¤½¤é¤¯°­¤¤·Á¤Ë¤Ê¤Ã¤Æ¤¤¤¿¡£
º£¸å¤Ï¡¢¥Ð¡¼¥¸¥ç¥óÈÖ¹æ¤ò´Þ¤á¤ë¤Î¤ÏÈò¤±¤ë¤³¤È¡£)

.\"O For library calls that are part of glibc or one of the
.\"O other common GNU libraries, just use
.\"O .IR "GNU C Library" ", " GNU ,
.\"O or an empty string.
glibc ¤Î¥é¥¤¥Ö¥é¥ê¥³¡¼¥ë¤ä
¤½¤Î¾¤Î°ìÈÌŪ¤Ê GNU ¥é¥¤¥Ö¥é¥ê¤Î¥é¥¤¥Ö¥é¥ê¥³¡¼¥ë¤Î¾ì¹ç¡¢
ñ¤Ë
.IR "GNU C Library" ", " GNU
¤È½ñ¤¯¤«¡¢¶õ¤Îʸ»úÎó¤ò»È¤¦¡£

.\"O For Section 4 pages, use
.\"O .IR "Linux" .
¥»¥¯¥·¥ç¥ó 4 ¤Î¥Ú¡¼¥¸¤Ç¤Ï
.I "Linux"
¤ò»È¤¦¡£

.\"O In cases of doubt, just write
.\"O .IR Linux ", or " GNU .
¤è¤¯¤ï¤«¤é¤Ê¤¤¾ì¹ç¤Ï¡¢
.I Linux
¤È¤«
.I GNU
¤È½ñ¤¤¤Æ¤ª¤¯¡£
.TP
.I manual
.\"O The title of the manual (e.g., for Section 2 and 3 pages in
.\"O the \fIman-pages\fP package, use
.\"O .IR "Linux Programmer's Manual" ).
¥Þ¥Ë¥å¥¢¥ë¤Î¥¿¥¤¥È¥ë (Îã:
\fIman-pages\fP ¥Ñ¥Ã¥±¡¼¥¸¤Î¥»¥¯¥·¥ç¥ó 2 ¤ª¤è¤Ó 3 ¤Î¥Ú¡¼¥¸¤Î¾ì¹ç¤Ë¤Ï¡¢
.I "Linux Programmer's Manual"
¤ò»È¤¦¤³¤È)¡£
.RE
.\"O .SS Sections within a manual page
.SS ¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Î¥»¥¯¥·¥ç¥ó
.\"O The list below shows conventional or suggested sections.
.\"O Most manual pages should include at least the
.\"O .B highlighted
.\"O sections.
.\"O Arrange a new manual page so that sections
.\"O are placed in the order shown in the list.
ÀΤ«¤é»È¤ï¤ì¤Æ¤­¤¿¥»¥¯¥·¥ç¥ó̾¤ò°Ê²¼¤Î¥ê¥¹¥È¤Ë¼¨¤¹¡£
¤³¤ì¤é¤ò»È¤¦¤ÈÎɤ¤¤À¤í¤¦¡£
°ìÈÌŪ¤Ë¡¢¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ï¡¢¾¯¤Ê¤¯¤È¤â
.B ¿§¤Ä¤­
¤Î¥»¥¯¥·¥ç¥ó¤ò»ý¤Ä¤Î¤¬Ë¾¤Þ¤·¤¤¡£
¿·¤·¤¯¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤òºîÀ®¤¹¤ëºÝ¤Ë¤Ï¡¢¤À¤¤¤¿¤¤°Ê²¼¤Î¥ê¥¹¥È¤Ë¼¨¤·¤¿
½ç½ø¤Ç¥»¥¯¥·¥ç¥ó¤òÇÛÃÖ¤¹¤ë¤è¤¦¤Ë¤·¤Æ¤â¤é¤¤¤¿¤¤¡£
.in +0.5i
.nf

.\"O \fBNAME\fP
\fB̾Á°\fP
.\"O \fBSYNOPSIS\fP
\fB½ñ¼°\fP
.\"O CONFIGURATION      [Normally only in Section 4]
ÀßÄê               [Ä̾ï¤Ï¥»¥¯¥·¥ç¥ó 4 ¤Î¤ß]
.\"O \fBDESCRIPTION\fP
\fBÀâÌÀ\fP
.\"O OPTIONS            [Normally only in Sections 1, 8]
¥ª¥×¥·¥ç¥ó         [Ä̾ï¤Ï¥»¥¯¥·¥ç¥ó 1, 8 ¤Î¤ß]
.\"O EXIT STATUS        [Normally only in Sections 1, 8]
½ªÎ»¥¹¥Æ¡¼¥¿¥¹     [Ä̾ï¤Ï¥»¥¯¥·¥ç¥ó 1, 8 ¤Î¤ß]
.\"O RETURN VALUE       [Normally only in Sections 2, 3]
ÊÖ¤êÃÍ             [Ä̾ï¤Ï¥»¥¯¥·¥ç¥ó 2, 3 ¤Î¤ß]
.\" May 07: Few current man pages have an ERROR HANDLING section,,,
.\"O .\" ERROR HANDLING,
.\" ¥¨¥é¡¼½èÍý
.\"O ERRORS             [Typically only in Sections 2, 3]
¥¨¥é¡¼             [¤¿¤¤¤Æ¤¤¤Ï¥»¥¯¥·¥ç¥ó 2, 3 ¤Î¤ß]
.\" May 07: Almost no current man pages have a USAGE section,,,
.\"O .\" USAGE,
.\" ÍøÍÑË¡
.\"O .\" DIAGNOSTICS,
.\" ¿ÇÃÇ¥á¥Ã¥»¡¼¥¸
.\" May 07: Almost no current man pages have a SECURITY section,,,
.\"O .\" SECURITY,
.\" ¥»¥­¥å¥ê¥Æ¥£
.\"O ENVIRONMENT
´Ä¶­ÊÑ¿ô
.\"O FILES
¥Õ¥¡¥¤¥ë
.\"O VERSIONS           [Normally only in Sections 2, 3]
¥Ð¡¼¥¸¥ç¥ó         [Ä̾ï¤Ï¥»¥¯¥·¥ç¥ó 2, 3 ¤Î¤ß]
.\"O CONFORMING TO
½àµò
.\"O NOTES
Ãí°Õ/È÷¹Í
.\"O BUGS
¥Ð¥°
.\"O EXAMPLE
Îã
.\"O .\" AUTHORS sections are discouraged
.\"O .\" AUTHORS             [Discouraged]
.\" Ãø¼Ô ¥»¥¯¥·¥ç¥ó¤ÏÈó¿ä¾©¤Ç¤¢¤ë
.\" Ãø¼Ô
.\"O \fBSEE ALSO\fP
\fB´ØÏ¢¹àÌÜ\fP

.fi
.in
.\"O .IR "Where a traditional heading would apply" ", " "please use it" ;
.\"O this kind of consistency can make the information easier to understand.
.\"O If you must, you can create your own
.\"O headings if they make things easier to understand (this can
.\"O be especially useful for pages in Sections 4 and 5).
.\"O However, before doing this, consider whether you could use the
.\"O traditional headings, with some subsections (\fI.SS\fP) within
.\"O those sections.
¡ÖÅÁÅýŪ¤Ë»È¤ï¤ì¤Æ¤­¤¿¸«½Ð¤·¤¬»È¤¨¤ë¾ì¹ç¤Ë¤Ï¡¢¤½¤ì¤ò»È¤Ã¤Æ¤Û¤·¤¤¡£¡×
¤³¤Î¼ï¤Î°ì´ÓÀ­¤òÊݤĤ³¤È¤Ç¡¢¾ðÊó¤òÍý²ò¤·¤ä¤¹¤¯¤Ê¤ë¤«¤é¤Ç¤¢¤ë¡£
¤É¤¦¤·¤Æ¤âɬÍפʾì¹ç¤Ë¤Ï¡¢Íý²ò¤·¤ä¤¹¤¯¤Ê¤ë¤è¤¦¤ËÆȼ«¤Î¸«½Ð¤·¤ò
ºî¤Ã¤Æ¤â¤è¤¤ (Æä˥»¥¯¥·¥ç¥ó 4 ¤ä 5 ¤Î¥Ú¡¼¥¸¤Ç¤Ï¤³¤¦¤·¤¿Êý¤¬
¤ï¤«¤ê¤ä¤¹¤¯¤Ê¤ë)¡£¤¿¤À¤·¡¢¤½¤¦¤¹¤ëÁ°¤Ë¡¢ÅÁÅýŪ¤Ê¸«½Ð¤·¤ò»È¤¤¡¢
¤½¤Î¥»¥¯¥·¥ç¥óÆâ¤Ë¥µ¥Ö¥»¥¯¥·¥ç¥ó (\fI.SS\fP) ¤òÀߤ±¤ë¤³¤È¤Ç
Âбþ¤Ç¤­¤Ê¤¤¤«¹Í¤¨¤Æ¤Û¤·¤¤¡£

.\"O The following list elaborates on the contents of each of
.\"O the above sections.
°Ê²¼¤Î¥ê¥¹¥È¤Ç¤Ï¡¢¾åµ­¤Î¥»¥¯¥·¥ç¥ó¤Î¤½¤ì¤¾¤ì¤ÎÆâÍƤˤĤ¤¤Æ
¾Ü¤·¤¯ÀâÌÀ¤¹¤ë¡£
.TP 14
.\"O .B NAME
.B ̾Á° (NAME)
.\"O The name of this manual page.
.\"O See
.\"O .BR man (7)
.\"O for important details of the line(s) that should follow the
.\"O \fB.SH NAME\fP command.
¤½¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Î̾Á°¡£
\fB.SH NAME\fP ¥³¥Þ¥ó¥É¤Î¹Ô¤¬½¾¤¦¤Ù¤­Âç»ö¤ÊÅÀ¤Ë¤Ä¤¤¤Æ¤Ï
.BR man (7)
¤ò»²¾È¤·¤Æ¤Û¤·¤¤¡£
.TP
.\"O .B SYNOPSIS
.B ½ñ¼° (SYNOPSIS)
.\"O briefly describes the command or function's interface.
.\"O For commands, this shows the syntax of the command and its arguments
.\"O (including options);
.\"O boldface is used for as-is text and italics are used to
.\"O indicate replaceable arguments.
.\"O Brackets ([]) surround optional arguments, vertical bars (|)
.\"O separate choices, and ellipses (\&...) can be repeated.
.\"O For functions, it shows any required data declarations or
.\"O .B #include
.\"O directives, followed by the function declaration.
¥³¥Þ¥ó¥É¤ä´Ø¿ô¤Î¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤ò´Ê·é¤Ëµ­½Ò¤¹¤ë¡£
¥³¥Þ¥ó¥É¤ËÂФ·¤Æ¤Ï¡¢¥³¥Þ¥ó¥É¤ä°ú¤­¿ô (¥ª¥×¥·¥ç¥ó) ¤Îʸˡ¤ò½ñ¤¯¡£
¤½¤Î¤Þ¤Þ½ñ¤¯¥Æ¥­¥¹¥È¤Ë¤Ï¥Ü¡¼¥ë¥ÉÂΤòÍѤ¤¡¢ÃÖ¤­´¹¤¨¤ë°ú¤­¿ô¤Ë¤Ï
¥¤¥¿¥ê¥Ã¥¯ÂΤòÍѤ¤¤ë¡£¾Êά²Äǽ¤Ê¥ª¥×¥·¥ç¥ó¤Ï¥Ö¥é¥±¥Ã¥È ([]) ¤Ç°Ï¤¤¡¢
ÁªÂò»è¤Ï½ÄËÀ (|) ¤Ç¶èÀڤꡢ·«¤êÊÖ¤·¤Ë¤Ï¾ÊάÉä¹æ (...) ¤ò½ñ¤¯¡£
´Ø¿ô¤ËÂФ·¤Æ¤Ï¡¢É¬Íפʥǡ¼¥¿Àë¸À¤ä
.B #include
»ØÄê¤ò½ñ¤­¡¢´Ø¿ôÀë¸À¤ò³¤±¤ë¡£

.\"O Where a feature test macro must be defined in order to obtain
.\"O the declaration of a function (or a variable) from a header file,
.\"O then the SYNOPSIS should indicate this, as described in
.\"O .BR feature_test_macros (7).
¥Ø¥Ã¥À¥Õ¥¡¥¤¥ë¤«¤é´Ø¿ô (¤äÊÑ¿ô) ¤ÎÄêµÁ¤òÆÀ¤ë¤¿¤á¤Ë
µ¡Ç½¸¡ºº¥Þ¥¯¥í (feature test macro) ¤òÄêµÁ¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¾ì¹ç¡¢
½ñ¼° (SYNOPSIS) ¤ËɬÍפʵ¡Ç½¸¡ºº¥Þ¥¯¥í¤òµ­ºÜ¤¹¤Ù¤­¤Ç¤¢¤ë¡£
µ¡Ç½¸¡ºº¥Þ¥¯¥í¤Ë¤Ä¤¤¤Æ¤Ï
.BR feature_test_macros (7)
¤ÇÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¡£
.\" FIXME . Say something here about compiler options
.TP
.B CONFIGURATION
.\"O Configuration details for a device.
.\"O This section normally only appears in Section 4 pages.
¥Ç¥Ð¥¤¥¹¤ÎÀßÄê¾ÜºÙ¡£
Ä̾¤³¤Î¥»¥¯¥·¥ç¥ó¤Ï 4 ¾Ï¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ç¤Î¤ßÅо줹¤ë¡£
.TP
.\"O .B DESCRIPTION
.B ÀâÌÀ (DESCRIPTION)
.\"O gives an explanation of what the program, function, or format does.
.\"O Discuss how it interacts with files and standard input, and what it
.\"O produces on standard output or standard error.
.\"O Omit internals and implementation details unless they're critical for
.\"O understanding the interface.
.\"O Describe the usual case;
.\"O for information on command-line options of a program use the
.\"O .B OPTIONS
.\"O section.
¥×¥í¥°¥é¥à¡¦´Ø¿ô¡¦¥Õ¥©¡¼¥Þ¥Ã¥È¤ÎÆ°ºî¡¦ÌÜŪ¤òÀâÌÀ¤¹¤ë¡£
¥Õ¥¡¥¤¥ë¤äɸ½àÆþÎϤò¤É¤Î¤è¤¦¤Ë½èÍý¤·¡¢É¸½à½ÐÎϤäɸ½à¥¨¥é¡¼½ÐÎϤò
¤É¤Î¤è¤¦¤ËÀ¸À®¤¹¤ë¤«¤È¤¤¤Ã¤¿¤³¤È¤Ë¤Ä¤¤¤Æ½Ò¤Ù¤ë¡£
ÆâÉôÆ°ºî¤ä¼ÂÁõ¤Î¾ÜºÙ¤Ë¤Ä¤¤¤Æ¤Ï¾Êά¤¹¤ë
(¤¿¤À¤·¤½¤ì¤¬Æ°ºî¤ÎÍý²ò¤Ë¤É¤¦¤·¤Æ¤âɬÍפʤéÊÌ)¡£
Ä̾ï¤Î¾ì¹ç¤Ë¤Ä¤¤¤Æµ­½Ò¤¹¤ë¡£
¥×¥í¥°¥é¥à¤Î¥³¥Þ¥ó¥É¥é¥¤¥ó¡¦¥ª¥×¥·¥ç¥ó¤ÎÀâÌÀ¤Ë¤Ï¡¢
.B ¥ª¥×¥·¥ç¥ó
¤Î¥»¥¯¥·¥ç¥ó¤òÍѤ¤¤ë¡£
.\"O .\" If there is some kind of input grammar or complex set of subcommands,
.\"O .\" consider describing them in a separate
.\"O .\" .B USAGE
.\"O .\" section (and just place an overview in the
.\"O .\" .B DESCRIPTION
.\"O .\" section).
.\" ÆþÎϤˤ¢¤ë¼ï¤Îʸˡ¤¬¤¢¤Ã¤¿¤ê¡¢Ê£»¨¤Ê¥µ¥Ö¥³¥Þ¥ó¥É¤¬¤¢¤ë¾ì¹ç¤Ï¡¢
.\" ¤½¤ì¤é¤Ï
.\" .B ÍøÍÑË¡
.\" ¤Î¥»¥¯¥·¥ç¥ó¤ËʬΥ¤¹¤ë¤³¤È¤ò¹Í¤¨¤ë¤È¤è¤¤
.\" .RB ( ÀâÌÀ
.\" ¤Î¥»¥¯¥·¥ç¥ó¤Ë¤Ï³µÍפÀ¤±¤òÃÖ¤¯¤è¤¦¤Ë¤¹¤ë)¡£
.TP
.\"O .B OPTIONS
.B ¥ª¥×¥·¥ç¥ó (OPTIONS)
.\"O describes the command-line options accepted by a
.\"O program and how they change its behavior.
.\"O This section should only appear for Section 1 and 8 manual pages.
¥×¥í¥°¥é¥à¤¬¼õ¤±ÉÕ¤±¤ë¥³¥Þ¥ó¥É¥é¥¤¥ó¡¦¥ª¥×¥·¥ç¥ó¤È¡¢
¤½¤Î¾ì¹ç¥×¥í¥°¥é¥à¤Î¿¶Éñ¤¤¤¬¤É¤¦ÊѤï¤ë¤«¤òÀâÌÀ¤¹¤ë¡£
¤³¤Î¥»¥¯¥·¥ç¥ó¤Ï¥»¥¯¥·¥ç¥ó 1 ¤È 8 ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ë¤À¤±Åо줹¤Ù¤­¤Ç¤¢¤ë¡£
.\" .TP
.\"O .\" .B USAGE
.\" .B ÍøÍÑË¡ (USAGE)
.\"O .\" describes the grammar of any sublanguage this implements.
.\" ¥³¥Þ¥ó¥É¤Ê¤É¤¬¼ÂÁõ¤·¤Æ¤¤¤ëÉû¸À¸ì (sublanguage) ¤Îʸˡ¤òµ­½Ò¤¹¤ë¡£
.TP
.\"O .B EXIT STATUS
.B ½ªÎ»¥¹¥Æ¡¼¥¿¥¹ (EXIT STATUS)
.\"O lists the possible exit status values of a program and
.\"O the conditions that cause these values to be returned.
.\"O This section should only appear for Section 1 and 8 manual pages.
¥×¥í¥°¥é¥à¤Î½ªÎ»¥¹¥Æ¡¼¥¿¥¹¤ÎÃͤȡ¢¤½¤ì¤é¤ÎÃͤËÂбþ¤¹¤ë¾õ¶·¤òÎóµó¤¹¤ë¡£
¤³¤Î¥»¥¯¥·¥ç¥ó¤Ï¥»¥¯¥·¥ç¥ó 1 ¤È 8 ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ë¤À¤±Åо줹¤Ù¤­¤Ç¤¢¤ë¡£
.TP
.\"O .B RETURN VALUE
.B ÊÖ¤êÃÍ (RETURN VALUE)
.\"O For Section 2 and 3 pages, this section gives a
.\"O list of the values the library routine will return to the caller
.\"O and the conditions that cause these values to be returned.
¥»¥¯¥·¥ç¥ó 2 ¤È 3 ¤Î¥Ú¡¼¥¸¤Î¾ì¹ç¡¢¤³¤Î¥»¥¯¥·¥ç¥ó¤Ë
¥é¥¤¥Ö¥é¥ê¥ë¡¼¥Á¥ó¤¬¸Æ¤Ó½Ð¤·¸µ¤ËÊÖ¤¹ÃͤΥꥹ¥È¤òµ­ºÜ¤¹¤ë¡£
¤½¤ì¤é¤ÎÃͤ¬ÊÖ¤µ¤ì¤¿¾ì¹ç¤Î¾õÂÖ¤ËÂФ¹¤ëÀâÌÀ¤â½ñ¤¯¡£
.TP
.\"O .B ERRORS
.B ¥¨¥é¡¼ (ERRORS)
.\"O For Section 2 and 3 manual pages, this is a list of the
.\"O values that may be placed in
.\"O .I errno
.\"O in the event of an error, along with information about the cause
.\"O of the errors.
.\"O .IR "The error list should be in alphabetical order" .
¥»¥¯¥·¥ç¥ó 2 ¤È 3 ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ç¤Ï¡¢
¥¨¥é¡¼¤¬È¯À¸¤·¤¿¾ì¹ç¤Ë
.I errno
¤ËÀßÄꤵ¤ì¤ë²ÄǽÀ­¤¬¤¢¤ëÃͤΥꥹ¥È¤òµ­ºÜ¤¹¤ë¡£
¥ê¥¹¥È¤Ë¤Ï¡¢¥¨¥é¡¼¤ÎÃͤȥ¨¥é¡¼¤Î¸¶°ø¤Ë¤Ä¤¤¤Æ¤Î¾ðÊó¤ò½ñ¤¯¡£
¡Ö¥¨¥é¡¼¥ê¥¹¥È¤Ï¥¢¥ë¥Õ¥¡¥Ù¥Ã¥È½ç¤Ë¤¹¤Ù¤­¤Ç¤¢¤ë¡£¡×
.TP
.\"O .B ENVIRONMENT
.B ´Ä¶­ÊÑ¿ô (ENVIRONMENT)
.\"O lists all environment variables that affect the program or function
.\"O and how they affect it.
¥×¥í¥°¥é¥à¤ä´Ø¿ô¤Ë±Æ¶Á¤¹¤ë´Ä¶­ÊÑ¿ô¤ò¥ê¥¹¥È¤·¡¢¤½¤ì¤é¤Î¸ú²Ì¤ò½ñ¤¯¡£
.TP
.\"O .B FILES
.B ¥Õ¥¡¥¤¥ë (FILES)
.\"O lists the files the program or function uses, such as
.\"O configuration files, startup files,
.\"O and files the program directly operates on.
.\"O Give the full pathname of these files, and use the installation
.\"O process to modify the directory part to match user preferences.
.\"O For many programs, the default installation location is in
.\"O .IR /usr/local ,
.\"O so your base manual page should use
.\"O .I /usr/local
.\"O as the base.
¥×¥í¥°¥é¥à¤ä´Ø¿ô¤¬ÍѤ¤¤ë¥Õ¥¡¥¤¥ë¤òÎóµ­¤¹¤ë¡£
Î㤨¤Ð¡¢ÀßÄê¥Õ¥¡¥¤¥ë¡¢µ¯Æ°¥Õ¥¡¥¤¥ë¡¢¥×¥í¥°¥é¥à¤¬Ä¾ÀÜÁàºî¤¹¤ë¥Õ¥¡¥¤¥ë¤Ê¤É¤Ç¤¢¤ë¡£
¤³¤ì¤é¤Î¥Õ¥¡¥¤¥ë¤Î¥Õ¥¡¥¤¥ë̾¤Ï¥Õ¥ë¥Ñ¥¹¤Çµ­ºÜ¤·¡¢
¥Ç¥£¥ì¥¯¥È¥ê¤ÎÉôʬ¤Ï¥æ¡¼¥¶¡¼¤Î¹¥¤ß¤Ë¹ç¤ï¤»¤Æ
¥¤¥ó¥¹¥È¡¼¥ë½èÍý¤ÇÊѹ¹¤Ç¤­¤ë¤è¤¦¤Ë¤¹¤ë¡£
¿¤¯¤Î¥×¥í¥°¥é¥à¤Ç¤Ï¥Ç¥Õ¥©¥ë¥È¤Î¥¤¥ó¥¹¥È¡¼¥ëÀè¤Ï
.I /usr/local
¤Ç¤¢¤ë¡£¤·¤¿¤¬¤Ã¤Æ¥Ù¡¼¥¹¤È¤Ê¤ë¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ç¤â
.I /usr/local
¤¬»È¤ï¤ì¤Æ¤¤¤ë¤³¤È¤¬Â¿¤¤¤À¤í¤¦¡£
.\" May 07: Almost no current man pages have a DIAGNOSTICS section;
.\"         "RETURN VALUE" or "EXIT STATUS" is preferred.
.\" .TP
.\"O .\" .B DIAGNOSTICS
.\" .B ¿ÇÃÇ¥á¥Ã¥»¡¼¥¸ (DIAGNOSTICS)
.\"O .\" gives an overview of the most common error messages and how to
.\"O .\" cope with them.
.\"O .\" You don't need to explain system error messages
.\"O .\" or fatal signals that can appear during execution of any program
.\"O .\" unless they're special in some way to the program.
.\" ¤´¤¯°ìÈÌŪ¤Ê¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤Î³µÍפȡ¢
.\" ¤½¤ì¤é¤ò¤É¤¦°·¤¦¤«¤Ë¤Ä¤¤¤Æ½Ò¤Ù¤ë¡£¥×¥í¥°¥é¥à¤Î¼Â¹Ô»þ¤Ë¸½¤ì¤ë
.\" ¥·¥¹¥Æ¥à¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤äÃ×̿Ū¥·¥°¥Ê¥ë¤òÁ´ÉôÀâÌÀ¤¹¤ëɬÍפϤʤ¤¡£
.\" ¤¿¤À¤·¤½¤ì¤é¤¬¥×¥í¥°¥é¥à¤ËÂФ·¤Æ
.\" ²¿¤é¤«¤ÎÆüì¤Ê°ÕÌ£¤ò»ý¤Ã¤Æ¤¤¤ë¾ì¹ç¤ÏÊ̤Ǥ¢¤ë¡£
.\"
.\" May 07: Almost no current man pages have a SECURITY section.
.\".TP
.\"O .\".B SECURITY
.\" .B ¥»¥­¥å¥ê¥Æ¥£ (SECURITY)
.\"O .\"discusses security issues and implications.
.\"O .\"Warn about configurations or environments that should be avoided,
.\"O .\"commands that may have security implications, and so on, especially
.\"O .\"if they aren't obvious.
.\"O .\"Discussing security in a separate section isn't necessary;
.\"O .\"if it's easier to understand, place security information in the
.\"O .\"other sections (such as the
.\"O .\" .B DESCRIPTION
.\"O .\" or
.\"O .\" .B USAGE
.\"O .\" section).
.\"O .\" However, please include security information somewhere!
.\" ¥»¥­¥å¥ê¥Æ¥£´ØÏ¢¤ÎÏÃÂꡦÌäÂê¤Ë¤Ä¤¤¤Æ½Ò¤Ù¤ë¡£
.\" Èò¤±¤ë¤Ù¤­ÀßÄê¤ä´Ä¶­¡¦¥»¥­¥å¥ê¥Æ¥£¾å¤ÎÌäÂê¤ò°ú¤­µ¯¤³¤¹¥³¥Þ¥ó¥É
.\" ¤Ê¤É¤Ë¤Ä¤¤¤Æ·Ù¹ð¤¹¤ë¡£¤½¤ì¤é¤¬ÌÀ¤é¤«¤Ç¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢¤³¤ì¤ÏÆä˽ÅÍפǤ¢¤ë¡£
.\" ¥»¥­¥å¥ê¥Æ¥£¤Ë´Ø¤¹¤ëÏÃÂê¤Ï¡¢É¬¤º¤·¤âÆÈΩ¤·¤¿¥»¥¯¥·¥ç¥ó¤Ë¤¹¤ëɬÍפϤʤ¤¡£
.\" ¤â¤·Íý²ò¤·¤ä¤¹¤±¤ì¤Ð¡¢¥»¥­¥å¥ê¥Æ¥£¤Î¾ðÊó¤Ï¾¤Î¥»¥¯¥·¥ç¥ó
.\" (Î㤨¤Ð
.\" .B ÀâÌÀ
.\" ¤ä
.\" .B ÍøÍÑË¡
.\" ¤Ê¤É) ¤Ë½ñ¤¤¤Æ¤â¤è¤¤¡£
.\" ¤·¤«¤·¡¢¥»¥­¥å¥ê¥Æ¥£¤Î¾ðÊó¤Ï¤É¤³¤«¤Ë¤Ï½ñ¤¤¤Æ¤ª¤¤¤Æ¤Û¤·¤¤!
.TP
.\"O .B VERSIONS
.B ¥Ð¡¼¥¸¥ç¥ó (VERSIONS)
.\"O A brief summary of the Linux kernel or glibc versions where a
.\"O system call or library function appeared,
.\"O or changed significantly in its operation.
¥·¥¹¥Æ¥à¥³¡¼¥ë¤ä¥é¥¤¥Ö¥é¥ê´Ø¿ô¤¬Åо줷¤¿¤ê¡¢Æ°ºî¤Î½ÅÍפÊÊѹ¹¤¬¹Ô¤ï¤ì¤¿¡¢
Linux ¥«¡¼¥Í¥ë¤ä glibc ¤Î¥Ð¡¼¥¸¥ç¥ó¤Ë¤Ä¤¤¤Æ¤Î´Ê·é¤Ê³µÍס£
.\"O As a general rule, every new interface should
.\"O include a VERSIONS section in its manual page.
.\"O Unfortunately,
.\"O many existing manual pages don't include this information
.\"O (since there was no policy to do so when they were written).
.\"O Patches to remedy this are welcome,
.\"O but, from the perspective of programmers writing new code,
.\"O this information probably only matters in the case of kernel
.\"O interfaces that have been added in Linux 2.4 or later
.\"O (i.e., changes since kernel 2.2),
.\"O and library functions that have been added to glibc since version 2.1
.\"O (i.e., changes since glibc 2.0).
°ìÈ̤ˡ¢Á´¤Æ¤Î¿·¤·¤¤¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹¤Ï¡¢¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ë
¡Ö¥Ð¡¼¥¸¥ç¥ó¡×¤ÎÀá¤òÀߤ±¤ë¤Ù¤­¤Ç¤¢¤ë¡£
»ÄÇ°¤Ê¤³¤È¤Ë¡¢Â¿¤¯¤Î´û¸¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ë¤³¤Î¾ðÊó¤Ï´Þ¤Þ¤ì¤Æ¤¤¤Ê¤¤
(¤³¤ì¤é¤Î¥Ú¡¼¥¸¤¬½ñ¤«¤ì¤¿»þÅÀ¤Ç¤Ï¤½¤Î¤è¤¦¤Ê¥Ý¥ê¥·¡¼¤Ï¤Ê¤«¤Ã¤¿¤«¤é¤Ç¤¢¤ë)¡£
¤³¤ì¤ò²þÁ±¤¹¤ë¥Ñ¥Ã¥Á¤Ï´¿·Þ¤µ¤ì¤ë¤¬¡¢
¿·¤·¤¤¥³¡¼¥É¤ò½ñ¤¯¥×¥í¥°¥é¥Þ¤Î´ÑÅÀ¤«¤é¤¹¤ì¤Ð¡¢
¤ª¤½¤é¤¯¤³¤Î¾ðÊ󤬽ÅÍפˤʤë¤Î¤Ï¡¢
Linux 2.4 °Ê¹ß¤ÇÄɲ䵤줿¥«¡¼¥Í¥ë¥¤¥ó¥¿¡¼¥Õ¥§¥¤¥¹ (¥«¡¼¥Í¥ë 2.2 ¤«¤é¤ÎÊѹ¹) ¤È
glibc ¥Ð¡¼¥¸¥ç¥ó 2.1 °Ê¹ß¤ÇÄɲ䵤줿¥é¥¤¥Ö¥é¥ê´Ø¿ô (glibc 2.0 ¤«¤é¤ÎÊѹ¹)
¤Ë¤Ä¤¤¤Æ¤Î¤ß¤Ç¤¢¤í¤¦¡£

.\"O The
.\"O .BR syscalls (2)
.\"O manual page also provides information about kernel versions
.\"O in which various system calls first appeared.
.BR syscalls (2)
¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ë¤â¡¢¤¤¤í¤¤¤í¤Ê¥·¥¹¥Æ¥à¥³¡¼¥ë¤¬½é¤á¤ÆÅо줷¤¿
¥«¡¼¥Í¥ë¥Ð¡¼¥¸¥ç¥ó¤Ë¤Ä¤¤¤Æ¤Î¾ðÊ󤬽ñ¤«¤ì¤Æ¤¤¤ë¡£
.TP
.\"O .B CONFORMING TO
.B ½àµò (CONFORMING TO)
.\"O describes any standards or conventions that relate to the function
.\"O or command described by the manual page.
.\"O For a page in Section 2 or 3,
.\"O this section should note the POSIX.1
.\"O version(s) that the call conforms to,
.\"O and also whether the call is specified in C99.
.\"O (Don't worry too much about other standards like SUS, SUSv2, and XPG,
.\"O or the SVr4 and 4.xBSD implementation standards,
.\"O unless the call was specified in those standards,
.\"O but isn't in the current version of POSIX.1.)
.\"O (See
.\"O .BR standards (7).)
¤½¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ÇÀâÌÀ¤·¤Æ¤¤¤ë´Ø¿ô¤ä¥³¥Þ¥ó¥É¤Ë´ØÏ¢¤¹¤ë
ɸ½àµ¬³Ê¤ä´·½¬¤Ë¤Ä¤¤¤Æµ­ºÜ¤¹¤ë¡£
¥»¥¯¥·¥ç¥ó 2 ¤ä 3 ¤Î¥Ú¡¼¥¸¤Ç¤Ï¡¢¤³¤Î¥»¥¯¥·¥ç¥ó¤Ç
¥·¥¹¥Æ¥à¥³¡¼¥ë¤ä´Ø¿ô¤¬½àµò¤¹¤ë POSIX.1 ¤Î¥Ð¡¼¥¸¥ç¥ó¤È¡¢
C99 ¤Çµ¬Äꤵ¤ì¤Æ¤¤¤ë¤«¤Ë¿¨¤ì¤ë¤Ù¤­¤Ç¤¢¤ë¡£
(SUS, SUSv2, XPG ¤Ê¤É¤Î¾¤Îɸ½àµ¬³Ê¤ä¡¢SVr4 ¤ä 4.xBSD ¤Î¼ÂÁõɸ½à¤Ë
¤Ä¤¤¤Æ¤Ï¡¢ÀâÌÀ¤·¤Æ¤¤¤ë¥³¡¼¥ë¤¬¤³¤ì¤é¤Îµ¬³Ê¤Çµ¬Äꤵ¤ì¤Æ¤ª¤ê
POSIX.1 ¤Î¸½¹Ô¥Ð¡¼¥¸¥ç¥ó¤Çµ¬Äꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç°Ê³°¤Ï¡¢
¤¢¤Þ¤ê¿¼¤¯µ¤¤Ë¤¹¤ëɬÍפϤʤ¤¡£)
.RB ( standards (7)
»²¾È¡£)

.\"O If the call is not governed by any standards but commonly
.\"O exists on other systems, note them.
.\"O If the call is Linux-specific, note this.
¤½¤Î¥³¡¼¥ë¤¬¤É¤Îɸ½à¤Ë¤â´ð¤Å¤¤¤Æ¤¤¤Ê¤¤¤¬¡¢
¾¤Î¥·¥¹¥Æ¥à¤Ç¹­¤¯Â¸ºß¤¹¤ë¾ì¹ç¤Ï¡¢¤½¤Î»Ý¤òµ­ºÜ¤¹¤ë¤³¤È¡£
¤½¤Î¥³¡¼¥ë¤¬ Linux ¸ÇÍ­¤Î¾ì¹ç¤Ï¡¢¤½¤Î»Ý¤òµ­ºÜ¤¹¤ë¤³¤È¡£

.\"O If this section consists of just a list of standards
.\"O (which it commonly does),
.\"O terminate the list with a period (\(aq.\(aq).
(¤½¤¦¤Ê¤Ã¤Æ¤¤¤ë¥Ú¡¼¥¸¤¬Â¿¤¤¤¬) ¤³¤Î¥»¥¯¥·¥ç¥ó¤ÎÆâÍƤ¬É¸½à¤Î¥ê¥¹¥È
¤À¤±¤Î¾ì¹ç¡¢¥ê¥¹¥È¤ÎºÇ¸å¤Ë¥Ô¥ê¥ª¥É (\(aq.\(aq) ¤òÃÖ¤¯¤³¤È¡£
.TP
.\"O .B NOTES
.B Ãí°Õ (NOTES)
.\"O provides miscellaneous notes.
.\"O For Section 2 and 3 man pages you may find it useful to include
.\"O subsections (\fBSS\fP) named \fILinux Notes\fP and \fIGlibc Notes\fP.
¤½¤Î¾¤ÎÃí°ÕÅÀ¤ò½ñ¤¯¡£
¥»¥¯¥·¥ç¥ó 2 ¤È 3 ¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ç¤Ï¡¢
\fILinux ¤Ç¤ÎÃí°Õ (Linux Notes)\fP ¤ä \fIglibc ¤Ç¤ÎÃí°Õ (Glibc Notes)\fP
¤È¤¤¤¦Ì¾Á°¤Î¥µ¥Ö¥»¥¯¥·¥ç¥ó (\fBSS\fP) ¤òÀߤ±¤ë¤ÈÊØÍø¤Ê¤³¤È¤â¤¢¤ë¡£
.TP
.\"O .B BUGS
.B ¥Ð¥° (BUGS)
.\"O lists limitations, known defects or inconveniences,
.\"O and other questionable activities.
À©¸Â¡¦ÃΤé¤ì¤Æ¤¤¤ë·ç´Ù¤äÉÔÊؤÊÅÀ¡¢¤½¤Î¾ÉԻ׵ĤÊÆ°ºî¤Ê¤É¤ò½ñ¤¯¡£
.TP
.\"O .B EXAMPLE
.B Îã (EXAMPLE)
.\"O provides one or more examples describing how this function, file or
.\"O command is used.
.\"O For details on writing example programs,
.\"O see \fIExample Programs\fP below.
¤³¤Î´Ø¿ô¡¦¥Õ¥¡¥¤¥ë¡¦¥³¥Þ¥ó¥É¤ò¤É¤Î¤è¤¦¤Ë»È¤¦¤«¤ò¼¨¤·¤¿
¤Ò¤È¤Ä¤Þ¤¿¤ÏÊ£¿ô¤ÎÎã¤òµ­½Ò¤¹¤ë¡£
¥µ¥ó¥×¥ë¥×¥í¥°¥é¥à¤ò½ñ¤¯ºÝ¤Î¾ÜºÙ¤Ï
°Ê²¼¤Î¡Ö¥µ¥ó¥×¥ë¥×¥í¥°¥é¥à¡×¤ÎÀá¤ò»²¾È¤Î¤³¤È¡£
.TP
.\"O .B AUTHORS
.B Ãø¼Ô (AUTHORS)
.\"O lists authors of the documentation or program.
ʸ½ñ¤Þ¤¿¤Ï¥×¥í¥°¥é¥à¤ÎÃø¼Ô¤òÎóµ­¤¹¤ë¡£
.\"O \fBUse of an AUTHORS section is strongly discouraged\fP.
.B Ãø¼Ô¥»¥¯¥·¥ç¥ó¤Ï¶ËÎÏ»ÈÍѤ·¤Ê¤¤¤³¤È¡£
.\"O Generally, it is better not to clutter every page with a list
.\"O of (over time potentially numerous) authors;
.\"O if you write or significantly amend a page,
.\"O add a copyright notice as a comment in the source file.
°ìÈÌŪ¤Ë¤Ï¡¢Ãø¼Ô¤Î¥ê¥¹¥È¤ò³Æ¥Ú¡¼¥¸¤Ë»µ¤­»¶¤é¤µ¤Ê¤¤Êý¤¬¤è¤¤
(»þ´Ö¤¬¤¿¤Ä¤È¡¢ºî¼Ô¤Î¥ê¥¹¥È¤ÏËÄÂç¤Ë¤Ê¤ë²ÄǽÀ­¤¬¤¢¤ë)¡£
¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò¿·µ¬¤Ë½ñ¤¤¤¿¤ê¡¢ÂçÉý¤Ë½¤Àµ¤ò¹Ô¤Ã¤¿¾ì¹ç¤Ë¤Ï¡¢
¥½¡¼¥¹¥Õ¥¡¥¤¥ë¤Ë¥³¥á¥ó¥È¤È¤·¤ÆÃøºî¸¢É½¼¨¤òÄɲ乤뤳¤È¡£
.\"O If you are the author of a device driver and what to include
.\"O an address for reporting bugs, place this under the BUGS section.
¤¢¤Ê¤¿¤¬¥Ç¥Ð¥¤¥¹¥É¥é¥¤¥Ð¤Îºî¼Ô¤Ç¡¢¥Ð¥°¤òÊó¹ð¤¹¤ë¤¿¤á¤Î¥¢¥É¥ì¥¹¤ò
ºÜ¤»¤¿¤¤¾ì¹ç¤Ï¡¢¡Ö¥Ð¥°¡×¥»¥¯¥·¥ç¥ó¤Î¸å¤í¤Ë¤³¤Î¥»¥¯¥·¥ç¥ó¤òÇÛÃÖ¤¹¤ë¤³¤È¡£
.TP
.\"O .B SEE ALSO
.B ´ØÏ¢¹àÌÜ (SEE ALSO)
.\"O provides a comma-separated list of related man pages,
.\"O ordered by section number and
.\"O then alphabetically by name, possibly followed by
.\"O other related pages or documents.
.\"O Do not terminate this with a period.
´ØÏ¢¤¹¤ë¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ò¡¢¥³¥ó¥Þ¶èÀÚ¤ê¤Î¥ê¥¹¥È¤Ç¡¢
¥»¥¯¥·¥ç¥óÈÖ¹æ½ç¤Ë¡¢¥»¥¯¥·¥ç¥óÆâ¤Ç¤Ï¥¢¥ë¥Õ¥¡¥Ù¥Ã¥È½ç¤Çµ­ºÜ¤¹¤ë¡£
²Äǽ¤Ê¤é´ØÏ¢¤¹¤ë¾¤Îʸ½ñ¤â½ñ¤¯¡£
´·½¬¤Ç¤Ï¡¢¤³¤Î¥»¥¯¥·¥ç¥ó¤ÏºÇ¸å¤ËÃÖ¤¯¡£
¥ê¥¹¥È¤ÎËöÈø¤Ë¥Ô¥ê¥ª¥É¤òÃÖ¤«¤Ê¤¤¤³¤È¡£
.\"O .SS Font conventions
.SS ¥Õ¥©¥ó¥È¤Î´·½¬
.PP
.\"O For functions, the arguments are always specified using italics,
.\"O .IR "even in the SYNOPSIS section" ,
.\"O where the rest of the function is specified in bold:
´Ø¿ô¤ËÂФ·¤Æ¤Ï¡¢°ú¤­¿ô¤Ë¤Ï¾ï¤Ë¥¤¥¿¥ê¥Ã¥¯ÂΤòÍѤ¤¤ë¡£
¡Ö¤¿¤È¤¨½ñ¼° (SYNOPSIS) ¥»¥¯¥·¥ç¥ó¤Ç¤¢¤Ã¤Æ¤â¡¢¤³¤Î¥ë¡¼¥ë¤Ë½¾¤¦¡×
´Ø¿ô¤Î¾¤ÎÉôʬ¤Ï¥Ü¡¼¥ë¥É¤ò»ØÄꤹ¤ë:
.PP
.BI "    int myfunction(int " argc ", char **" argv );
.PP
.\"O Variable names should, like argument names, be specified in italics.
°ú¤­¿ô̾¤È¤¤¤Ã¤¿ÊÑ¿ô̾¤Ï¥¤¥¿¥ê¥Ã¥¯ÂΤò»ØÄꤹ¤Ù¤­¤Ç¤¢¤ë¡£
.PP
.\"O Filenames (whether pathnames, or references to files in the
.\"O .I /usr/include
.\"O directory)
.\"O are always in italics (e.g.,
.\"O .IR <stdio.h> ),
.\"O except in the SYNOPSIS section, where included files are in bold (e.g.,
.\"O .BR "#include <stdio.h>" ).
¥Õ¥¡¥¤¥ë̾ (¥Ñ¥¹Ì¾¡¢¤Þ¤¿¤Ï
.I /usr/include
¥Ç¥£¥ì¥¯¥È¥êÆâ¤Î¥Õ¥¡¥¤¥ë¤Ø¤Î»²¾È) ¤Ï¾ï¤Ë¥¤¥¿¥ê¥Ã¥¯ÂΤˤ¹¤ë (Îã:
.IR <stdio.h> )¡£
¤¿¤À¤·¡¢½ñ¼° (SYNOPSIS) ¥»¥¯¥·¥ç¥ó¤ÏÎã³°¤Ç¡¢
¥¤¥ó¥¯¥ë¡¼¥É¥Õ¥¡¥¤¥ë¤Ï¥Ü¡¼¥ë¥É¤Ë¤¹¤ë (Îã:
.BR "#include <stdio.h>" )¡£
.\"O When referring to a standard include file under
.\"O .IR /usr/include ,
.\"O specify the header file surrounded by angle brackets,
.\"O in the usual C way (e.g.,
.\"O .IR <stdio.h> ).
.I /usr/include
°Ê²¼¤Îɸ½à¤Î¥¤¥ó¥¯¥ë¡¼¥É¥Õ¥¡¥¤¥ë¤ò»²¾È¤¹¤ëºÝ¤Ï¡¢
Ä̾ï¤Î C ¸À¸ì¤ÈƱÍͤ˻³³ç¸Ì¤Ç¥Ø¥Ã¥À¥Õ¥¡¥¤¥ë¤ò°Ï¤Ì¤Ç»ØÄꤹ¤ë (Î㡧
.IR <stdio.h> )¡£
.PP
.\"O Special macros, which are usually in upper case, are in bold (e.g.,
.\"O .BR MAXINT ).
.\"O Exception: don't boldface NULL.
Ä̾Âçʸ»ú¤Çɽ¸½¤¹¤ëÆüì¥Þ¥¯¥í¤Ï¥Ü¡¼¥ë¥É¤Çɽ¤¹ (Î㤨¤Ð
.BR MAXINT )¡£
Îã³°¤È¤·¤Æ NULL ¤Ï¥Ü¡¼¥ë¥É¤Ë¤·¤Ê¤¤¡£
.PP
.\"O When enumerating a list of error codes, the codes are in bold (this list
.\"O usually uses the
.\"O .B \&.TP
.\"O macro).
¥¨¥é¡¼¥³¡¼¥É¤Î¥ê¥¹¥È¤òÎóµó¤¹¤ë»þ¤Ë¤Ï¡¢¥³¡¼¥É¤Ï¥Ü¡¼¥ë¥É¤Çɽ¤¹
(¤³¤Î¥ê¥¹¥È¤Ë¤ÏÄ̾ï
.B \&.TP
¥Þ¥¯¥í¤òÍѤ¤¤ë)¡£
.PP
.\"O Complete commands should, if long,
.\"O be written as in an indented line on their own, for example
´°Á´¤Ê¥³¥Þ¥ó¥É¤Ï¡¢Ä¹¤¤¾ì¹ç¤Ë¤Ï¡¢Îã¤Ë¼¨¤¹¤è¤¦¤Ë
»ú²¼¤²¤·¤¿¹Ô¤Ë¥³¥Þ¥ó¥É¤À¤±¤òµ­ºÜ¤¹¤Ù¤­¤Ç¤¢¤ë¡£
.in +4n
.nf

man 7 man-pages

.fi
.in
.\"O If the command is short, then it can be included inline in the text,
.\"O in italic format, for example,
.\"O .IR "man 7 man-pages" .
.\"O In this case, it may be worth using nonbreaking spaces
.\"O ("\e\ ") at suitable places in the command.
.\"O Command options should be written in italics, e.g.,
.\"O .IR \-l .
¥³¥Þ¥ó¥É¤¬Ã»¤¤¾ì¹ç¤Ï¡¢
.I "man 7 man-pages"
¤Î¤è¤¦¤Ë¥¤¥¿¥ê¥Ã¥¯ÂΤÇʸÃæ¤ËËä¤á¹þ¤ó¤Çµ­ºÜ¤·¤Æ¤â¤è¤¤¡£
¤³¤Î¾ì¹ç¡¢¥³¥Þ¥ó¥ÉÆâ¤ÎŬÀڤʰÌÃ֤ˡ¢²þ¹Ô¤Ç¤­¤Ê¤¤¥¹¥Ú¡¼¥¹ ("\e\ ")
¤ò»È¤¦¤È¤è¤¤¤«¤â¤·¤ì¤Ê¤¤¡£
¥³¥Þ¥ó¥É¥ª¥×¥·¥ç¥ó¤â
.I \-l
¤Î¤è¤¦¤Ë¥¤¥¿¥ê¥Ã¥¯ÂΤǵ­ºÜ¤¹¤Ù¤­¤Ç¤¢¤ë¡£
.PP
.\"O Expressions, if not written on a separate indented line, should
.\"O be specified in italics.
.\"O Again, the use of nonbreaking spaces may be appropriate
.\"O if the expression is inlined with normal text.
¼°¤Ï¡¢ÀìÍѤλú²¼¤²¤·¤¿¹Ô¤Ëµ­ºÜ¤·¤Ê¤¤¾ì¹ç¡¢¥¤¥¿¥ê¥Ã¥¯ÂΤò»ØÄꤹ¤ë¤³¤È¡£
·«¤êÊÖ¤·¤Ë¤Ê¤ë¤¬¡¢¼°¤òÄ̾ï¤ÎʸÃæ¤ËËä¤á¹þ¤à¾ì¹ç¤Ë¤â¡¢
²þ¹Ô¤Ç¤­¤Ê¤¤¥¹¥Ú¡¼¥¹¤ò»È¤¦¤È¤è¤¤¤À¤í¤¦¡£
.PP
.\"O Any reference to the subject of the current manual page
.\"O should be written with the name in bold.
.\"O If the subject is a function (i.e., this is a Section 2 or 3 page),
.\"O then the name should be followed by a pair of parentheses
.\"O in Roman (normal) font.
.\"O For example, in the
.\"O .BR fcntl (2)
.\"O man page, references to the subject of the page would be written as:
.\"O .BR fcntl ().
.\"O The preferred way to write this in the source file is:
¤½¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ÎÀâÌÀÂоݤؤλ²¾È¤Ï¡¢¥Ü¡¼¥ë¥É¤Ç̾Á°¤òµ­ºÜ¤¹¤ë¡£
Âоݤ¬´Ø¿ô (¤Ä¤Þ¤ê¡¢¥»¥¯¥·¥ç¥ó 2 ¤ä 3 ¤Î¥Ú¡¼¥¸) ¤Î¾ì¹ç¡¢
̾Á°¤Î¸å¤í¤Ë¥í¡¼¥Þ¥ó¥Õ¥©¥ó¥È (Ä̾ï¤Î¥Õ¥©¥ó¥È) ¤Ç´Ý³ç¸Ì¤ÎÂФò³¤±¤ë¡£
Î㤨¤Ð¡¢
.BR fcntl (2)
¤Î¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ç¤Ï¡¢ÀâÌÀÂоݤؤλ²¾È¤Ï
.BR fcntl ()
¤Î¤è¤¦¤Ëµ­ºÜ¤¹¤ë¡£
¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Î¥½¡¼¥¹¥Õ¥¡¥¤¥ë¤Ë¤Ï¼¡¤Î¤è¤¦¤Ëµ­ºÜ¤¹¤ë¤Î¤¬Ë¾¤Þ¤·¤¤:
.nf

    .BR fcntl ()

.fi
.\"O (Using this format, rather than the use of "\\fB...\\fP()"
.\"O makes it easier to write tools that parse man page source files.)
("\\fB...\\fP()" ¤è¤ê¤â¡¢¤³¤Î·Á¼°¤ò»È¤¦¤³¤È¡£
¤³¤ì¤Ë¤è¤ê¡¢¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Î¥½¡¼¥¹¥Õ¥¡¥¤¥ë¤ò²ò¼á¤¹¤ë¥Ä¡¼¥ë¤ò
½ñ¤¯¤Î¤¬´Êñ¤Ë¤Ê¤ë¡£)
.PP
.\"O Any reference to another man page
.\"O should be written with the name in bold,
.\"O \fIalways\fP followed by the section number,
.\"O formatted in Roman (normal) font, without any
.\"O separating spaces (e.g.,
.\"O .BR intro (2)).
.\"O The preferred way to write this in the source file is:
Ê̤Υޥ˥奢¥ë¥Ú¡¼¥¸¤Ø¤Î»²¾È¤Ï¡¢¥Ü¡¼¥ë¥É¤Ç̾Á°¤òµ­ºÜ¤·¡¢
¤½¤ì¤Ë³¤±¤Æ¥»¥¯¥·¥ç¥óÈÖ¹æ¤ò¡Öɬ¤º¡×½ñ¤¯¡£¥»¥¯¥·¥ç¥óÈÖ¹æ¤Ï
¥í¡¼¥Þ¥ó¥Õ¥©¥ó¥È (Ä̾ï¤Î¥Õ¥©¥ó¥È) ¤Ç½ñ¤­¡¢¥¹¥Ú¡¼¥¹¤ÏÆþ¤ì¤Ê¤¤
(Îã:
.BR intro (2))¡£
¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Î¥½¡¼¥¹¥Õ¥¡¥¤¥ë¤Ë¤Ï¼¡¤Î¤è¤¦¤Ëµ­ºÜ¤¹¤ë¤Î¤¬Ë¾¤Þ¤·¤¤:
.nf

    .BR intro (2)

.fi
.\"O (Including the section number in cross references lets tools like
.\"O .BR man2html (1)
.\"O create properly hyperlinked pages.)
(Áê¸ß»²¾È¤Ë¥»¥¯¥·¥ç¥óÈÖ¹æ¤ò´Þ¤á¤Æ¤ª¤¯¤È¡¢
.B man2html
¤È¤¤¤Ã¤¿¥Ä¡¼¥ë¤¬¥Ú¡¼¥¸´Ö¤Î¥Ï¥¤¥Ñ¡¼¥ê¥ó¥¯¤òŬÀÚ¤ËÀ¸À®¤Ç¤­¤ë¡£)
.\"O .SS Spelling
.SS ÄÖ¤ê (spelling)
.\"O Starting with release 2.59,
.\"O .I man-pages
.\"O follows American spelling conventions;
.\"O please write all new pages and patches according to these conventions.
¥ê¥ê¡¼¥¹ 2.59 ¤«¤é¤À¤¬¡¢
.I man-pages
¤Ï¥¢¥á¥ê¥«±Ñ¸ì¤ÎÄÖ¤ê¤Î´·½¬¤Ë½¾¤Ã¤Æ¤¤¤ë¡£
¿·¤·¤¤¥Ú¡¼¥¸¤ä¥Ñ¥Ã¥Á¤ÏÁ´¤Æ¤³¤Î´·½¬¤Ë½¾¤Ã¤Æ²¼¤µ¤¤¡£
.\"O .SS Example Programs and Shell Sessions
.SS ¥µ¥ó¥×¥ë¥×¥í¥°¥é¥à¤È¥·¥§¥ë¤Î¥»¥Ã¥·¥ç¥ó
.\"O Manual pages can include example programs demonstrating how to
.\"O use a system call or library function.
.\"O However, note the following:
¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤Ë¤Ï¡¢¥·¥¹¥Æ¥à¥³¡¼¥ë¤ä¥é¥¤¥Ö¥é¥ê´Ø¿ô¤Î»È¤¤Êý¤ò¼¨¤¹
¥µ¥ó¥×¥ë¥×¥í¥°¥é¥à¤ò´Þ¤á¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
¤½¤ÎºÝ¤Ë¤Ï¡¢°Ê²¼¤ÎÅÀ¤Ëα°Õ¤¹¤Ù¤­¤Ç¤¢¤ë¡£
.TP 3
*
.\"O Example programs should be written in C.
¥µ¥ó¥×¥ë¥×¥í¥°¥é¥à¤Ï C ¤Çµ­ºÜ¤¹¤ë¤³¤È¡£
.TP
*
.\"O An example program is only necessary and useful if it demonstrates
.\"O something beyond what can easily be provided in a textual
.\"O description of the interface.
.\"O An example program that does nothing
.\"O other than call an interface usually serves little purpose.
¥µ¥ó¥×¥ë¥×¥í¥°¥é¥à¤Ï¡¢
¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ë¤Ä¤¤¤Æʸ¾Ï¤Ç´Êñ¤ËÀâÌÀ¤Ç¤­¤ë°Ê¾å¤Î¤³¤È¤ò¼¨¤¹¾ì¹ç¤Ë¤À¤±
ɬÍפ«¤ÄÍ­ÍѤǤ¢¤ë¡£¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤ò¸Æ¤Ó½Ð¤¹°Ê³°¤Ë²¿¤â¤·¤Ê¤¤¥µ¥ó¥×¥ë
¥×¥í¥°¥é¥à¤ÏÉáÄ̤ϤۤȤó¤ÉÌò¤ËΩ¤¿¤Ê¤¤¡£
.TP
*
.\"O Example programs should be fairly short (preferably less than 100 lines;
.\"O ideally less than 50 lines).
¥µ¥ó¥×¥ë¥×¥í¥°¥é¥à¤Ï¤«¤Ê¤êû¤á¤Ë¤¹¤ë¤³¤È
(100¹Ô̤Ëþ¤¬Ë¾¤Þ¤·¤¯¡¢50¹Ô̤Ëþ¤¬ÍýÁÛŪ¤Ç¤¢¤ë)¡£
.TP
*
.\"O Example programs should do error checking after system calls and
.\"O library function calls.
¥µ¥ó¥×¥ë¥×¥í¥°¥é¥à¤Ç¤Ï¡¢¥·¥¹¥Æ¥à¥³¡¼¥ë¤ä¥é¥¤¥Ö¥é¥ê´Ø¿ô¤ò¸Æ¤Ó½Ð¤·¤¿¸å¤Ç
¥¨¥é¡¼¥Á¥§¥Ã¥¯¤ò¹Ô¤¦¤³¤È¡£
.TP
*
.\"O Example programs should be complete, and compile without
.\"O warnings when compiled with \fIcc\ \-Wall\fP.
¥µ¥ó¥×¥ë¥×¥í¥°¥é¥à¤Ï´°·ë¤·¤Æ¤¤¤Æ¡¢
\fIcc\ \-Wall\fP
¤Ç¥³¥ó¥Ñ¥¤¥ë¤·¤¿ºÝ¤Ë·Ù¹ð¤Ê¤·¤Ç¥³¥ó¥Ñ¥¤¥ë¤Ç¤­¤ë¤³¤È¡£
.TP
*
.\"O Where possible and appropriate, example programs should allow
.\"O experimentation, by varying their behavior based on inputs
.\"O (ideally from command-line arguments, or alternatively, via
.\"O input read by the program).
²Äǽ¤«¤ÄŬÀڤʾì¹ç¤Ë¤Ï¡¢¥µ¥ó¥×¥ë¥×¥í¥°¥é¥à¤Ç
ÆþÎϤˤè¤êÆ°ºî¤òÊѲ½¤µ¤»¤ë¤Ê¤É¤Î¼Â¸³¤ò¹Ô¤¦¤È¤è¤¤
(ÍýÁÛŪ¤Ë¤Ï¡¢¥³¥Þ¥ó¥É¥é¥¤¥ó°ú¤­¿ô¤ä¡¢¥×¥í¥°¥é¥à¤¬Æɤ߹þ¤àÆþÎϥǡ¼¥¿
·Ðͳ¤Ç¡¢Æ°ºî¤òÊѲ½¤µ¤»¤ë¤Î¤¬¤è¤¤)¡£
.TP
*
.\"O Example programs should be laid out according to Kernighan and
.\"O Ritchie style, with 4-space indents.
¥µ¥ó¥×¥ë¥×¥í¥°¥é¥à¤Ï¡¢K&R (Kernighan and Ritchie) ¥¹¥¿¥¤¥ë¤Ç½ñ¤­¡¢
»ú²¼¤²¤Ï¥¹¥Ú¡¼¥¹ 4ʸ»ú¤Ç¹Ô¤¦¡£
.\"O (Avoid the use of TAB characters in source code!)
(¥½¡¼¥¹¥³¡¼¥É¤Ç TAB ʸ»ú¤ò»È¤¦¤Î¤ÏÈò¤±¤ë¤³¤È¡£)
.PP
.\"O For some examples of what example programs should look like, see
.\"O .BR wait (2)
.\"O and
.\"O .BR pipe (2).
¥µ¥ó¥×¥ë¥×¥í¥°¥é¥à¤¬¤É¤ó¤ÊÉ÷¤Ë¤Ê¤Ã¤Æ¤¤¤ì¤Ð¤è¤¤¤«¤ÎÎã¤Ë¤Ä¤¤¤Æ¤Ï¡¢
.BR wait (2)
¤È
.BR pipe (2)
¤ò»²¾È¤¹¤ë¤³¤È¡£

.\"O If you include a shell session demonstrating the use of a program
.\"O or other system feature, boldface the user input text,
.\"O to distinguish it from output produced by the system.
¥×¥í¥°¥é¥à¤Î»È¤¤Êý¤ä¾¤Î¥·¥¹¥Æ¥à¤ÎÆÃħ¤ò¼¨¤¹¤¿¤á¤Ë¥·¥§¥ë¤Î¥»¥Ã¥·¥ç¥óÎã
¤ò´Þ¤á¤ë¾ì¹ç¡¢¥æ¡¼¥¶¤ÎÆþÎÏʸ¤ò¥Ü¡¼¥ë¥É¤Ë¤·¤Æ¡¢¥·¥¹¥Æ¥à¤¬À¸À®¤¹¤ë
½ÐÎϤȶèÊ̤Ǥ­¤ë¤è¤¦¤Ë¤¹¤ë¤³¤È¡£
.\"O .SS Indentation of structure definitions, shell session logs, etc.
.SS ¹½Â¤ÂΤÎÄêµÁ¡¢¥·¥§¥ë¤Î¥»¥Ã¥·¥ç¥ó¥í¥°¤Ê¤É¤Î»ú²¼¤²
.\"O When structure definitions, shell session logs, etc. are included
.\"O in running text, indent them by 4 spaces (i.e., a block enclosed by
.\"O .I ".in\ +4n"
.\"O and
.\"O .IR ".in" ).
¹½Â¤ÂΤÎÄêµÁ¤ä¥·¥§¥ë¤Î¥»¥Ã¥·¥ç¥ó¥í¥°¤Ê¤É¤òËÜʸÃæ¤Ëµ­ºÜ¤¹¤ëºÝ¤Ï¡¢
¥¹¥Ú¡¼¥¹ 4¸Äʬ¤Î»ú²¼¤²¤ò¹Ô¤¦ (¤Ä¤Þ¤ê¡¢¥Ö¥í¥Ã¥¯¤ò
.I ".in\ +4n"
¤È
.I ".in"
¤Ç°Ï¤à)¡£
.\"O .SH EXAMPLE
.SH Îã
.\"O For canonical examples of how man pages in the
.\"O .I man-pages
.\"O package should look, see
.\"O .BR pipe (2)
.\"O and
.\"O .BR fcntl (2).
.I man-pages
¥Ñ¥Ã¥±¡¼¥¸¤Ë´Þ¤Þ¤ì¤ë¥Þ¥Ë¥å¥¢¥ë¥Ú¡¼¥¸¤ÎÂκۤÎɸ½àŪ¤ÊÎã¤Ë¤Ä¤¤¤Æ¤Ï¡¢
.BR pipe (2)
¤È
.BR fcntl (2)
¤ò»²¾È¤¹¤ë¤³¤È¡£
.\"O .SH SEE ALSO
.SH ´ØÏ¢¹àÌÜ
.BR man (1),
.BR man2html (1),
.BR groff (7),
.BR groff_man (7),
.BR man (7),
.BR mdoc (7)