Handbook:Main Page/ko

도입부
젠투 핸드북은 문서를 일관성 있는 핸드북으로 한대 모은 노력의 산물입니다. 이 핸드북에는 인터넷 기반 설치 방법을 통한 설치 절차와 젠투 및 포티지를 다루는 방법이 들어있습니다.

아키텍처
다양한 아키텍처용 젠투 리눅스가 있습니다. 그런데 아키텍처의 정확한 의미는 뭘까요?

아키텍처란 동일한 기계어 명령을 지원하는 CPU(프로세서)의 계열 모음입니다. 데스크탑 계열에서 유명한 두가지 주요 아키텍처는 아키텍처와 x86_64 아키텍처(젠투에서는 로 칭함)가 있습니다. 그러나, (PowerPC 계열), ,  등의 다른 아키텍처도 있습니다.

젠투와 같은 다용도 배포판은 수많은 아키텍처를 지원합니다. 이 때문에, 지원 아키텍처 만큼 젠투 핸드북을 찾아볼 수 있습니다. 그러나 모든 사용자가 차이점을 인지하지 않기 때문에 혼동을 줄 수 있습니다. 몇가지 아키텍처는 (i686 또는 인텔 Core i7 같은) 시스템의 CPU 형식이나 이름의 일부로 인식되고 있습니다. 지원 아키텍처에 대한 간단한 정리와 젠투에서 사용하는 약어를 아래에서 찾아볼 수 있습니다. 그러나 대부분 사람은 이나 와 같이 상당수가 관심있어하는 시스템의 아키텍처를 모릅니다.

Viewing the Handbook
The list below gives a high-level overview 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 note for new users: if the CPU is less than five years old and the manufacturer is Intel or AMD, choosing the AMD64 Handbook is probably the correct route.


 * Alpha Handbook
 * 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: Installation – Working – Portage – Networking


 * AMD64 Handbook
 * 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, AMD Opteron, AMD Sempron processors, AMD Phenom, Intel Pentium 4, Intel Core2, Intel Core i3, i5, i7, and some Intel Atoms.
 * Full sections: Installation – Working – Portage – Networking


 * ARM Handbook
 * ARM is a 32-bit architecture that is a very popular in embedded and small systems. Sub-architectures range from ARMv1 to ARMv7 (Cortex) 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. Please see ARM project and.


 * ARM64 Handbook
 * ARM64 is a new 64-bit variant of ARM for embedded and server systems. The only sub-architecture is ARMv8 and includes the Cortex-A53, and Cortex-A57 processors which are starting to appear in a variety of SoCs in developer boards, smart phones, tablets etc. Variants include: Cortex-A53 and Cortex-A57.
 * There is no ARM64 Handbook. Please see ARM project and.


 * HPPA Handbook
 * 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: Installation – Working – Portage – Networking


 * IA64 Handbook
 * 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: Installation – Working – Portage – Networking


 * MIPS Handbook
 * 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: Installation – Working – Portage – Networking


 * PPC Handbook
 * 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.
 * Full sections: Installation – Working – Portage – Networking


 * PPC64 Handbook
 * 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.
 * Full sections: Installation – Working – Portage – Networking


 * SPARC Handbook
 * The SPARC architecture is best known by its most common producers, Sun (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: Installation – Working – Portage – Networking


 * X86 Handbook
 * 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: Installation – Working – Portage – Networking

Can't the Handbook be dynamically generated for each installation choice?
Everything is possible, but we have opted to only do this on a per-architecture level. Other choices, like partitioning, kernel selection, and package installation are easy enough to explain in a single document.

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 Gentoo FAQ. A stage3 installation is the only supported method of installation.

How to I improve the Handbook?
Suggestions, comments, or ideas on how to make the Handbook better can be reported to the Handbook project 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, as seen in the following example:

Please also remember to sign your discussion using the Signature and timestamp button in the text formatting toolbox.