JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... 構造体を定義するには、 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 ... the problem. 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 wa ... ile extended 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 ... ... 構造体を定義するには、 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 ... the problem. 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 wa ... ile extended 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 ... ... s system call no longer exists on current kernels! See NOTES. _sysctl () コールはカーネルパラメーターを読み書きする。例えば、 ホストネームや同時にオープンできるファイルの最 ... kernel log, and in Linux 5.5, the system call was finally removed. Use the /proc/sys interface instead. Note that on older kernels where this system call still exists, it is available only if the kernel was configured with the CONFIG_SYSCTL_SYSCALL opti ... ... s system call no longer exists on current kernels! See NOTES. _sysctl () コールはカーネルパラメーターを読み書きする。例えば、 ホストネームや同時にオープンできるファイルの最 ... kernel log, and in Linux 5.5, the system call was finally removed. Use the /proc/sys interface instead. Note that on older kernels where this system call still exists, it is available only if the kernel was configured with the CONFIG_SYSCTL_SYSCALL opti ... ... days ram disks use the buffer cache, and grow dynamically. For a lot of information on the current ramdisk setup, see the kernel source file Documentation/blockdev/ramdisk.txt ( Documentation/ramdisk.txt in older kernels). 4 つのパラメーターがある。論理 ... ブートシーケンス (具体的には /sbin/init の呼び出し) が実行される。 For a detailed description of the initrd feature, see the kernel source file Documentation/admin-guide/initrd.rst (or Documentation/initrd.txt before Linux 4.10). 'noinitrd' オプションを用 ... ons, the 'hd=' option will be cited for brevity. See the file Documentation/ide/ide.txt (or Documentation/ide.txt in older kernels, or drivers/block/README.ide in ancient kernels) in the Linux kernel source for more details. 'hd=cyls,heads,sects[,wpcom[ ... ... ore/somaxconn , then it is silently truncated to that value. Since Linux 5.4, the default in this file is 4096; in earlier kernels, the default value is 128. In kernels before 2.4.25, this limit was a hard coded value, SOMAXCONN , with the value 128. 例 ... ... エラー EBADF fd が有効なファイルディスクリプターではない。 ENOTTY fd refers to a file other than a terminal. On some older kernels, some types of files resulted in the error EINVAL in this case (which is a violation of POSIX, which specifies the error E ... ... 5.3.0, the pipe template is split on spaces into an argument list before the template parameters are expanded. In earlier kernels, the template parameters are expanded first and the resulting string is split on spaces into an argument list. This means ... that in earlier kernels executable names added by the %e and %E template parameters could get split into multiple arguments. So the core dump hand ... f the executable name using spaces. Executable names with multiple spaces in them are not correctly represented in earlier kernels, meaning that the core dump handler needs to use mechanisms to find the executable name. コアダンプは、ファイルに書き込まれ ... ... concept and the setfsgid () system call were invented for historical reasons that are no longer applicable on modern Linux kernels. See setfsuid (2) for a discussion of why the use of both setfsuid (2) and setfsgid () is nowadays unneeded. 元々の Linux ... ... concept and the setfsgid () system call were invented for historical reasons that are no longer applicable on modern Linux kernels. See setfsuid (2) for a discussion of why the use of both setfsuid (2) and setfsgid () is nowadays unneeded. 元々の Linux ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。