This is Gentoo's testing wiki. It is a non-operational environment and its textual content is outdated.

Please visit our production wiki at https://wiki.gentoo.org

Handbook:Alpha/Installation/Media/tr

From Gentoo Wiki (test)
Jump to:navigation Jump to:search
This page is a translated version of the page Handbook:Alpha/Installation/Media and the translation is 50% complete.
Other languages:
Alpha Handbook
Installation
About the installation
Choosing the media
Configuring the network
Preparing the disks
Installing stage3
Installing base system
Configuring the kernel
Configuring the system
Installing tools
Configuring the bootloader
Finalizing
Working with Gentoo
Portage introduction
USE flags
Portage features
Initscript system
Environment variables
Working with Portage
Files and directories
Variables
Mixing software branches
Additional tools
Custom package repository
Advanced features
Network configuration
Getting started
Advanced configuration
Modular networking
Wireless
Adding functionality
Dynamic management


Donanım gereksinimleri

Before we start, we first list what hardware requirements are needed to successfully install Gentoo on a alpha box.


Minimal CD LiveDVD
CPU Any Alpha CPU N/A
Memory 64 MB N/A
Disk space 1.5 GB (excluding swap space) N/A
Swap space At least 256 MB N/A


Gentoo Linux installation media

Minimal kurulum CD'si

Note
As of August 23, 2018 the official Minimal CDs are capable of booting in UEFI mode. Previous versions boot in BIOS (MBR) mode only. Readers looking to make their system UEFI bootable must download the latest ISO.

The Gentoo minimal installation CD is a bootable image which contains a self-sustained Gentoo environment. It allows the user to boot Linux from the CD or other installation media. During the boot process the hardware is detected and the appropriate drivers are loaded. The image is maintained by Gentoo developers and allows anyone to install Gentoo if an active Internet connection is available.

The Minimal Installation CD is called install-alpha-minimal-<release>.iso.

Ara sıra çıkan Gentoo LiveDVD

Bazı dönemlerde, Gentoo onuncu yıl projesi tarafından hazırlanan özel DVD'ler yayınlanır. Aşağıdaki detaylar minimal CD'yi hedef almaktadır, bu sebeple bazı farklar bulunabilir. Ancak LiveDVD (veya bilgisayarınızı başlatabileceğiniz herhangi bir canlı Linux ortamı) üzerinde sudo su - veya sudo -i komutu ile root terminaline geçiş yapılabilir.

Peki bu stage'ler nedir?

A stage3 tarball is an archive containing a minimal Gentoo environment, suitable to continue the Gentoo installation using the instructions in this manual. Previously, the Gentoo Handbook described the installation using one of three stage tarballs. While Gentoo still offers stage1 and stage2 tarballs, the official installation method uses the stage3 tarball. If you are interested in performing a Gentoo installation using a stage1 or stage2 tarball, please read the Gentoo FAQ on How do I install Gentoo using a stage1 or stage2 tarball?

Stage3 tarballs can be downloaded from releases/alpha/autobuilds/ on any of the official Gentoo mirrors. Stage files update frequently and are not included on the installation images.

Downloading

Obtain the media

The default installation media that Gentoo Linux uses are the minimal installation CDs, which host a bootable, very small Gentoo Linux environment. This environment contains all the right tools to install Gentoo. The CD images themselves can be downloaded from the downloads page (recommended) or by manually browsing to the ISO location on one of the many available mirrors.

Bu yansılarda, minimal kurulum CD'leri şu şekilde bulunabilir:

  1. Go to the releases/ directory.
  2. Select the directory for the relevant target architecture (such as alpha/).
  3. Select the autobuilds/ directory.
  4. For amd64 and x86 architectures select either the current-install-amd64-minimal/ or current-install-x86-minimal/ directory (respectively). For all other architectures navigate to the current-iso/ directory.
Not
arm, mips ve s390 gibi bazı mimarilerde minimal kurulum CD'si bulunmamakta. Henüz Gentoo Sürüm Geliştirme Projesi bu mimariler için .iso oluşturmayı desteklemiyor.

Inside this location, the installation media file is the file with the .iso suffix. For instance, take a look at the following listing:

