Choosing the right installation medium. Hardware requirements. Before we start, we first list what hardware requirements are needed to successfully install Gentoo on a amd. It allows the user to boot Linux from the CD. During the boot process the hardware is detected and the appropriate drivers are loaded. The CD is maintained by Gentoo developers and allows anyone to install Gentoo if an active Internet connection is available. The instructions further down this chapter target the Minimal Installation CD so might be a bit different. However, the Live. DVD (or any other bootable Linux environment) supports getting a root prompt by just invoking sudo su - or sudo - i in a terminal. Previously, the Gentoo Handbook described the installation using one of three stage tarballs.
While Gentoo still offers stage. If you are interested in performing a Gentoo installation using a stage. Gentoo FAQ on How do I install Gentoo using a stage. Stage files update frequently and are not included on the installation CDs. 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. Select the directory for the relevant target architecture (such as amd. Select the autobuilds/ directory. For amd. 64 and x. For all other architectures navigate to the current- iso/ directory. Note. Some target architectures such as arm, mips, and s. CDs. At this time the Gentoo Release Engineering project does not support building . Inside this location, the installation CD file is the file with the . For instance, take a look at the following listing. CODEExample list of downloadable files at releases/amd. 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 CD. This file can be useful to verify if particular firmware or drivers are available on the installation CD 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. Fedora Minimal InstallationDebian Minimal InstallationA . 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. Ignore the other files available at this location for now - those will come back when the installation has proceeded further. Download the . iso file and, if verification of the download is wanted, download the . DIGESTS. asc file for the . The . CONTENTS file does not need to be downloaded as the installation instructions will not refer to this file anymore, and the . DIGESTS file should contain the same information as the . DIGESTS. asc file, except that the latter also contains a signature on top of it. However, it is recommended as it ensures that the downloaded file is not corrupt and has indeed been provided by the Gentoo Infrastructure team. Through the . DIGESTS and . DIGESTS. asc files, the validity of the ISO file can be confirmed using the right set of tools. This verification is usually done in two steps. First, the cryptographic signature is validated to make sure that the installation file is provided by the Gentoo Release Engineering team If the cryptographic signature validates, then the checksum is verified to make sure that the downloaded file itself is not corrupted. Microsoft Windows based verification. On a Microsoft Windows system, chances are low that the right set of tools to verify checksums and cryptographic signatures are in place. After installation, the public keys of the Gentoo Release Engineering team need to be imported. Be capable of running in the Minimal Server Interface configuration to take advantage of the reduced resource. Windows Services for UNIX should be part of the Windows server core / minimal installation. Minimal Installation Requirements. In some cases, you may not want to leave GAUSS installed on your license server. Reprise requires that a few files remain on the license server in order to hand out licenses: aptech.set. The list of keys is available on the signatures page. Once imported, the user can then verify the signature of the . DIGESTS. asc file. That also implies that the checksum should be verified against the values in the . DIGESTS. asc file, which is why the instructions above only refer to downloading the . DIGESTS. asc file. The checksum itself can be verified using the Hashcalc application, although many others exist as well. Most of the time, these tools will show the user the calculated checksum, and the user is requested to verify this checksum with the value that is inside the . DIGESTS. asc file. With this package installed, the following commands can be used to verify the cryptographic signature of the . DIGESTS. asc file. The . DIGESTS. asc file contains multiple hashing algorithms, so one of the methods to validate the right one is to first look at the checksum registered in the . DIGESTS. asc file. For instance, to get the SHA5. A 1 - i sha. 51. 2 install- amd. DIGESTS. asc. 3. 64d. CONTENTS. In the above output, two SHA5. CONTENTS file. Only the first checksum is of interest, as it needs to be compared with the calculated SHA5. As both checksums match, the file is not corrupted and the installation can continue. The ISO file needs to be burned on a CD to boot from, and in such a way that its content is burned on the CD, not just the file itself. Below a few common methods are described - a more elaborate set of instructions can be found in Our FAQ on burning an ISO file. Then change the Files of type to ISO image file. Then locate the ISO file and click Open. After clicking on Start recording the ISO image will be burned correctly onto the CD- R. With Nero Burning ROM, cancel the wizard which automatically pops up and select Burn Image from the File menu. Select the image to burn and click Open. Now hit the Burn button and watch the brand new CD being burnt. Burning with Linux. On Linux, the ISO file can be burned on a CD using the cdrecord command, part of the app- cdr/cdrtools package. In K3. B, go to Tools and use Burn CD Image. Then follow the instructions provided by K3. B. Remove all external bootable media from the system (including any CD/DVD disks or USB drives), reboot the system, and enter the motherboard's firmware user interface. This is usually performed by pressing a keyboard key such as DEL, F1, F1. ESC during the Power- On Self- test (POST) process. The 'trigger' key varies depending on the system and motherboard. If it is not obvious use an internet search engine and do some research using the motherboard's model name as the search keyword. Results should be easy to determine. Once inside the motherboard's firmware menu, change the boot order so that the external bootable media (CD/DVD disks or USB drives) are tried before the internal disk devices. Without this change, the system will most likely reboot to the internal disk device, ignoring the external boot media. If not, then it might be necessary to create a bootable UEFI USB stick (or other medium) once before finalizing the Gentoo Linux installation. Now place the installation CD in the CD- ROM drive and reboot. A boot prompt should be shown. At this screen, Enter will begin the boot process with the default boot options. To boot the installation CD with custom boot options, specify a kernel followed by boot options and then hit Enter. If no choice is made within 1. CD will fall back to booting from disk. This allows installations to reboot and try out their installed environment without the need to remove the CD from the tray (something well appreciated for remote installations). On the installation CD, several kernels are provided. The default one is called gentoo. Other kernels are for specific hardware needs and the - nofb variants disable framebuffer support. This is only needed if the system requires ACPI to function properly. This is not required for Hyperthreading support. This is useful on some older systems and is also a requirement for using APM. This will disable any Hyperthreading support of your processor. The first option is the device, usually tty. S0 on x. 86, followed by any connection options, which are comma separated. The default options are 9. Options should be encapsulated in quotes. This also requires that acpi=off. This is only required when booting from PCMCIA/Cardbus devices. This is also a requirement for booting most USB devices, as they use the SCSI subsystem of the kernel. This option is only used on machines with an older BIOS. Replace sda with the device that requires this option. If the system is having trouble reading from the IDE CDROM, try this option. This also disables the default hdparm settings from being executed. It has been known to cause some problems on older hardware. This is useful for doing debugging of a failing CD or driver. This is useful on networks with only static addresses. This should only be necessary if your Firewire hardware is causing a problem with booting the CD. This is useful for doing debugging of a failing CD or driver. This is used if the system is having problems with the SATA subsystem. This is useful for debugging SMP- related issues with certain drivers and motherboards. This is useful for systems where sound support causes problems. This is useful for debugging USB issues. This might get messy, as it displays a lot of data to the screen. This option requires that there is at least twice as much available RAM as the size of the CD. Replace X with the module name. Multiple modules can be specified by a comma- separated list. Syntax matches that of doload. Replace X with the number of seconds to pause. As an example, we boot the gentoo kernel, with dopcmcia as a kernel parameter. Next the user will be greeted with a boot screen and progress bar. If the installation is done on a system with a non- US keyboard, make sure to immediately press Alt + F1 to switch to verbose mode and follow the prompt. If no selection is made in 1. US keyboard) will be accepted and the boot process will continue. Once the boot process completes, the user is automatically logged in to the .
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |