JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... tomary, the proc filesystem is mounted on /proc , you can find in the file /proc/filesystems which filesystems your kernel currently supports; see proc (5) for more details. There is also a legacy sysfs (2) system call (whose availability is controlled by ... the CONFIG_SYSFS_SYSCALL kernel build configuration option since Linux 3.15) that enables enumeration of the currently available filesystem types regardless of /proc availability and/or sanity. If you need a currently unsupported filesystem, ... ... tomary, the proc filesystem is mounted on /proc , you can find in the file /proc/filesystems which filesystems your kernel currently supports; see proc (5) for more details. There is also a legacy sysfs (2) system call (whose availability is controlled by ... the CONFIG_SYSFS_SYSCALL kernel build configuration option since Linux 3.15) that enables enumeration of the currently available filesystem types regardless of /proc availability and/or sanity. If you need a currently unsupported filesystem, ... ... tion (in order to guarantee the ability to perform atomic operations required by commands such as FUTEX_WAIT ), but is not currently used in on any architecture. PROT_SAO (Linux 2.6.26 以降) The memory should have strong access ordering. This feature is s ... tection) exceeding the allowed maximum. (For example, making the protection of a range PROT_READ in the middle of a region currently protected as PROT_READ|PROT_WRITE would result in three mappings: two read/write mappings at each end and a read-only mapp ... ... tion (in order to guarantee the ability to perform atomic operations required by commands such as FUTEX_WAIT ), but is not currently used in on any architecture. PROT_SAO (Linux 2.6.26 以降) The memory should have strong access ordering. This feature is s ... tection) exceeding the allowed maximum. (For example, making the protection of a range PROT_READ in the middle of a region currently protected as PROT_READ|PROT_WRITE would result in three mappings: two read/write mappings at each end and a read-only mapp ... ... クションを使うこと。 -c , --combine combine consecutive rules with the same matches but different targets. iptables does not currently support more than one target per match, so this simulates that by collecting the targets from consecutive iptables rules i ... ... ows block-based filesystems to use polling of the device, which provides lower latency, but may use additional resources. (Currently, this feature is usable only on a file descriptor opened using the O_DIRECT flag.) RWF_SYNC (Linux 4.7 以降) Provide a per ... essfully read, it will return the number of bytes read. If no bytes were read, it will return -1 and set errno to EAGAIN . Currently, this flag is meaningful only for preadv2 (). RWF_APPEND (Linux 4.16 以降) Provide a per-write equivalent of the O_APPEND ... ... ows block-based filesystems to use polling of the device, which provides lower latency, but may use additional resources. (Currently, this feature is usable only on a file descriptor opened using the O_DIRECT flag.) RWF_SYNC (Linux 4.7 以降) Provide a per ... essfully read, it will return the number of bytes read. If no bytes were read, it will return -1 and set errno to EAGAIN . Currently, this flag is meaningful only for preadv2 (). RWF_APPEND (Linux 4.16 以降) Provide a per-write equivalent of the O_APPEND ... ... ows block-based filesystems to use polling of the device, which provides lower latency, but may use additional resources. (Currently, this feature is usable only on a file descriptor opened using the O_DIRECT flag.) RWF_SYNC (Linux 4.7 以降) Provide a per ... essfully read, it will return the number of bytes read. If no bytes were read, it will return -1 and set errno to EAGAIN . Currently, this flag is meaningful only for preadv2 (). RWF_APPEND (Linux 4.16 以降) Provide a per-write equivalent of the O_APPEND ... ... ows block-based filesystems to use polling of the device, which provides lower latency, but may use additional resources. (Currently, this feature is usable only on a file descriptor opened using the O_DIRECT flag.) RWF_SYNC (Linux 4.7 以降) Provide a per ... essfully read, it will return the number of bytes read. If no bytes were read, it will return -1 and set errno to EAGAIN . Currently, this flag is meaningful only for preadv2 (). RWF_APPEND (Linux 4.16 以降) Provide a per-write equivalent of the O_APPEND ... ... ows block-based filesystems to use polling of the device, which provides lower latency, but may use additional resources. (Currently, this feature is usable only on a file descriptor opened using the O_DIRECT flag.) RWF_SYNC (Linux 4.7 以降) Provide a per ... essfully read, it will return the number of bytes read. If no bytes were read, it will return -1 and set errno to EAGAIN . Currently, this flag is meaningful only for preadv2 (). RWF_APPEND (Linux 4.16 以降) Provide a per-write equivalent of the O_APPEND ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。