CODE Example list of downloadable files at releases/alpha/autobuilds/current-iso/
[DIR] hardened/                                          05-Dec-2014 01:42    -   
[   ] install-alpha-minimal-20141204.iso                 04-Dec-2014 21:04  208M  
[   ] install-alpha-minimal-20141204.iso.CONTENTS        04-Dec-2014 21:04  3.0K  
[   ] install-alpha-minimal-20141204.iso.DIGESTS         04-Dec-2014 21:04  740   
[TXT] install-alpha-minimal-20141204.iso.DIGESTS.asc     05-Dec-2014 01:42  1.6K  
[   ] stage3-alpha-20141204.tar.bz2                      04-Dec-2014 21:04  198M  
[   ] stage3-alpha-20141204.tar.bz2.CONTENTS             04-Dec-2014 21:04  4.6M  
[   ] stage3-alpha-20141204.tar.bz2.DIGESTS              04-Dec-2014 21:04  720   
[TXT] stage3-alpha-20141204.tar.bz2.DIGESTS.asc          05-Dec-2014 01:42  1.5K

In the above example, the install-alpha-minimal-20141204.iso file is the minimal installation CD itself. But as can be seen, other related files exist as well:

  • A .CONTENTS file which is a text file listing all files available on the installation media. This file can be useful to verify if particular firmware or drivers are available on the installation media before downloading it.
  • A .DIGESTS file which contains the hash of the ISO file itself, in various hashing formats/algorithms. This file can be used to verify if the downloaded ISO file is corrupt or not.
  • A .DIGESTS.asc file which not only contains the hash of the ISO file (like the .DIGESTS file), but also a cryptographic signature of that file. This can be used to both verify if the downloaded ISO file is corrupt or not, as well as verify that the download is indeed provided by the Gentoo Release Engineering team and has not been tampered with.

Şimdilik diğer dosyaları es geçelim (onlara ilerleyen adımlarda döneceğiz). .iso dosyasını ve ISO'nun kontrolünü de istiyorsanız .DIGESTS.asc dosyasını da indirin. Bu dosya .CONTENTS dosyasını da içerdiği ve .DIGESTS dosyasının imzalanmış sürümü olduğu için, tek başına yeterli olacaktır.

İndirilen dosyaların bütünlük kontrolü

Note
Bu adım seçime bağlıdır ve Gentoo Linux kurulumu için bir zorunluluk değildir. Ancak kurulumun sağlıklı tamamlanması ve doğru kaynaktan geldiğine emin olunması için tavsiye edilmektedir.

.DIGESTS ve .DIGESTS.asc dosyaları doğru araçlar ile kullanılırsa bütünlük kontrolü yapmak için yeterlidir. Kontrol genelde iki adımda yapılır:

  1. Öncelikle kriptografik imza kullanılarak dosyanın Gentoo geliştirici ekibinden geldiğine emin olunur.
  2. Eğer kriptografik imza doğruysa, parmak izi (checksum) kullanılarak dosyanın sağlam indirildiği doğrulanır.

Microsoft Windows üzerinde doğrulama

Var olan bir Microsoft Windows üzerinde checksum ve kriptografik imzaları kullanabilecek doğru araçları bulmanız pek olası değildir.

Öncelikle kriptografik imza doğrulaması için GPG4Win türünde bir araç kullanılabilir. Kurulduktan sonra Gentoo geliştirici ekibinin imzası içe aktarılmalıdır. Anahtarlar ilgili sayfada bulunabilir.İçe aktarmanın ardından .DIGESTS.asc dosyasının imzası doğrulanabilir.

Important
Bu işlem .DIGESTS dosyasını değil, .DIGESTS.asc dosyasını doğrulayabilir. Bu da aynı zamanda .DIGESTS.asc dosyasının da checksum ile kontrol edilmesi gerektiği anlamına gelir.

Checksum (parmak izi) de Hashcalc uygulaması kullanılarak doğrulanabilir. Çoğunlukla bu tür araçlar hesapladıkları checksum'u iletip, kullanıcının .DIGESTS.asc dosyasındaki değerle karşılaştırmasını ister.

Linux üzerinde doğrulama

Bir Linux sistem üzerinde kriptografik imzayı onaylamak için gerekli dosyalar için app-crypt/gnupg yazılımı gerekmektedir. Bu pakette bulunan araçlar ile aşağıdaki komutları kullanarak .DIGESTS.asc dosyasının doğrulamasını yapabilirsiniz.

Öncelikle, imzalar sayfasından doğru imzaları indirin:

user $gpg --keyserver hkp://keys.gnupg.net --recv-keys 0xBB572E0E2D182910
gpg: requesting key 0xBB572E0E2D182910 from hkp server pool.sks-keyservers.net
gpg: key 0xBB572E0E2D182910: "Gentoo Linux Release Engineering (Automated Weekly Release Key) <releng@gentoo.org>" 1 new signature
gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model
gpg: depth: 0  valid:   3  signed:  20  trust: 0-, 0q, 0n, 0m, 0f, 3u
gpg: depth: 1  valid:  20  signed:  12  trust: 9-, 0q, 0n, 9m, 2f, 0u
gpg: next trustdb check due at 2018-09-15
gpg: Total number processed: 1
gpg:         new signatures: 1

