JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... は < sys/io.h > と < sys/perm.h > の両方にプロトタイプを持っている。 後者は i386 のみで利用可能なので、使用すべきではない。 Prior to Linux 5.5 iopl () allowed the thread to disable interrupts while running at a higher I/O privilege level. This will pro ... bably 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 ... ... the same guarantees as fsync () called on every file in the system or filesystem respectively. In mainline kernel versions prior to 5.8, syncfs () will fail only when passed a bad file descriptor ( EBADF ). Since Linux 5.8, syncfs () will also report ... ... the same guarantees as fsync () called on every file in the system or filesystem respectively. In mainline kernel versions prior to 5.8, syncfs () will fail only when passed a bad file descriptor ( EBADF ). Since Linux 5.8, syncfs () will also report ... ... an appreciable delay when requesting large amounts of data. When read during early boot time, /dev/urandom may return data prior to the entropy pool being initialized. If this is of concern in your application, use getrandom (2) or /dev/random instead ... hat can be used to obtain randomness, see random (7). バグ During early boot time, reads from /dev/urandom may return data prior to the entropy pool being initialized. 関連項目 mknod (1), getrandom (2), random (7) RFC 1750, "Randomness Recommendations ... ... an appreciable delay when requesting large amounts of data. When read during early boot time, /dev/urandom may return data prior to the entropy pool being initialized. If this is of concern in your application, use getrandom (2) or /dev/random instead ... hat can be used to obtain randomness, see random (7). バグ During early boot time, reads from /dev/urandom may return data prior to the entropy pool being initialized. 関連項目 mknod (1), getrandom (2), random (7) RFC 1750, "Randomness Recommendations ... ... a process nor to restrict filesystem system calls. In the past, chroot () has been used by daemons to restrict themselves prior to passing paths supplied by untrusted users to system calls such as open (2). However, if a folder is moved out of the ch ... ... 定義するには、 struct __user_cap_header_struct と struct __user_cap_data_struct という名前を使用しなければならない。 Kernels prior to 2.6.25 prefer 32-bit capabilities with version _LINUX_CAPABILITY_VERSION_1 . Linux 2.6.25 added 64-bit capability sets, ... ... 定義するには、 struct __user_cap_header_struct と struct __user_cap_data_struct という名前を使用しなければならない。 Kernels prior to 2.6.25 prefer 32-bit capabilities with version _LINUX_CAPABILITY_VERSION_1 . Linux 2.6.25 added 64-bit capability sets, ... ... e mount point may be remounted using a mount (2) call with a mount_flags argument that includes both MS_REC and MS_PRIVATE prior to umount () being called. Historical details 元々の umount () 関数は umount(device) の形で呼び出され、 ブロックデバイス以 ... ... e mount point may be remounted using a mount (2) call with a mount_flags argument that includes both MS_REC and MS_PRIVATE prior to umount () being called. Historical details 元々の umount () 関数は umount(device) の形で呼び出され、 ブロックデバイス以 ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。