JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... ded for older X servers which require access to all 65536 I/O ports. It is mostly for the i386 architecture. On many other architectures it does not exist or will always return an error. 返り値 成功した場合は 0 が返される。エラーの場合は -1 が返され、 errno が ... at a higher I/O privilege level. This will probably crash the system, and is not recommended. Prior to Linux 3.7, on some architectures (such as i386), permissions were inherited by the child produced by fork (2) and were preserved across execve (2). This be ... ... }; struct fd_pair pipe(); /* On all other architectures */ int pipe(int pipefd [2]); #define _GNU_SOURCE /* feature_test_macros (7) 参照 */ #include < fcntl.h > /* O_* 定数の定義 ... 以降で利用できる。 準拠 pipe (): POSIX.1-2001, POSIX.1-2008. pipe2 () は Linux 固有である。 注意 The System V ABI on some architectures allows the use of more than one register for returning multiple values; several architectures (namely, Alpha, IA-64, MIPS, ... ... }; struct fd_pair pipe(); /* On all other architectures */ int pipe(int pipefd [2]); #define _GNU_SOURCE /* feature_test_macros (7) 参照 */ #include < fcntl.h > /* O_* 定数の定義 ... 以降で利用できる。 準拠 pipe (): POSIX.1-2001, POSIX.1-2008. pipe2 () は Linux 固有である。 注意 The System V ABI on some architectures allows the use of more than one register for returning multiple values; several architectures (namely, Alpha, IA-64, MIPS, ... ... t1 R10 R00 - R01 1 x86-64 syscall rax rax rdx - 5 x32 syscall rax rax rdx - 5 xtensa syscall a2 a2 - - Notes: [1] On a few architectures, a register is used as a boolean (0 indicating no error, and -1 indicating an error) to signal that the system call failed ... kernel terms), but passes an 8-byte pos argument in a single register and not two, as is done in every other ABI. [6] Some architectures (namely, Alpha, IA-64, MIPS, SuperH, sparc/32, and sparc/64) use an additional register ("Retval2" in the above table) to ... pha uses this technique in the architecture-specific getxpid (2), getxuid (2), and getxgid (2) system calls as well. Other architectures do not use the second return value register in the system call interface, even if it is defined in the System V ABI. 2 つ目 ... ... set , int whence ); The C library's lseek () wrapper function uses the type off_t . This is a 32-bit signed type on 32-bit architectures, unless one compiles with #define _FILE_OFFSET_BITS 64 を定義してコンパイルした場合は 64 ビット符号付き型である。 lseek64( ... 可にできる。 Since glibc 2.28, this function symbol is no longer available to newly linked applications. _llseek() On 32-bit architectures, this is the system call that is used (by the C library wrapper functions) to implement all of the above functions. The pr ... ... wrapper function is provided.) Note: system calls indicate a failure by returning a negative error number to the caller on architectures without a separate error register/flag, as noted in syscall (2); when this happens, the wrapper function negates the retur ... がユーザー空間から使える状態になったことはない。 System calls on removed ports Some system calls only ever existed on Linux architectures that have since been removed from the kernel: AVR32 (port removed in Linux 4.12) * pread (2) * pwrite (2) Blackfin (port r ... the need to increase the size of structures or scalar values passed to the system call. Because of these changes, certain architectures (notably, longstanding 32-bit architectures such as i386) now have various groups of related system calls (e.g., truncate ... ... most PATH_MAX bytes. (Before Linux 3.12, the limit on the size of the returned pathname was the system page size. On many architectures, PATH_MAX and the system page size are both 4096 bytes, but a few architectures have a larger page size.) If the length of ... ... ) The memory should have strong access ordering. This feature is specific to the PowerPC architecture (version 2.06 of the architecture specification adds the SAO CPU feature, and it is available on POWER 7 or PowerPC A2, for example). Additionally (since Lin ... Apply the protection mode up to the end of a mapping that grows upwards. (Such mappings are created for the stack area on architectures---for example, HP-PARISC---that have an upwardly growing stack.) PROT_GROWSDOWN Apply the protection mode down to the begi ... e process's personality flags (see personality (2)), specifying PROT_READ will implicitly add PROT_EXEC . On some hardware architectures (e.g., i386), PROT_WRITE implies PROT_READ . POSIX.1 では、 prot で指定されていないアクセスを許可する実装を認めている。 た ... ... ) The memory should have strong access ordering. This feature is specific to the PowerPC architecture (version 2.06 of the architecture specification adds the SAO CPU feature, and it is available on POWER 7 or PowerPC A2, for example). Additionally (since Lin ... Apply the protection mode up to the end of a mapping that grows upwards. (Such mappings are created for the stack area on architectures---for example, HP-PARISC---that have an upwardly growing stack.) PROT_GROWSDOWN Apply the protection mode down to the begi ... e process's personality flags (see personality (2)), specifying PROT_READ will implicitly add PROT_EXEC . On some hardware architectures (e.g., i386), PROT_WRITE implies PROT_READ . POSIX.1 では、 prot で指定されていないアクセスを許可する実装を認めている。 た ... ... most PATH_MAX bytes. (Before Linux 3.12, the limit on the size of the returned pathname was the system page size. On many architectures, PATH_MAX and the system page size are both 4096 bytes, but a few architectures have a larger page size.) If the length of ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。