Ardından .DIGESTS.asc dosyasının kriptografik imzasını doğrulayın:

user $gpg --verify install-alpha-minimal-20141204.iso.DIGESTS.asc
gpg: Signature made Fri 05 Dec 2014 02:42:44 AM CET
gpg:                using RSA key 0xBB572E0E2D182910
gpg: Good signature from "Gentoo Linux Release Engineering (Automated Weekly Release Key) <releng@gentoo.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 13EB BDBE DE7A 1277 5DFD  B1BA BB57 2E0E 2D18 2910

Her şeyin düzgün olduğundan emin olmak için, Gentoo imza sayfasındaki parmak izini (fingerprint) deoğrulayın.

Kriptografik imzayı onayladıktan sonra, ISO dosyasının bozulmadan indiğini de kontrol edin. Bunun için içerisinde birçok algoritma ile üretilmiş hash'ler bulunan .DIGESTS.asc dosyasını kullanabilirsiniz. Örneğin SHA512 kontrolü yapmak için:

user $grep -A 1 -i sha512 install-alpha-minimal-20141204.iso.DIGESTS.asc
# SHA512 HASH
364d32c4f8420605f8a9fa3a0fc55864d5b0d1af11aa62b7a4d4699a427e5144b2d918225dfb7c5dec8d3f0fe2cddb7cc306da6f0cef4f01abec33eec74f3024  install-alpha-minimal-20141204.iso
--
# SHA512 HASH
0719a8954dc7432750de2e3076c8b843a2c79f5e60defe43fcca8c32ab26681dfb9898b102e211174a895ff4c8c41ddd9e9a00ad6434d36c68d74bd02f19b57f  install-alpha-minimal-20141204.iso.CONTENTS

In the above output, two SHA512 checksums are shown - one for the install-alpha-minimal-20141204.iso file and one for its accompanying .CONTENTS file. Only the first checksum is of interest, as it needs to be compared with the calculated SHA512 checksum which can be generated as follows:

user $sha512sum install-alpha-minimal-20141204.iso
364d32c4f8420605f8a9fa3a0fc55864d5b0d1af11aa62b7a4d4699a427e5144b2d918225dfb7c5dec8d3f0fe2cddb7cc306da6f0cef4f01abec33eec74f3024  install-alpha-minimal-20141204.iso

Birbiriyle eşleştiğine göre, kurulum ortamımız zarar görmemiş diyebilir ve kuruluma devam edebiliriz.

Burning a disk

Tabi ki sadece ISO dosyası ile kurulum yapamayız. Öncelikle ISO dosyamızın içeriğini bir CD'ye yazmamız gerekmekte. Bu işlemi nasıl yapabileceğinizi hızlıca anlatalım. Detaylı açıklamalar için iso dosyası nasıl yazdırılır belgemize bakabilirsiniz.

Microsoft Windows Kullanarak

