Handbook:Main Page

The Gentoo Handbook is Article description::an effort to centralize documentation into a coherent handbook. This handbook contains the installation instructions for an Internet-based installation and additional sections for working with Gentoo's native software tools such as the OpenRC init system and the Portage package manager.

Architectures
Gentoo Linux is available for many computer architectures.

An instruction set architecture (ISA) (Wikipedia) or architecture for short is a family of CPUs (processors) who support the same instructions. The two most prominent architectures in the desktop world are the architecture and the x86_64 architecture (for which Gentoo uses the  notation). But many other architectures exist, such as, (the PowerPC family), , , etc...

A distribution as versatile as Gentoo supports many architectures. Below you will find a quick summary of the supported architectures and the abbreviation used in Gentoo. Most people that do not know the architecture of their PC system are likely interested in.

Viewing the Handbook
The list below gives a high-level overview of the architectures supported by various Gentoo Linux projects. It is important to choose the correct architecture before proceeding with the associated Installation section of a Handbook. Be sure to verify the CPU's architecture before moving onward.

A rule of thumb for new Gentoo users: If the CPU was manufactured after 2015 and the manufacturer is either Intel or AMD, choosing the is probably the correct route.


 * 
 * The Alpha architecture is a 64-bit architecture developed by Digital Equipment Corporation (DEC). It is still in use by some mid-range and high-end servers, but the architecture is slowly being faded out. Variants include: ES40, AlphaPC, UP1000, and Noname.
 * Full sections: –  –  –


 * 
 * AMD64 is a 64-bit architecture that is compatible with the architecture (and thus also known as ). It was first used by AMD (under the AMD64 name) and Intel (under the EM64T name) and is now the most prominent architecture for medium and high-end desktop PCs. It is also commonly found in the server segment. Variants include: AMD Athlon 64, Opteron, Sempron, Phenom, FX, Ryzen, Threadripper, and Epyc along with Intel Pentium 4, Core2, Core i3, i5, i7, i9, Xeon, and some Atoms.
 * Full sections: –  –  –


 * ARM Handbook
 * ARM is a 32-bit architecture that is a very popular in embedded and small systems. Sub-architectures range from ARMv2 to ARMv6 (legacy), to ARMv6-M (Cortex), as well as ARMv8-R and ARMv8-M and are often found in smart phones, tablets, hand-held consoles, end-user GPS navigation systems, etc. Variants include: StrongARM and Cortex-M.
 * There is no ARM Handbook available at this time. Please see the and  for more information about Gentoo's support for ARM.


 * ARM64 Handbook
 * ARM64 is a 64-bit variant of ARM for embedded and server systems. The primary sub-architecture referred to as AArch64 (also known as ARMv8-A) is produced by a few manufacturers. AArch64 chips are seen in a variety of SoCs including developer boards, smart phones, tablets, smart TVs, etc. Variants include: ARM Holdings' Cortex-A53, A57, A72, A73, and Qualcomm's Kryo and Falkor.
 * There is no ARM64 Handbook available at this time. Please see the and  for more information about Gentoo's support for ARM64.


 * 
 * Referred to as HPPA, the PA-RISC architecture is an instruction set developed by Hewlett-Packard and was used in their mid- and high-end server series until about 2008 (after which HP started using Intel Itanium). Variants include: HP 9000 and PA-8600.
 * Full sections: –  –  –


 * 
 * IA64 is a 64-bit architecture designed by Intel and used in their Intel Itanium processor series. This architecture is not compatible with or  (a.k.a. ) and is mostly found in medium and high-end server series. Variants include: Intel Itanium.
 * Full sections: –  –  –


 * 
 * Developed by MIPS Technologies, the MIPS architecture comprises multiple subfamilies (called revisions) such as MIPS I, MIPS III, MIPS32, MIPS64 and more. MIPS is most common in embedded systems. Variants include: MIPS32 1074K and R16000.
 * Full sections: –  –  –


 * 
 * PPC is a 32-bit architecture used by many Apple, IBM, and Motorola processors. They are most commonly found in embedded systems. Variants include: Apple OldWorld, Apple NewWorld, generi Pegasos, Efika, older IBM iSeries and pSeries. Readers of this handbook may which to take a look at the page before getting started.
 * Full sections: –  –  –


 * 
 * PPC64 is the 64-bit variant of the PPC architecture, popular in both embedded as well as high-end performance servers. Variants include: IBM RS/6000s, IBM pSeries, and IBM iSeries. Readers of this handbook may which to take a look at the page before getting started.
 * Full sections: –  –  –


 * RISC-V Handbook
 * RISC-V is an upcoming 32-bit, 64-bit, and 128-bit architecture with an open instruction set. Currently, the 64-bit RISC-V variant is supported by Gentoo.
 * There is no RISC-V Handbook available at this time. See the for more information about Gentoo's support for RISC-V.


 * 
 * The SPARC architecture is best known by its most common producers, Sun Microsystems (now Oracle) and Fujitsu. It is used in server systems although a few workstations exist as well. In Gentoo, only SPARC64-compatible CPUs are supported. Variants include: E3000, Blade 1000, and Ultra 2.
 * Full sections: –  –  –


 * 
 * X86 is a 32-bit architecture used by CPUs that are often said to be "Intel compatible". It was until recently the most popular architecture for desktop PCs. Gentoo offers builds for i486 (supports all families) and i686 (supports Pentium and higher or compatible). Variants include: i486, i686, AMD Athlon, Intel Core, and some Intel Atoms.
 * Full sections: –  –  –

Can't the Handbook be dynamically generated for each installation choice?
The handbook maintainers have opted to write on a per-architecture level using Gentoo's default init system and basic partitioning schemes. The point of the Handbook is to get a bare-bones Gentoo system up and running, not to cover all possible installation paths (irregular partitioning, init systems, kernel configuration, system management utilities, etc.).

Concepts such as advanced partitioning, non-generic kernel configuration, and alternate init systems are explained other areas around the wiki in publicly modifiable namespace (hint: anyone with wiki account can edit them!).

We ask our readers to search wiki and discover what is already available before requesting a new section or addition to be added to the Handbook. If you believe a new generic section is necessary to add to the Handbook, then propose a request by {{{{Link|Handbook:Main_Page|section=#How do I improve the Handbook?|following the instructions below}}.

I cannot find stage1 information in the Handbook. Where do I look?
Instructions on using a stage1 or stage2 tarball are now available in the. A stage3 installation is the only supported method of installation.

How do I improve the Handbook?
Suggestions, comments, or ideas on how to make the Handbook better can be reported to the via the Discussion page of the respective article. Documentation is made for the community, so community feedback is well appreciated.

Be aware that most decisions made while developing documentation are based on a consensus-model. It is impossible to write or structure documentation in such a way that renders every reader happy.

Those who open discussions with the goal of improving the Handbook must be able to accept a "No" as an answer. Typically "No" is used when we believe the current implementation is beneficial for the majority of readers.

In order to properly track open issues we ask you to add the Talk template to each discussion you open. Something similar to what is seen in the following example will suffice:

The  code at the end of the example inserts a dated signature when the page is saved or previewed. This code can either be typed in manually or generated by using the Signature and timestamp button in the edit toolbar. Wiki editors will refer to this as 'signing a discussion.' Please remember to sign each comment made on discussion pages.