JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... uction will instead generate a SIGSEGV signal. This feature can be used to emulate cpuid results that differ from what the underlying hardware would have produced (e.g., in a paravirtualization setting). The ARCH_SET_CPUID setting is preserved across fork ... が有効なサブコマンドでない。 EPERM addr がプロセスのアドレス空間の外にある。 ENODEV ARCH_SET_CPUID was requested, but the underlying hardware does not support CPUID faulting. 準拠 arch_prctl () は Linux/x86-64 拡張であり、移植性を意図したプログラムでは使う ... ... 超えている。 EINTR 実行中にシグナルが捕捉された。 EINVAL offset was less than 0, or len was less than or equal to 0, or the underlying filesystem does not support the operation. ENODEV fd が通常のファイルとして参照されていない。 ENOSPC fd が参照するファイル ... the glibc implementation, posix_fallocate () is implemented using the fallocate (2) system call, which is MT-safe. If the underlying filesystem does not support fallocate (2), then the operation is emulated with the following caveats: * The emulation is i ... ... て整った状態で (上述の linkat (2) を使って) ファイルシステム内にアトミックにリンクを行う。 O_TMPFILE requires support by the underlying filesystem; only a subset of Linux filesystems provide that support. In the initial implementation, support was provided i ... the final component ("basename") of the new file's pathname is invalid (e.g., it contains characters not permitted by the underlying filesystem). EINVAL The final component ("basename") of pathname is invalid (e.g., it contains characters not permitted by ... the underlying filesystem). EISDIR pathname はディレクトリを参照しており、書き込み要求が含まれていた (つまり O_WRONLY または O_RDWR が設定 ... ... て整った状態で (上述の linkat (2) を使って) ファイルシステム内にアトミックにリンクを行う。 O_TMPFILE requires support by the underlying filesystem; only a subset of Linux filesystems provide that support. In the initial implementation, support was provided i ... the final component ("basename") of the new file's pathname is invalid (e.g., it contains characters not permitted by the underlying filesystem). EINVAL The final component ("basename") of pathname is invalid (e.g., it contains characters not permitted by ... the underlying filesystem). EISDIR pathname はディレクトリを参照しており、書き込み要求が含まれていた (つまり O_WRONLY または O_RDWR が設定 ... ... て整った状態で (上述の linkat (2) を使って) ファイルシステム内にアトミックにリンクを行う。 O_TMPFILE requires support by the underlying filesystem; only a subset of Linux filesystems provide that support. In the initial implementation, support was provided i ... the final component ("basename") of the new file's pathname is invalid (e.g., it contains characters not permitted by the underlying filesystem). EINVAL The final component ("basename") of pathname is invalid (e.g., it contains characters not permitted by ... the underlying filesystem). EISDIR pathname はディレクトリを参照しており、書き込み要求が含まれていた (つまり O_WRONLY または O_RDWR が設定 ... ... エラーを返す。 RENAME_NOREPLACE can't be employed together with RENAME_EXCHANGE . RENAME_NOREPLACE requires support from the underlying filesystem. Support for various filesystems was added as follows: * ext4 (Linux 3.15); * btrfs, shmem, cifs (Linux 3.17); ... D capability). RENAME_WHITEOUT can't be employed together with RENAME_EXCHANGE . RENAME_WHITEOUT requires support from the underlying filesystem. Among the filesystems that provide that support are tmpfs (since Linux 3.18), ext4 (since Linux 3.18), XFS (si ... ... エラーを返す。 RENAME_NOREPLACE can't be employed together with RENAME_EXCHANGE . RENAME_NOREPLACE requires support from the underlying filesystem. Support for various filesystems was added as follows: * ext4 (Linux 3.15); * btrfs, shmem, cifs (Linux 3.17); ... D capability). RENAME_WHITEOUT can't be employed together with RENAME_EXCHANGE . RENAME_WHITEOUT requires support from the underlying filesystem. Among the filesystems that provide that support are tmpfs (since Linux 3.18), ext4 (since Linux 3.18), XFS (si ... ... エラーを返す。 RENAME_NOREPLACE can't be employed together with RENAME_EXCHANGE . RENAME_NOREPLACE requires support from the underlying filesystem. Support for various filesystems was added as follows: * ext4 (Linux 3.15); * btrfs, shmem, cifs (Linux 3.17); ... D capability). RENAME_WHITEOUT can't be employed together with RENAME_EXCHANGE . RENAME_WHITEOUT requires support from the underlying filesystem. Among the filesystems that provide that support are tmpfs (since Linux 3.18), ext4 (since Linux 3.18), XFS (si ... ... _GNU_SOURCE 説明 sync () causes all pending modifications to filesystem metadata and cached file data to be written to the underlying filesystems. syncfs () は sync () と同様だが、オープンされたファイルディスクリプター fd が参照するファイルを含むファイルシ ... ... _GNU_SOURCE 説明 sync () causes all pending modifications to filesystem metadata and cached file data to be written to the underlying filesystems. syncfs () は sync () と同様だが、オープンされたファイルディスクリプター fd が参照するファイルを含むファイルシ ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。