Microsoft Windows altında ISO'ları CD'ye yazmak için kullanılabilecek birkaç araç bulunmakta (güncel sürümlerinde ISO dosyasına sağ tıklayarak CD'ye yazdırma seçeneğini de bulabilirsiniz).

  • EasyCD Creator kullanıyorsanız, Dosya menüsünden, CD imajından CD oluştur seçeneğini kullanın. Ardından Dosya türü bölümünde ISO imaj dosyasını seçin. ISO dosyasını seçip Aç'a tıklayın. Başlat'a tıkladığınızda ISO yazdırma işlemi başlayacaktır.
  • Nero Burning ROM kullanıyorsanız, açılan sihirbaz penceresini kapatıp Dosya menüsünden İmaj yazdır seçeneğini kullanın.

Linux Kullanarak

Linux'da ISO yazdırma işlemi, app-cdr/cdrtools paketindeki cdrecord komutu ile yapılabilir.

Örneğin ISO dosyasını /dev/sr0 aygıtındaki CD'ye yazıdrmak için (bu isim sistemdeki ilk CD aygıtını işaret eder, gerek görürseniz değiştirin):

user $cdrecord dev=/dev/sr0 install-alpha-minimal-20141204.iso

Users that prefer a graphical user interface can use K3B, part of the kde-apps/k3b package. In K3B, go to Tools and use Burn CD Image. Then follow the instructions provided by K3B.

Booting

Booting the installation CD

When an Alpha system is powered on, the first thing that gets started is the firmware. It is loosely synonymous with the BIOS software on PC systems. There are two types of firmware on Alpha systems: SRM (Systems Reference Manual) and ARC (Advanced Risc Console).

SRM is based on the Alpha Console Subsystem specification, which provides an operating environment for OpenVMS, Tru64 UNIX, and Linux operating systems. ARC is based on the Advanced RISC Computing (ARC) specification, which provides an operating environment for Windows NT. A detailed guide on using SRM can be found at the Alpha Linux website.

If the Alpha system supports both SRM and ARCs (ARC, AlphaBIOS, ARCSBIOS) then follow these instructions for switching to SRM. If the system already uses SRM, then everything is ready. If the system can only use ARCs (Ruffian, nautilus, xl, etc.) then choose MILO later on when the instructions talk about bootloaders.

Now to boot an Alpha Installation CD, put the CD-ROM in the tray and reboot the system. SRM can be used to boot the Installation CD. If that isn't possible, MILO needs to be used.

To boot a CD-ROM using SRM, first list the available hardware drives:

>>>show device
dkb0.0.1.4.0        DKB0       TOSHIBA CDROM

Next boot the CD by providing the right CD-ROM drive device. For instance, with dkb0:

>>>boot dkb0 -flags 0

With -flags 2 the serial port /dev/ttyS0 will be used as the default console.

To boot a CD-ROM using MILO, use a command like the following after substituting sdb with the right CD-ROM drive device:

MILO>boot sdb:/boot/gentoo initrd=/boot/gentoo.igz root=/dev/ram0 init=/linuxrc looptype=squashfs loop=/image.squashfs cdroot

To use the serial port /dev/ttyS0 as the default console, add console=ttyS0 to the command line.

After booting, a root ("#") prompt will be shown on the current console. Users can switch to other consoles by pressing Alt + F2, Alt + F3 and Alt + F4. Get back to the first one by pressing Alt + F1.


Extra hardware configuration

When the Installation medium boots, it tries to detect all the hardware devices and loads the appropriate kernel modules to support the hardware. In the vast majority of cases, it does a very good job. However, in some cases it may not auto-load the kernel modules needed by the system. If the PCI auto-detection missed some of the system's hardware, the appropriate kernel modules have to be loaded manually.

In the next example the 8139too module (which supports certain kinds of network interfaces) is loaded:

root #modprobe 8139too

Optional: User accounts

If other people need access to the installation environment, or there is need to run commands as a non-root user on the installation medium (such as to chat using irssi without root privileges for security reasons), then an additional user account needs to be created and the root password set to a strong password.

To change the root password, use the passwd utility:

root #passwd
New password: (Enter the new password)
Re-enter password: (Re-enter the password)

To create a user account, first enter their credentials, followed by the account's password. The useradd and passwd commands are used for these tasks.

In the next example, a user called john is created:

root #useradd -m -G users john
root #passwd john
New password: (Enter john's password)
Re-enter password: (Re-enter john's password)

To switch from the (current) root user to the newly created user account, use the su command:

root #su - john

Optional: Viewing documentation while installing

TTYs

To view the Gentoo handbook during the installation, first create a user account as described above. Then press Alt+F2 to go to a new terminal.

During the installation, the links command can be used to browse the Gentoo handbook - of course only from the moment that the Internet connection is working.

user $links https://wiki.gentoo.org/wiki/Handbook:Alpha

To go back to the original terminal, press Alt+F1.

GNU Screen

The GNU Screen utility is installed by default on official Gentoo installation media. It may be more efficient for the seasoned Linux enthusiast to use screen to view installation instructions via split panes rather than the multiple TTY method mentioned above.

Seçime bağlı: SSH servisinin başlatılması

To allow other users to access the system during the installation (perhaps to support during an installation, or even do it remotely), a user account needs to be created (as was documented earlier on) and the SSH daemon needs to be started.

To fire up the SSH daemon on an OpenRC init, execute the following command:

root #rc-service sshd start
Note
If users log on to the system, they will see a message that the host key for this system needs to be confirmed (through what is called a fingerprint). This behavior is typical and can be expected for initial connections to an SSH server. However, later when the system is set up and someone logs on to the newly created system, the SSH client will warn that the host key has been changed. This is because the user now logs on to - for SSH - a different server (namely the freshly installed Gentoo system rather than the live environment that the installation is currently using). Follow the instructions given on the screen then to replace the host key on the client system.

To be able to use sshd, the network needs to function properly. Continue with the chapter on Configuring the network.


← Kurulum hakkında Home Ağı yapılandırma →


Retrieved from "https://wikitest.gentoo.org/index.php?title=Handbook:Alpha/Installation/Media/tr&oldid=338932"