JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... Note that 64-bit capabilities use datap[0] and datap[1] , whereas 32-bit capabilities use only datap[0] . On kernels that support file capabilities (VFS capabilities support), these system calls behave slightly differently. This support was added as an ... ended attribute (see xattr (7)) to allow capabilities to be attached to executables. This privilege model obsoletes kernel support for one process asynchronously setting the capabilities of another. That is, on kernels that have VFS capabilities support ... returned by gettid (2). VFS ケーパビリティがサポートされていない場合 On older kernels that do not provide VFS capabilities support capset () can, if the caller has the CAP_SETPCAP capability, be used to change not only the caller's own capabilities, but ... ... Note that 64-bit capabilities use datap[0] and datap[1] , whereas 32-bit capabilities use only datap[0] . On kernels that support file capabilities (VFS capabilities support), these system calls behave slightly differently. This support was added as an ... ended attribute (see xattr (7)) to allow capabilities to be attached to executables. This privilege model obsoletes kernel support for one process asynchronously setting the capabilities of another. That is, on kernels that have VFS capabilities support ... returned by gettid (2). VFS ケーパビリティがサポートされていない場合 On older kernels that do not provide VFS capabilities support capset () can, if the caller has the CAP_SETPCAP capability, be used to change not only the caller's own capabilities, but ... ... でに存在する場合エラーを返す。 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); * xfs (Linux 4.0); * Support for many other filesystems was added in Linux 4.9, including ext2, minix, reiserfs, jfs, vfat, and bpf. RENAME_WHITEOUT (L ... t methods for storing whiteout entries; specifically, BSD union mount employs a separate inode type, DT_WHT , which, while supported by some filesystems available in Linux, such as CODA and XFS, is ignored by the kernel's whiteout support code, as of Li ... ... でに存在する場合エラーを返す。 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); * xfs (Linux 4.0); * Support for many other filesystems was added in Linux 4.9, including ext2, minix, reiserfs, jfs, vfat, and bpf. RENAME_WHITEOUT (L ... t methods for storing whiteout entries; specifically, BSD union mount employs a separate inode type, DT_WHT , which, while supported by some filesystems available in Linux, such as CODA and XFS, is ignored by the kernel's whiteout support code, as of Li ... ... でに存在する場合エラーを返す。 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); * xfs (Linux 4.0); * Support for many other filesystems was added in Linux 4.9, including ext2, minix, reiserfs, jfs, vfat, and bpf. RENAME_WHITEOUT (L ... t methods for storing whiteout entries; specifically, BSD union mount employs a separate inode type, DT_WHT , which, while supported by some filesystems available in Linux, such as CODA and XFS, is ignored by the kernel's whiteout support code, as of Li ... ... ナルが捕捉された。 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 が参照するファイルを含むデバイスに十分な空き領 ... 域がない。 EOPNOTSUPP The filesystem containing the file referred to by fd does not support this operation. This error code can be returned by C libraries that don't perform the emulation shown in NOTES, such as mu ... x_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 inefficient. * There is a rac ... ... nux libc4 was the last version to use the a.out binary format, and the first version to provide (primitive) shared library support. Linux libc 5 was the first version to support the ELF binary format; this version used the shared library soname libc.so. ... ... nux libc4 was the last version to use the a.out binary format, and the first version to provide (primitive) shared library support. Linux libc 5 was the first version to support the ELF binary format; this version used the shared library soname libc.so. ... ... スに割り当てられたアドレス空間の外を指している。 EINVAL Either the value specified in how was invalid or the kernel does not support the size passed in sigsetsize. 準拠 POSIX.1-2001, POSIX.1-2008. 注意 SIGKILL や SIGSTOP を禁止することはできない。 禁止しよ ... l-time signals in Linux 2.2, the fixed-size, 32-bit sigset_t (referred to as old_kernel_sigset_t in this manual page) type supported by that system call was no longer fit for purpose. Consequently, a new system call, rt_sigprocmask (), was added to supp ... ... スに割り当てられたアドレス空間の外を指している。 EINVAL Either the value specified in how was invalid or the kernel does not support the size passed in sigsetsize. 準拠 POSIX.1-2001, POSIX.1-2008. 注意 SIGKILL や SIGSTOP を禁止することはできない。 禁止しよ ... l-time signals in Linux 2.2, the fixed-size, 32-bit sigset_t (referred to as old_kernel_sigset_t in this manual page) type supported by that system call was no longer fit for purpose. Consequently, a new system call, rt_sigprocmask (), was added to supp ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。