JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... TEXT は空文字列である。 view NAME TYPE SUBTREE [MASK] このディレクティブは指定した名前のビュー (view) を定義する。 TYPE は included または excluded である。 MASK は 16 進数で表した 8 ビットを '.' または ':' で区切ってリストにしたものである。 MASK が指定さ ... とにある。 例えば、ISP ではそれぞれの顧客に対して 顧客ごとのインタフェースにアクセスさせたいと考えるかもしれない: view cust1 included interfaces.ifTable.ifEntry.ifIndex.1 ff.a0 view cust2 included interfaces.ifTable.ifEntry.ifIndex.2 ff.a0 (interfaces.ifTa ... p local usm local group public v1 public group public v2c public group public usm public # incl/excl subtree mask view all included .1 80 view system included system fe view mib2 included .iso.org.dod.internet.mgmt.mib-2 fc # context sec.model sec.level ... ... ted to an event. An additional record of type FAN_EVENT_INFO_TYPE_FID encapsulates the information about the object and is included alongside the generic event metadata structure. The file descriptor that is used to represent the object correlated to an ... vent. An additional record of type FAN_EVENT_INFO_TYPE_DFID encapsulates the information about the directory object and is included alongside the generic event metadata structure. For events that occur on a non-directory object, the additional structure ... additional record of type FAN_EVENT_INFO_TYPE_DFID_NAME , which encapsulates the information about the directory entry, is included alongside the generic event metadata structure and substitutes the additional information record of type FAN_EVENT_INFO_TY ... ... /usr/bin (in that order) and may also include the current working directory. On some other systems, the current working is included after /bin and /usr/bin , as an anti-Trojan-horse measure. The glibc implementation long followed the traditional default ... where the current working directory is included at the start of the search path. However, some code refactoring during the development of glibc 2.24 caused the current wo ... ... /usr/bin (in that order) and may also include the current working directory. On some other systems, the current working is included after /bin and /usr/bin , as an anti-Trojan-horse measure. The glibc implementation long followed the traditional default ... where the current working directory is included at the start of the search path. However, some code refactoring during the development of glibc 2.24 caused the current wo ... ... /usr/bin (in that order) and may also include the current working directory. On some other systems, the current working is included after /bin and /usr/bin , as an anti-Trojan-horse measure. The glibc implementation long followed the traditional default ... where the current working directory is included at the start of the search path. However, some code refactoring during the development of glibc 2.24 caused the current wo ... ... /usr/bin (in that order) and may also include the current working directory. On some other systems, the current working is included after /bin and /usr/bin , as an anti-Trojan-horse measure. The glibc implementation long followed the traditional default ... where the current working directory is included at the start of the search path. However, some code refactoring during the development of glibc 2.24 caused the current wo ... ... /usr/bin (in that order) and may also include the current working directory. On some other systems, the current working is included after /bin and /usr/bin , as an anti-Trojan-horse measure. The glibc implementation long followed the traditional default ... where the current working directory is included at the start of the search path. However, some code refactoring during the development of glibc 2.24 caused the current wo ... ... /usr/bin (in that order) and may also include the current working directory. On some other systems, the current working is included after /bin and /usr/bin , as an anti-Trojan-horse measure. The glibc implementation long followed the traditional default ... where the current working directory is included at the start of the search path. However, some code refactoring during the development of glibc 2.24 caused the current wo ... ... /usr/bin (in that order) and may also include the current working directory. On some other systems, the current working is included after /bin and /usr/bin , as an anti-Trojan-horse measure. The glibc implementation long followed the traditional default ... where the current working directory is included at the start of the search path. However, some code refactoring during the development of glibc 2.24 caused the current wo ... ... pectively, 2 MB, 1 GB, ...) on systems that support multiple hugetlb page sizes. Definitions for known huge page sizes are included in the header file < linux/memfd.h >. For details on encoding huge page sizes not included in the header file, see the dis ... 合、-1 を返し、 errno にエラーを示す値を設定する。 エラー EFAULT name のアドレスが無効なメモリーを指している。 EINVAL flags included unknown bits. EINVAL name was too long. (The limit is 249 bytes, excluding the terminating null byte.) EINVAL Both MFD_HUG ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。