2016-09-19 08:07:56 -03:00
.. _changes:
2016-10-26 16:34:09 -06:00
Minimal requirements to compile the Kernel
2016-09-19 08:07:42 -03:00
++++++++++++++++++++++++++++++++++++++++++
2005-04-16 15:20:36 -07:00
Intro
=====
This document is designed to provide a list of the minimum levels of
2022-04-19 11:48:52 -03:00
software necessary to run the current kernel version.
2005-04-16 15:20:36 -07:00
This document is originally based on my "Changes" file for 2.0.x kernels
and therefore owes credit to the same people as that file (Jared Mauch,
Axel Boldt, Alessandro Sigala, and countless other users all over the
'net).
Current Minimal Requirements
2016-09-19 08:07:42 -03:00
***** ***** ***** ***** ***** ***
2005-04-16 15:20:36 -07:00
2016-09-19 08:07:42 -03:00
Upgrade to at **least** these software revisions before thinking you've
2005-04-16 15:20:36 -07:00
encountered a bug! If you're unsure what version you're currently
running, the suggested command should tell you.
2011-07-11 16:48:38 -07:00
Again, keep in mind that this list assumes you are already functionally
running a Linux kernel. Also, not all tools are necessary on all
2019-04-18 22:43:36 +02:00
systems; obviously, if you don't have any PC Card hardware, for example,
you probably needn't concern yourself with pcmciautils.
2005-04-16 15:20:36 -07:00
2016-09-19 08:07:42 -03:00
====================== =============== ========================================
Program Minimal version Command to check the version
====================== =============== ========================================
2021-09-10 16:40:38 -07:00
GNU C 5.1 gcc --version
kbuild: raise the minimum supported version of LLVM to 13.0.1
Patch series "Bump the minimum supported version of LLVM to 13.0.1".
This series bumps the minimum supported version of LLVM for building the
kernel to 13.0.1. The first patch does the bump and all subsequent
patches clean up all the various workarounds and checks for earlier
versions.
Quoting the first patch's commit message for those that were only on CC
for the clean ups:
When __builtin_mul_overflow() has arguments that differ in terms of
signedness and width, LLVM may generate a libcall to __muloti4 because
it performs the checks in terms of 65-bit multiplication. This issue
becomes harder to hit (but still possible) after LLVM 12.0.0, which
includes a special case for matching widths but different signs.
To gain access to this special case, which the kernel can take advantage
of when calls to __muloti4 appear, bump the minimum supported version of
LLVM for building the kernel to 13.0.1. 13.0.1 was chosen because there
is minimal impact to distribution support while allowing a few more
workarounds to be dropped in the kernel source than if 12.0.0 were
chosen. Looking at container images of up to date distribution versions:
archlinux:latest clang version 16.0.6
debian:oldoldstable-slim clang version 7.0.1-8+deb10u2 (tags/RELEASE_701/final)
debian:oldstable-slim Debian clang version 11.0.1-2
debian:stable-slim Debian clang version 14.0.6
debian:testing-slim Debian clang version 16.0.6 (19)
debian:unstable-slim Debian clang version 16.0.6 (19)
fedora:38 clang version 16.0.6 (Fedora 16.0.6-3.fc38)
fedora:latest clang version 17.0.6 (Fedora 17.0.6-1.fc39)
fedora:rawhide clang version 17.0.6 (Fedora 17.0.6-1.fc40)
opensuse/leap:latest clang version 15.0.7
opensuse/tumbleweed:latest clang version 17.0.6
ubuntu:focal clang version 10.0.0-4ubuntu1
ubuntu:latest Ubuntu clang version 14.0.0-1ubuntu1.1
ubuntu:rolling Ubuntu clang version 16.0.6 (15)
ubuntu:devel Ubuntu clang version 17.0.6 (3)
The only distribution that gets left behind is Debian Bullseye, as the
default version is 11.0.1; other distributions either have a newer
version than 13.0.1 or one older than the current minimum of 11.0.0.
Debian has easy access to more recent LLVM versions through
apt.llvm.org, so this is not as much of a concern. There are also the
kernel.org LLVM toolchains, which should work with distributions with
glibc 2.28 and newer.
Another benefit of slimming up the number of supported versions of LLVM
for building the kernel is reducing the build capacity needed to support
a matrix that builds with each supported version, which allows a matrix
to reallocate the freed up build capacity towards something else, such
as more configuration combinations.
This passes my build matrix with all supported versions.
This is based on Andrew's mm-nonmm-unstable to avoid trivial conflicts
with my series to update the LLVM links across the repository [1] but I
can easily rebase it to linux-kbuild if Masahiro would rather these
patches go through there (and defer the conflict resolution to the merge
window).
[1]: https://lore.kernel.org/20240109-update-llvm-links-v1-0-eb09b59db071@kernel.org/
This patch (of 11):
When __builtin_mul_overflow() has arguments that differ in terms of
signedness and width, LLVM may generate a libcall to __muloti4 because it
performs the checks in terms of 65-bit multiplication. This issue becomes
harder to hit (but still possible) after LLVM 12.0.0, which includes a
special case for matching widths but different signs.
To gain access to this special case, which the kernel can take advantage
of when calls to __muloti4 appear, bump the minimum supported version of
LLVM for building the kernel to 13.0.1. 13.0.1 was chosen because there
is minimal impact to distribution support while allowing a few more
workarounds to be dropped in the kernel source than if 12.0.0 were chosen.
Looking at container images of up to date distribution versions:
archlinux:latest clang version 16.0.6
debian:oldoldstable-slim clang version 7.0.1-8+deb10u2 (tags/RELEASE_701/final)
debian:oldstable-slim Debian clang version 11.0.1-2
debian:stable-slim Debian clang version 14.0.6
debian:testing-slim Debian clang version 16.0.6 (19)
debian:unstable-slim Debian clang version 16.0.6 (19)
fedora:38 clang version 16.0.6 (Fedora 16.0.6-3.fc38)
fedora:latest clang version 17.0.6 (Fedora 17.0.6-1.fc39)
fedora:rawhide clang version 17.0.6 (Fedora 17.0.6-1.fc40)
opensuse/leap:latest clang version 15.0.7
opensuse/tumbleweed:latest clang version 17.0.6
ubuntu:focal clang version 10.0.0-4ubuntu1
ubuntu:latest Ubuntu clang version 14.0.0-1ubuntu1.1
ubuntu:rolling Ubuntu clang version 16.0.6 (15)
ubuntu:devel Ubuntu clang version 17.0.6 (3)
The only distribution that gets left behind is Debian Bullseye, as the
default version is 11.0.1; other distributions either have a newer version
than 13.0.1 or one older than the current minimum of 11.0.0. Debian has
easy access to more recent LLVM versions through apt.llvm.org, so this is
not as much of a concern. There are also the kernel.org LLVM toolchains,
which should work with distributions with glibc 2.28 and newer.
Another benefit of slimming up the number of supported versions of LLVM
for building the kernel is reducing the build capacity needed to support a
matrix that builds with each supported version, which allows a matrix to
reallocate the freed up build capacity towards something else, such as
more configuration combinations.
Link: https://lkml.kernel.org/r/20240125-bump-min-llvm-ver-to-13-0-1-v1-0-f5ff9bda41c5@kernel.org
Closes: https://github.com/ClangBuiltLinux/linux/issues/1975
Link: https://github.com/llvm/llvm-project/issues/38013
Link: https://github.com/llvm/llvm-project/commit/3203143f1356a4e4e3ada231156fc6da6e1a9f9d
Link: https://mirrors.edge.kernel.org/pub/tools/llvm/
Link: https://lkml.kernel.org/r/20240125-bump-min-llvm-ver-to-13-0-1-v1-1-f5ff9bda41c5@kernel.org
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Reviewed-by: Kees Cook <keescook@chromium.org>
Cc: Albert Ou <aou@eecs.berkeley.edu>
Cc: "Aneesh Kumar K.V (IBM)" <aneesh.kumar@kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>
Cc: Borislav Petkov (AMD) <bp@alien8.de>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Conor Dooley <conor@kernel.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Nathan Chancellor <nathan@kernel.org>
Cc: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
Cc: Nicholas Piggin <npiggin@gmail.com>
Cc: Nicolas Schier <nicolas@fjasle.eu>
Cc: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Russell King <linux@armlinux.org.uk>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Will Deacon <will@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2024-01-25 15:55:07 -07:00
Clang/LLVM (optional) 13.0.1 clang --version
rust: upgrade to Rust 1.78.0
This is the next upgrade to the Rust toolchain, from 1.77.1 to 1.78.0
(i.e. the latest) [1].
See the upgrade policy [2] and the comments on the first upgrade in
commit 3ed03f4da06e ("rust: upgrade to Rust 1.68.2").
It is much smaller than previous upgrades, since the `alloc` fork was
dropped in commit 9d0441bab775 ("rust: alloc: remove our fork of the
`alloc` crate") [3].
# Unstable features
There have been no changes to the set of unstable features used in
our own code. Therefore, the only unstable features allowed to be used
outside the `kernel` crate is still `new_uninit`.
However, since we finally dropped our `alloc` fork [3], all the unstable
features used by `alloc` (~30 language ones, ~60 library ones) are not
a concern anymore. This reduces the maintenance burden, increases the
chances of new compiler versions working without changes and gets us
closer to the goal of supporting several compiler versions.
It also means that, ignoring non-language/library features, we are
currently left with just the few language features needed to implement the
kernel `Arc`, the `new_uninit` library feature, the `compiler_builtins`
marker and the few `no_*` `cfg`s we pass when compiling `core`/`alloc`.
Please see [4] for details.
# Required changes
## LLVM's data layout
Rust 1.77.0 (i.e. the previous upgrade) introduced a check for matching
LLVM data layouts [5]. Then, Rust 1.78.0 upgraded LLVM's bundled major
version from 17 to 18 [6], which changed the data layout in x86 [7]. Thus
update the data layout in our custom target specification for x86 so
that the compiler does not complain about the mismatch:
error: data-layout for target `target-5559158138856098584`,
`e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128`,
differs from LLVM target's `x86_64-linux-gnu` default layout,
`e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-i128:128-f80:128-n8:16:32:64-S128`
In the future, the goal is to drop the custom target specifications.
Meanwhile, if we want to support other LLVM versions used in `rustc`
(e.g. for LTO), we will need to add some extra logic (e.g. conditional on
LLVM's version, or extracting the data layout from an existing built-in
target specification).
## `unused_imports`
Rust's `unused_imports` lint covers both unused and redundant imports.
Now, in 1.78.0, the lint detects more cases of redundant imports [8].
Thus one of the previous patches cleaned them up.
## Clippy's `new_without_default`
Clippy now suggests to implement `Default` even when `new()` is `const`,
since `Default::default()` may call `const` functions even if it is not
`const` itself [9]. Thus one of the previous patches implemented it.
# Other changes in Rust
Rust 1.78.0 introduced `feature(asm_goto)` [10] [11]. This feature was
discussed in the past [12].
Rust 1.78.0 introduced `feature(const_refs_to_static)` [13] to allow
referencing statics in constants and extended `feature(const_mut_refs)`
to allow raw mutable pointers in constants. Together, this should cover
the kernel's `VTABLE` use case. In fact, the implementation [14] in
upstream Rust added a test case for it [15].
Rust 1.78.0 with debug assertions enabled (i.e. `-Cdebug-assertions=y`,
kernel's `CONFIG_RUST_DEBUG_ASSERTIONS=y`) now always checks all unsafe
preconditions, though without a way to opt-out for particular cases [16].
It would be ideal to have a way to selectively disable certain checks
per-call site for this one (i.e. not just per check but for particular
instances of a check), even if the vast majority of the checks remain
in place [17].
Rust 1.78.0 also improved a couple issues we reported when giving feedback
for the new `--check-cfg` feature [18] [19].
# `alloc` upgrade and reviewing
As mentioned above, compiler upgrades will not update `alloc` anymore,
since we dropped our `alloc` fork [3].
Link: https://github.com/rust-lang/rust/blob/stable/RELEASES.md#version-1780-2024-05-02 [1]
Link: https://rust-for-linux.com/rust-version-policy [2]
Link: https://lore.kernel.org/rust-for-linux/20240328013603.206764-1-wedsonaf@gmail.com/ [3]
Link: https://github.com/Rust-for-Linux/linux/issues/2 [4]
Link: https://github.com/rust-lang/rust/pull/120062 [5]
Link: https://github.com/rust-lang/rust/pull/120055 [6]
Link: https://reviews.llvm.org/D86310 [7]
Link: https://github.com/rust-lang/rust/pull/117772 [8]
Link: https://github.com/rust-lang/rust-clippy/pull/10903 [9]
Link: https://github.com/rust-lang/rust/pull/119365 [10]
Link: https://github.com/rust-lang/rust/issues/119364 [11]
Link: https://lore.kernel.org/rust-for-linux/ZWipTZysC2YL7qsq@Boquns-Mac-mini.home/ [12]
Link: https://github.com/rust-lang/rust/issues/119618 [13]
Link: https://github.com/rust-lang/rust/pull/120932 [14]
Link: https://github.com/rust-lang/rust/pull/120932/files#diff-e6fc1622c46054cd46b1d225c5386c5554564b3b0fa8a03c2dc2d8627a1079d9 [15]
Link: https://github.com/rust-lang/rust/issues/120969 [16]
Link: https://github.com/Rust-for-Linux/linux/issues/354 [17]
Link: https://github.com/rust-lang/rust/pull/121202 [18]
Link: https://github.com/rust-lang/rust/pull/121237 [19]
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
Link: https://lore.kernel.org/r/20240401212303.537355-4-ojeda@kernel.org
[ Added a few more details and links I mentioned in the list. - Miguel ]
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2024-04-01 23:23:03 +02:00
Rust (optional) 1.78.0 rustc --version
rust: bindgen: upgrade to 0.65.1
In LLVM 16, anonymous items may return names like `(unnamed union at ..)`
rather than empty names [1], which breaks Rust-enabled builds because
bindgen assumed an empty name instead of detecting them via
`clang_Cursor_isAnonymous` [2]:
$ make rustdoc LLVM=1 CLIPPY=1 -j$(nproc)
RUSTC L rust/core.o
BINDGEN rust/bindings/bindings_generated.rs
BINDGEN rust/bindings/bindings_helpers_generated.rs
BINDGEN rust/uapi/uapi_generated.rs
thread 'main' panicked at '"ftrace_branch_data_union_(anonymous_at__/_/include/linux/compiler_types_h_146_2)" is not a valid Ident', .../proc-macro2-1.0.24/src/fallback.rs:693:9
...
thread 'main' panicked at '"ftrace_branch_data_union_(anonymous_at__/_/include/linux/compiler_types_h_146_2)" is not a valid Ident', .../proc-macro2-1.0.24/src/fallback.rs:693:9
...
This was fixed in bindgen 0.62.0. Therefore, upgrade bindgen to
a more recent version, 0.65.1, to support LLVM 16.
Since bindgen 0.58.0 changed the `--{white,black}list-*` flags to
`--{allow,block}list-*` [3], update them on our side too.
In addition, bindgen 0.61.0 moved its CLI utility into a binary crate
called `bindgen-cli` [4]. Thus update the installation command in the
Quick Start guide.
Moreover, bindgen 0.61.0 changed the default functionality to bind
`size_t` to `usize` [5] and added the `--no-size_t-is-usize` flag
to not bind `size_t` as `usize`. Then bindgen 0.65.0 removed
the `--size_t-is-usize` flag [6]. Thus stop passing the flag to bindgen.
Finally, bindgen 0.61.0 added support for the `noreturn` attribute (in
its different forms) [7]. Thus remove the infinite loop in our Rust
panic handler after calling `BUG()`, since bindgen now correctly
generates a `BUG()` binding that returns `!` instead of `()`.
Link: https://github.com/llvm/llvm-project/commit/19e984ef8f49bc3ccced15621989fa9703b2cd5b [1]
Link: https://github.com/rust-lang/rust-bindgen/pull/2319 [2]
Link: https://github.com/rust-lang/rust-bindgen/pull/1990 [3]
Link: https://github.com/rust-lang/rust-bindgen/pull/2284 [4]
Link: https://github.com/rust-lang/rust-bindgen/commit/cc78b6fdb6e829e5fb8fa1639f2182cb49333569 [5]
Link: https://github.com/rust-lang/rust-bindgen/pull/2408 [6]
Link: https://github.com/rust-lang/rust-bindgen/issues/2094 [7]
Signed-off-by: Aakash Sen Sharma <aakashsensharma@gmail.com>
Closes: https://github.com/Rust-for-Linux/linux/issues/1013
Tested-by: Ariel Miculas <amiculas@cisco.com>
Reviewed-by: Gary Guo <gary@garyguo.net>
Link: https://lore.kernel.org/r/20230612194311.24826-1-aakashsensharma@gmail.com
[ Reworded commit message. Mentioned the `bindgen-cli` binary crate
change, linked to it and updated the Quick Start guide. Re-added a
deleted "as" word in a code comment and reflowed comment to respect
the maximum length. ]
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2023-06-13 01:13:11 +05:30
bindgen (optional) 0.65.1 bindgen --version
2022-10-02 05:28:35 +09:00
GNU make 3.82 make --version
scripts/check-local-export: avoid 'wait $!' for process substitution
Bash 4.4, released in 2016, supports 'wait $!' to check the exit status
of a process substitution, but it seems too new.
Some people using older bash versions (on CentOS 7, Ubuntu 16.04, etc.)
reported an error like this:
./scripts/check-local-export: line 54: wait: pid 17328 is not a child of this shell
I used the process substitution to avoid a pipeline, which executes each
command in a subshell. If the while-loop is executed in the subshell
context, variable changes within are lost after the subshell terminates.
Fortunately, Bash 4.2, released in 2011, supports the 'lastpipe' option,
which makes the last element of a pipeline run in the current shell process.
Switch to the pipeline with 'lastpipe' solution, and also set 'pipefail'
to catch errors from ${NM}.
Add the bash requirement to Documentation/process/changes.rst.
Fixes: 31cb50b5590f ("kbuild: check static EXPORT_SYMBOL* by script instead of modpost")
Reported-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Reported-by: Michael Ellerman <mpe@ellerman.id.au>
Reported-by: Wang Yugui <wangyugui@e16-tech.com>
Tested-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Acked-by: Nick Desaulniers <ndesaulniers@google.com>
Tested-by: Sedat Dilek <sedat.dilek@gmail.com> # LLVM-14 (x86-64)
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2022-06-08 10:11:00 +09:00
bash 4.2 bash --version
2022-10-13 03:18:41 +09:00
binutils 2.25 ld -v
kbuild: prepare to remove C files pre-generated by flex and bison
In Linux build system convention, pre-generated files are version-
controlled with a "_shipped" suffix. During the kernel building,
they are simply shipped (copied) removing the suffix.
This approach can reduce external tool dependency for the kernel build,
but it is tedious to manually regenerate such artifacts from developers'
point of view. (We need to do "make REGENERATE_PARSERS=1" every time
we touch real source files such as *.l, *.y)
Some months ago, I sent out RFC patches to run flex, bison, and gperf
during the build.
In the review and test, Linus noticed gperf-3.1 had changed the lookup
function prototype. Then, the use of gperf in kernel was entirely
removed by commit bb3290d91695 ("Remove gperf usage from toolchain").
This time, I tested several versions of flex and bison, and I was not
hit by any compatibility issue except a flaw in flex-2.6.3; if you
generate lexer for dtc and genksyms with flex-2.6.3, you will see
"yywrap redefined" warning. This was not intentional, but a bug,
fixed by flex-2.6.4. Otherwise, both flex and bison look fairly
stable for a long time.
This commit prepares some build rules to remove the _shipped files.
Also, document minimal requirement for flex and bison.
Rationale for the minimal version:
The -Wmissing-prototypes option of GCC warns "no previous prototype"
for lexers generated by flex-2.5.34 or older, so I chose 2.5.35 as the
required version for flex. Flex-2.5.35 was released in 2008. Bison
looks more stable. I did not see any problem with bison-2.0, released
in 2004. I did not test bison-1.x, but bison-2.0 should be old enough.
Tested flex versions:
2.5.35
2.5.36
2.5.37
2.5.39
2.6.0
2.6.1
2.6.2
2.6.3 (*)
2.6.4
(*) flex-2.6.3 causes "yywrap redefined" warning
Tested bison versions:
2.0
2.1
2.2
2.3
2.4
2.4.1
2.5.1
2.6
2.6.1
2.6.2
2.6.3
2.6.4
2.6.5
2.7
2.7.1
3.0
3.0.1
3.0.2
3.0.3
3.0.4
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2017-12-10 01:02:29 +09:00
flex 2.5.35 flex --version
bison 2.0 bison --version
2021-11-19 15:56:03 -03:00
pahole 1.16 pahole --version
2023-12-20 06:02:49 +01:00
util-linux 2.10o mount --version
2018-07-01 19:46:06 -07:00
kmod 13 depmod -V
2016-09-19 08:07:42 -03:00
e2fsprogs 1.41.4 e2fsck -V
jfsutils 1.1.3 fsck.jfs -V
reiserfsprogs 3.6.3 reiserfsck -V
xfsprogs 2.6.0 xfs_db -V
squashfs-tools 4.0 mksquashfs -version
btrfs-progs 0.18 btrfsck
pcmciautils 004 pccardctl -V
quota-tools 3.09 quota -V
PPP 2.4.0 pppd --version
nfs-utils 1.0.5 showmount --version
procps 3.2.0 ps --version
udev 081 udevd --version
grub 0.93 grub --version || grub-install --version
mcelog 0.6 mcelog --version
iptables 1.4.2 iptables -V
openssl & libcrypto 1.0.0 openssl version
bc 1.06.95 bc --version
2023-12-08 16:10:17 -07:00
Sphinx\ [#f1]_ 2.4.4 sphinx-build --version
2022-04-19 11:48:15 -03:00
cpio any cpio --version
2023-05-21 22:23:36 +09:00
GNU tar 1.28 tar --version
2023-05-15 19:32:17 +02:00
gtags (optional) 6.6.5 gtags --version
2024-03-29 16:28:36 +13:00
mkimage (optional) 2017.01 mkimage --version
2016-09-19 08:07:42 -03:00
====================== =============== ========================================
2009-12-14 14:52:10 +01:00
2016-09-19 08:07:43 -03:00
.. [#f1] Sphinx is needed only to build the Kernel documentation
2005-04-16 15:20:36 -07:00
Kernel compilation
2016-09-19 08:07:42 -03:00
***** ***** ***** ***
2005-04-16 15:20:36 -07:00
GCC
---
The gcc version requirements may vary depending on the type of CPU in your
2006-01-08 01:04:09 -08:00
computer.
2005-04-16 15:20:36 -07:00
2020-08-26 12:15:55 -07:00
Clang/LLVM (optional)
---------------------
The latest formal release of clang and LLVM utils (according to
`releases.llvm.org <https://releases.llvm.org> `_ ) are supported for building
kernels. Older releases aren't guaranteed to work, and we may drop workarounds
from the kernel that were used to support older versions. Please see additional
docs on :ref: `Building Linux with Clang/LLVM <kbuild_llvm>` .
2021-07-03 17:23:16 +02:00
Rust (optional)
---------------
A particular version of the Rust toolchain is required. Newer versions may or
may not work because the kernel depends on some unstable Rust features, for
the moment.
Each Rust toolchain comes with several "components", some of which are required
(like `` rustc `` ) and some that are optional. The `` rust-src `` component (which
is optional) needs to be installed to build the kernel. Other components are
useful for developing.
Please see Documentation/rust/quick-start.rst for instructions on how to
satisfy the build requirements of Rust support. In particular, the `` Makefile ``
target `` rustavailable `` is useful to check why the Rust toolchain may not
be detected.
bindgen (optional)
------------------
`` bindgen `` is used to generate the Rust bindings to the C side of the kernel.
It depends on `` libclang `` .
2005-04-16 15:20:36 -07:00
Make
----
2022-10-02 05:28:35 +09:00
You will need GNU make 3.82 or later to build the kernel.
2005-04-16 15:20:36 -07:00
scripts/check-local-export: avoid 'wait $!' for process substitution
Bash 4.4, released in 2016, supports 'wait $!' to check the exit status
of a process substitution, but it seems too new.
Some people using older bash versions (on CentOS 7, Ubuntu 16.04, etc.)
reported an error like this:
./scripts/check-local-export: line 54: wait: pid 17328 is not a child of this shell
I used the process substitution to avoid a pipeline, which executes each
command in a subshell. If the while-loop is executed in the subshell
context, variable changes within are lost after the subshell terminates.
Fortunately, Bash 4.2, released in 2011, supports the 'lastpipe' option,
which makes the last element of a pipeline run in the current shell process.
Switch to the pipeline with 'lastpipe' solution, and also set 'pipefail'
to catch errors from ${NM}.
Add the bash requirement to Documentation/process/changes.rst.
Fixes: 31cb50b5590f ("kbuild: check static EXPORT_SYMBOL* by script instead of modpost")
Reported-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Reported-by: Michael Ellerman <mpe@ellerman.id.au>
Reported-by: Wang Yugui <wangyugui@e16-tech.com>
Tested-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Acked-by: Nick Desaulniers <ndesaulniers@google.com>
Tested-by: Sedat Dilek <sedat.dilek@gmail.com> # LLVM-14 (x86-64)
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2022-06-08 10:11:00 +09:00
Bash
----
Some bash scripts are used for the kernel build.
Bash 4.2 or newer is needed.
2005-04-16 15:20:36 -07:00
Binutils
--------
2022-10-13 03:18:41 +09:00
Binutils 2.25 or newer is needed to build the kernel.
2005-04-16 15:20:36 -07:00
2018-06-28 16:39:50 -07:00
pkg-config
----------
The build system, as of 4.18, requires pkg-config to check for installed
kconfig tools and to determine flags settings for use in
kconfig: do not require pkg-config on make {menu,n}config
Meelis Roos reported a {menu,n}config regression:
"I have libncurses devel package installed in the default system
location (as do 99%+ on actual developers probably) and in this
case, pkg-config is useless. pkg-config is needed only when
libraries and headers are installed in non-default locations but
it is bad to require installation of pkg-config on all the machines
where make menuconfig would be possibly run."
For {menu,n}config, do not use pkg-config if it is not installed.
For {g,x}config, keep checking pkg-config since we really rely on it
for finding the installation paths of the required packages.
Fixes: 4ab3b80159d4 ("kconfig: check for pkg-config on make {menu,n,g,x}config")
Reported-by: Meelis Roos <mroos@linux.ee>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Tested-by: Meelis Roos <mroos@linux.ee>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
2018-08-31 18:34:55 +09:00
'make {g,x}config'. Previously pkg-config was being used but not
2018-06-28 16:39:50 -07:00
verified or documented.
kbuild: prepare to remove C files pre-generated by flex and bison
In Linux build system convention, pre-generated files are version-
controlled with a "_shipped" suffix. During the kernel building,
they are simply shipped (copied) removing the suffix.
This approach can reduce external tool dependency for the kernel build,
but it is tedious to manually regenerate such artifacts from developers'
point of view. (We need to do "make REGENERATE_PARSERS=1" every time
we touch real source files such as *.l, *.y)
Some months ago, I sent out RFC patches to run flex, bison, and gperf
during the build.
In the review and test, Linus noticed gperf-3.1 had changed the lookup
function prototype. Then, the use of gperf in kernel was entirely
removed by commit bb3290d91695 ("Remove gperf usage from toolchain").
This time, I tested several versions of flex and bison, and I was not
hit by any compatibility issue except a flaw in flex-2.6.3; if you
generate lexer for dtc and genksyms with flex-2.6.3, you will see
"yywrap redefined" warning. This was not intentional, but a bug,
fixed by flex-2.6.4. Otherwise, both flex and bison look fairly
stable for a long time.
This commit prepares some build rules to remove the _shipped files.
Also, document minimal requirement for flex and bison.
Rationale for the minimal version:
The -Wmissing-prototypes option of GCC warns "no previous prototype"
for lexers generated by flex-2.5.34 or older, so I chose 2.5.35 as the
required version for flex. Flex-2.5.35 was released in 2008. Bison
looks more stable. I did not see any problem with bison-2.0, released
in 2004. I did not test bison-1.x, but bison-2.0 should be old enough.
Tested flex versions:
2.5.35
2.5.36
2.5.37
2.5.39
2.6.0
2.6.1
2.6.2
2.6.3 (*)
2.6.4
(*) flex-2.6.3 causes "yywrap redefined" warning
Tested bison versions:
2.0
2.1
2.2
2.3
2.4
2.4.1
2.5.1
2.6
2.6.1
2.6.2
2.6.3
2.6.4
2.6.5
2.7
2.7.1
3.0
3.0.1
3.0.2
3.0.3
3.0.4
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2017-12-10 01:02:29 +09:00
Flex
----
Since Linux 4.16, the build system generates lexical analyzers
during build. This requires flex 2.5.35 or later.
Bison
-----
Since Linux 4.16, the build system generates parsers
during build. This requires bison 2.0 or later.
2024-02-05 01:01:17 +01:00
pahole
------
2021-11-19 15:56:03 -03:00
Since Linux 5.2, if CONFIG_DEBUG_INFO_BTF is selected, the build system
generates BTF (BPF Type Format) from DWARF in vmlinux, a bit later from kernel
modules as well. This requires pahole v1.16 or later.
It is found in the 'dwarves' or 'pahole' distro packages or from
https://fedorapeople.org/~acme/dwarves/.
2009-06-17 16:26:30 -07:00
Perl
----
2016-09-19 08:07:42 -03:00
You will need perl 5 and the following modules: `` Getopt::Long `` ,
`` Getopt::Std `` , `` File::Basename `` , and `` File::Find `` to build the kernel.
2009-06-17 16:26:30 -07:00
2014-05-19 14:02:17 +01:00
BC
--
You will need bc to build kernels 3.10 and higher
2009-06-17 16:26:30 -07:00
2015-08-27 11:13:36 +01:00
OpenSSL
-------
Module signing and external certificate handling use the OpenSSL program and
crypto library to do key creation and signature generation.
You will need openssl to build kernels 3.7 and higher if module signing is
enabled. You will also need openssl development packages to build kernels 4.3
and higher.
2023-05-21 22:23:36 +09:00
Tar
---
GNU tar is needed if you want to enable access to the kernel headers via sysfs
(CONFIG_IKHEADERS).
2023-05-15 19:32:17 +02:00
gtags / GNU GLOBAL (optional)
-----------------------------
The kernel build requires GNU GLOBAL version 6.6.5 or later to generate
tag files through `` make gtags `` . This is due to its use of the gtags
`` -C (--directory) `` flag.
2015-08-27 11:13:36 +01:00
2024-03-29 16:28:36 +13:00
mkimage
-------
This tool is used when building a Flat Image Tree (FIT), commonly used on ARM
platforms. The tool is available via the `` u-boot-tools `` package or can be
built from the U-Boot source code. See the instructions at
https://docs.u-boot.org/en/latest/build/tools.html#building-tools-for-linux
2005-04-16 15:20:36 -07:00
System utilities
2016-09-19 08:07:42 -03:00
***** ***** ***** *
2005-04-16 15:20:36 -07:00
Architectural changes
---------------------
DevFS has been obsoleted in favour of udev
2020-06-21 15:36:30 +02:00
(https://www.kernel.org/pub/linux/utils/kernel/hotplug/)
2005-04-16 15:20:36 -07:00
32-bit UID support is now in place. Have fun!
Linux documentation for functions is transitioning to inline
documentation via specially-formatted comments near their
2017-05-14 11:50:11 -03:00
definitions in the source. These comments can be combined with ReST
files the Documentation/ directory to make enriched documentation, which can
then be converted to PostScript, HTML, LaTex, ePUB and PDF files.
In order to convert from ReST format to a format of your choice, you'll need
Sphinx.
2005-04-16 15:20:36 -07:00
Util-linux
----------
2016-09-19 08:07:42 -03:00
New versions of util-linux provide `` fdisk `` support for larger disks,
2005-04-16 15:20:36 -07:00
support new options to mount, recognize more supported partition
2023-12-20 06:02:49 +01:00
types, and similar goodies.
2005-04-16 15:20:36 -07:00
You'll probably want to upgrade.
Ksymoops
--------
2005-11-07 01:01:03 -08:00
If the unthinkable happens and your kernel oopses, you may need the
ksymoops tool to decode it, but in most cases you don't.
2016-09-19 08:07:42 -03:00
It is generally preferred to build the kernel with `` CONFIG_KALLSYMS `` so
2011-07-11 16:48:38 -07:00
that it produces readable dumps that can be used as-is (this also
produces better output than ksymoops). If for some reason your kernel
2016-09-19 08:07:42 -03:00
is not build with `` CONFIG_KALLSYMS `` and you have no way to rebuild and
2011-07-11 16:48:38 -07:00
reproduce the Oops with that option, then you can still decode that Oops
with ksymoops.
2005-04-16 15:20:36 -07:00
Mkinitrd
--------
2016-09-19 08:07:42 -03:00
These changes to the `` /lib/modules `` file tree layout also require that
2005-04-16 15:20:36 -07:00
mkinitrd be upgraded.
E2fsprogs
---------
2016-09-19 08:07:42 -03:00
The latest version of `` e2fsprogs `` fixes several bugs in fsck and
2005-04-16 15:20:36 -07:00
debugfs. Obviously, it's a good idea to upgrade.
JFSutils
--------
2016-09-19 08:07:42 -03:00
The `` jfsutils `` package contains the utilities for the file system.
2005-04-16 15:20:36 -07:00
The following utilities are available:
2016-09-19 08:07:42 -03:00
- `` fsck.jfs `` - initiate replay of the transaction log, and check
2005-04-16 15:20:36 -07:00
and repair a JFS formatted partition.
2016-09-19 08:07:42 -03:00
- `` mkfs.jfs `` - create a JFS formatted partition.
- other file system utilities are also available in this package.
2005-04-16 15:20:36 -07:00
Reiserfsprogs
-------------
The reiserfsprogs package should be used for reiserfs-3.6.x
(Linux kernels 2.4.x). It is a combined package and contains working
2016-09-19 08:07:42 -03:00
versions of `` mkreiserfs `` , `` resize_reiserfs `` , `` debugreiserfs `` and
`` reiserfsck `` . These utils work on both i386 and alpha platforms.
2005-04-16 15:20:36 -07:00
Xfsprogs
--------
2016-09-19 08:07:42 -03:00
The latest version of `` xfsprogs `` contains `` mkfs.xfs `` , `` xfs_db `` , and the
`` xfs_repair `` utilities, among others, for the XFS filesystem. It is
2005-04-16 15:20:36 -07:00
architecture independent and any version from 2.0.0 onward should
work correctly with this version of the XFS kernel code (2.6.0 or
later is recommended, due to some significant improvements).
2005-06-27 16:28:45 -07:00
PCMCIAutils
-----------
2016-09-19 08:07:42 -03:00
PCMCIAutils replaces `` pcmcia-cs `` . It properly sets up
2005-06-27 16:28:45 -07:00
PCMCIA sockets at system startup and loads the appropriate modules
for 16-bit PCMCIA devices if the kernel is modularized and the hotplug
subsystem is used.
2005-04-16 15:20:36 -07:00
Quota-tools
-----------
Support for 32 bit uid's and gid's is required if you want to use
the newer version 2 quota format. Quota-tools version 3.07 and
newer has this support. Use the recommended version or newer
from the table above.
Intel IA32 microcode
--------------------
A driver has been added to allow updating of Intel IA32 microcode,
2005-06-20 21:15:16 -07:00
accessible as a normal (misc) character device. If you are not using
2016-09-20 18:46:36 -06:00
udev you may need to::
2016-09-19 08:07:42 -03:00
mkdir /dev/cpu
mknod /dev/cpu/microcode c 10 184
chmod 0644 /dev/cpu/microcode
2005-04-16 15:20:36 -07:00
as root before you can use this. You'll probably also want to
get the user-space microcode_ctl utility to use with this.
udev
----
2016-09-19 08:07:42 -03:00
`` udev `` is a userspace application for populating `` /dev `` dynamically with
only entries for devices actually present. `` udev `` replaces the basic
2006-11-30 05:32:19 +01:00
functionality of devfs, while allowing persistent device naming for
2005-06-20 21:15:16 -07:00
devices.
2005-04-16 15:20:36 -07:00
2005-09-27 21:45:20 -07:00
FUSE
----
Needs libfuse 2.4.0 or later. Absolute minimum is 2.3.0 but mount
2016-09-19 08:07:42 -03:00
options `` direct_io `` and `` kernel_cache `` won't work.
2005-09-27 21:45:20 -07:00
2005-04-16 15:20:36 -07:00
Networking
2016-09-19 08:07:42 -03:00
***** *****
2005-04-16 15:20:36 -07:00
General changes
---------------
If you have advanced network configuration needs, you should probably
consider using the network tools from ip-route2.
Packet Filter / NAT
-------------------
The packet filtering and NAT code uses the same tools like the previous 2.4.x
kernel series (iptables). It still includes backwards-compatibility modules
for 2.2.x-style ipchains and 2.0.x-style ipfwadm.
PPP
---
The PPP driver has been restructured to support multilink and to
enable it to operate over diverse media layers. If you use PPP,
upgrade pppd to at least 2.4.0.
2005-06-20 21:15:16 -07:00
If you are not using udev, you must have the device file /dev/ppp
2016-09-20 18:46:36 -06:00
which can be made by::
2016-09-19 08:07:42 -03:00
mknod /dev/ppp c 108 0
2005-04-16 15:20:36 -07:00
as root.
NFS-utils
---------
2011-07-11 16:48:38 -07:00
In ancient (2.4 and earlier) kernels, the nfs server needed to know
about any client that expected to be able to access files via NFS. This
2016-09-19 08:07:42 -03:00
information would be given to the kernel by `` mountd `` when the client
mounted the filesystem, or by `` exportfs `` at system startup. exportfs
would take information about active clients from `` /var/lib/nfs/rmtab `` .
2005-04-16 15:20:36 -07:00
This approach is quite fragile as it depends on rmtab being correct
which is not always easy, particularly when trying to implement
2016-09-19 08:07:42 -03:00
fail-over. Even when the system is working well, `` rmtab `` suffers from
2005-04-16 15:20:36 -07:00
getting lots of old entries that never get removed.
2011-07-11 16:48:38 -07:00
With modern kernels we have the option of having the kernel tell mountd
when it gets a request from an unknown host, and mountd can give
appropriate export information to the kernel. This removes the
2016-09-19 08:07:42 -03:00
dependency on `` rmtab `` and means that the kernel only needs to know about
2011-07-11 16:48:38 -07:00
currently active clients.
2005-04-16 15:20:36 -07:00
2016-09-20 18:46:36 -06:00
To enable this new functionality, you need to::
2016-09-19 08:07:42 -03:00
2006-09-11 12:39:19 -04:00
mount -t nfsd nfsd /proc/fs/nfsd
2005-04-16 15:20:36 -07:00
before running exportfs or mountd. It is recommended that all NFS
services be protected from the internet-at-large by a firewall where
that is possible.
2009-04-28 23:37:02 +02:00
mcelog
------
2014-07-12 09:54:52 -07:00
On x86 kernels the mcelog utility is needed to process and log machine check
2016-09-19 08:07:42 -03:00
events when `` CONFIG_X86_MCE `` is enabled. Machine check events are errors
reported by the CPU. Processing them is strongly encouraged.
2009-04-28 23:37:02 +02:00
2016-09-19 08:07:43 -03:00
Kernel documentation
***** ***** ***** *****
Sphinx
------
2018-11-21 01:35:19 +01:00
Please see :ref: `sphinx_install` in :ref: `Documentation/doc-guide/sphinx.rst <sphinxdoc>`
2017-07-14 13:41:17 -03:00
for details about Sphinx requirements.
2016-09-19 08:07:43 -03:00
2021-07-03 17:23:16 +02:00
rustdoc
-------
`` rustdoc `` is used to generate the documentation for Rust code. Please see
Documentation/rust/general-information.rst for more information.
2005-04-16 15:20:36 -07:00
Getting updated software
========================
Kernel compilation
***** ***** ***** ***
2006-01-08 01:04:09 -08:00
gcc
---
2016-09-19 08:07:42 -03:00
- <ftp://ftp.gnu.org/gnu/gcc/>
2005-04-16 15:20:36 -07:00
2020-08-26 12:15:55 -07:00
Clang/LLVM
----------
- :ref: `Getting LLVM <getting_llvm>` .
2021-07-03 17:23:16 +02:00
Rust
----
- Documentation/rust/quick-start.rst.
bindgen
-------
- Documentation/rust/quick-start.rst.
2005-04-16 15:20:36 -07:00
Make
----
2016-09-19 08:07:42 -03:00
- <ftp://ftp.gnu.org/gnu/make/>
2005-04-16 15:20:36 -07:00
scripts/check-local-export: avoid 'wait $!' for process substitution
Bash 4.4, released in 2016, supports 'wait $!' to check the exit status
of a process substitution, but it seems too new.
Some people using older bash versions (on CentOS 7, Ubuntu 16.04, etc.)
reported an error like this:
./scripts/check-local-export: line 54: wait: pid 17328 is not a child of this shell
I used the process substitution to avoid a pipeline, which executes each
command in a subshell. If the while-loop is executed in the subshell
context, variable changes within are lost after the subshell terminates.
Fortunately, Bash 4.2, released in 2011, supports the 'lastpipe' option,
which makes the last element of a pipeline run in the current shell process.
Switch to the pipeline with 'lastpipe' solution, and also set 'pipefail'
to catch errors from ${NM}.
Add the bash requirement to Documentation/process/changes.rst.
Fixes: 31cb50b5590f ("kbuild: check static EXPORT_SYMBOL* by script instead of modpost")
Reported-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Reported-by: Michael Ellerman <mpe@ellerman.id.au>
Reported-by: Wang Yugui <wangyugui@e16-tech.com>
Tested-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Acked-by: Nick Desaulniers <ndesaulniers@google.com>
Tested-by: Sedat Dilek <sedat.dilek@gmail.com> # LLVM-14 (x86-64)
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2022-06-08 10:11:00 +09:00
Bash
----
- <ftp://ftp.gnu.org/gnu/bash/>
2005-04-16 15:20:36 -07:00
Binutils
--------
2016-09-19 08:07:42 -03:00
2017-03-27 22:05:34 +09:00
- <https://www.kernel.org/pub/linux/devel/binutils/>
2005-04-16 15:20:36 -07:00
kbuild: prepare to remove C files pre-generated by flex and bison
In Linux build system convention, pre-generated files are version-
controlled with a "_shipped" suffix. During the kernel building,
they are simply shipped (copied) removing the suffix.
This approach can reduce external tool dependency for the kernel build,
but it is tedious to manually regenerate such artifacts from developers'
point of view. (We need to do "make REGENERATE_PARSERS=1" every time
we touch real source files such as *.l, *.y)
Some months ago, I sent out RFC patches to run flex, bison, and gperf
during the build.
In the review and test, Linus noticed gperf-3.1 had changed the lookup
function prototype. Then, the use of gperf in kernel was entirely
removed by commit bb3290d91695 ("Remove gperf usage from toolchain").
This time, I tested several versions of flex and bison, and I was not
hit by any compatibility issue except a flaw in flex-2.6.3; if you
generate lexer for dtc and genksyms with flex-2.6.3, you will see
"yywrap redefined" warning. This was not intentional, but a bug,
fixed by flex-2.6.4. Otherwise, both flex and bison look fairly
stable for a long time.
This commit prepares some build rules to remove the _shipped files.
Also, document minimal requirement for flex and bison.
Rationale for the minimal version:
The -Wmissing-prototypes option of GCC warns "no previous prototype"
for lexers generated by flex-2.5.34 or older, so I chose 2.5.35 as the
required version for flex. Flex-2.5.35 was released in 2008. Bison
looks more stable. I did not see any problem with bison-2.0, released
in 2004. I did not test bison-1.x, but bison-2.0 should be old enough.
Tested flex versions:
2.5.35
2.5.36
2.5.37
2.5.39
2.6.0
2.6.1
2.6.2
2.6.3 (*)
2.6.4
(*) flex-2.6.3 causes "yywrap redefined" warning
Tested bison versions:
2.0
2.1
2.2
2.3
2.4
2.4.1
2.5.1
2.6
2.6.1
2.6.2
2.6.3
2.6.4
2.6.5
2.7
2.7.1
3.0
3.0.1
3.0.2
3.0.3
3.0.4
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2017-12-10 01:02:29 +09:00
Flex
----
- <https://github.com/westes/flex/releases>
Bison
-----
- <ftp://ftp.gnu.org/gnu/bison/>
2015-08-27 11:13:36 +01:00
OpenSSL
-------
2016-09-19 08:07:42 -03:00
- <https://www.openssl.org/>
2015-08-27 11:13:36 +01:00
2005-04-16 15:20:36 -07:00
System utilities
***** ***** ***** *
Util-linux
----------
2016-09-19 08:07:42 -03:00
2017-03-27 22:05:34 +09:00
- <https://www.kernel.org/pub/linux/utils/util-linux/>
2005-04-16 15:20:36 -07:00
2018-07-01 19:46:06 -07:00
Kmod
----
- <https://www.kernel.org/pub/linux/utils/kernel/kmod/>
- <https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git>
2005-04-16 15:20:36 -07:00
Ksymoops
--------
2016-09-19 08:07:42 -03:00
2017-03-27 22:05:34 +09:00
- <https://www.kernel.org/pub/linux/utils/kernel/ksymoops/v2.4/>
2005-04-16 15:20:36 -07:00
Mkinitrd
--------
2016-09-19 08:07:42 -03:00
- <https://code.launchpad.net/initrd-tools/main>
2005-04-16 15:20:36 -07:00
E2fsprogs
---------
2016-09-19 08:07:42 -03:00
2020-01-29 15:15:15 -08:00
- <https://www.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/>
- <https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/>
2005-04-16 15:20:36 -07:00
JFSutils
--------
2016-09-19 08:07:42 -03:00
2023-07-28 21:16:16 +00:00
- <https://jfs.sourceforge.net/>
2005-04-16 15:20:36 -07:00
Reiserfsprogs
-------------
2016-09-19 08:07:42 -03:00
2020-01-29 15:15:15 -08:00
- <https://git.kernel.org/pub/scm/linux/kernel/git/jeffm/reiserfsprogs.git/>
2005-04-16 15:20:36 -07:00
Xfsprogs
--------
2016-09-19 08:07:42 -03:00
2020-01-29 15:15:15 -08:00
- <https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git>
- <https://www.kernel.org/pub/linux/utils/fs/xfs/xfsprogs/>
2005-04-16 15:20:36 -07:00
2005-06-27 16:28:45 -07:00
Pcmciautils
-----------
2016-09-19 08:07:42 -03:00
2017-03-27 22:05:34 +09:00
- <https://www.kernel.org/pub/linux/utils/kernel/pcmcia/>
2005-06-27 16:28:45 -07:00
2005-04-16 15:20:36 -07:00
Quota-tools
2016-09-19 08:07:42 -03:00
-----------
2023-07-28 21:16:16 +00:00
- <https://sourceforge.net/projects/linuxquota/>
2005-04-16 15:20:36 -07:00
2005-05-01 08:59:27 -07:00
2005-04-16 15:20:36 -07:00
Intel P6 microcode
------------------
2016-09-19 08:07:42 -03:00
- <https://downloadcenter.intel.com/>
2005-04-16 15:20:36 -07:00
udev
----
2016-09-19 08:07:42 -03:00
2020-06-21 15:36:30 +02:00
- <https://www.freedesktop.org/software/systemd/man/udev.html>
2005-04-16 15:20:36 -07:00
2005-09-27 21:45:20 -07:00
FUSE
----
2016-09-19 08:07:42 -03:00
2018-03-27 14:59:50 +02:00
- <https://github.com/libfuse/libfuse/releases>
2005-09-27 21:45:20 -07:00
2009-04-28 23:37:02 +02:00
mcelog
------
2016-09-19 08:07:42 -03:00
2023-07-28 21:16:16 +00:00
- <https://www.mcelog.org/>
2009-04-28 23:37:02 +02:00
2022-04-19 11:48:15 -03:00
cpio
----
- <https://www.gnu.org/software/cpio/>
2005-04-16 15:20:36 -07:00
Networking
***** *****
PPP
---
2016-09-19 08:07:42 -03:00
2020-01-29 15:15:15 -08:00
- <https://download.samba.org/pub/ppp/>
- <https://git.ozlabs.org/?p=ppp.git>
- <https://github.com/paulusmack/ppp/>
2005-04-16 15:20:36 -07:00
NFS-utils
---------
2016-09-19 08:07:42 -03:00
2023-07-28 21:16:16 +00:00
- <https://sourceforge.net/project/showfiles.php?group_id=14>
- <https://nfs.sourceforge.net/>
2005-04-16 15:20:36 -07:00
Iptables
--------
2016-09-19 08:07:42 -03:00
2020-01-29 15:15:15 -08:00
- <https://netfilter.org/projects/iptables/index.html>
2005-04-16 15:20:36 -07:00
Ip-route2
---------
2016-09-19 08:07:42 -03:00
- <https://www.kernel.org/pub/linux/utils/net/iproute2/>
2005-04-16 15:20:36 -07:00
OProfile
--------
2016-09-19 08:07:42 -03:00
2023-07-28 21:16:16 +00:00
- <https://oprofile.sf.net/download/>
2016-09-19 08:07:43 -03:00
Kernel documentation
***** ***** ***** *****
Sphinx
------
2020-06-21 15:36:30 +02:00
- <https://www.sphinx-doc.org/>
