There are still merits to TFTP booting such as wide-range device support. Setting up a DHCP server on the same machine is possible - just make sure that the booted machines are connected to it. Or just tweak the configuration of an existing router. Create directories: The first thing to do is to create the directories where the diskless system will be stored. For the remainder of this howto, the client that is being worked on will be called 'eta'. For dhcpd, just run emerge dhcp or any other DHCP server of choice.
Original way was to copy the PXE image to the diskless client but the path does not seem to exit anymore. NFS is quite easy to configure. A next step is to reboot the server with a Gentoo installation CD although experienced administrators can continue without if they are sufficiently versed in Gentoo installations. This example uses a stage3 tarball.
Then follow the installation manual until kernel configuration. When doing the make menuconfig of the kernel configuration, don't forget to enable the following options with the others recommended into the install guide. Do not install another bootloader because there is already one - pxegrub. Simply finish the install and restart the server. For help with this consult the hardware manuals or manufacturers website. Then, a nice black and white GRUB bootmenu should be displayed from where users can select the kernel to boot and press the Enter Return key.
If everything is okay the kernel should boot, mount the root filesystem using NFS and provide a login prompt. In order to install Gentoo from an existing Linux distribution it needs to have the chroot command installed, and have a copy of the Gentoo installation or ISO that's desired to install. A network connection is highly recommended as otherwise the installation can only work with the files available in the installation media. The first example shows the output of mount on a system.
The second example uses df disk free to see how much space there is left and how it will be resized. Note that resizing the root partition is not mandatory! Anything else supported by the resizer can be resized, but let's talk about that later. In this case, it was decided to be resized as to leave MB of free space, therefore allocating 2 GB for Gentoo.
Not bad, it could have quite some stuff installed. However, 1 GB is deemed enough for most users. So now partition this thing! It is included on the Minimal installation CD. Look up on that page the type of file system to resize and see if parted can do it.
If not, some partitions might need to be destroyed to make space for Gentoo. Go ahead downloading the software and install it. It was very useful to me. Good luck i havent tried gentoo in ages it had an installer back then i believe this was hmm perhaps 7 years ago give or take now i miss it and its capabilities trying it again alongside my windows good luck CJ this guide makes it much easier in case a hiccup browser next to u for reference : if using live dvd tat is.
Wish me luck. Very complicated but much appreciated. I just followed the links in this tutorial, and will do so again for part 2, but I learned a little bit. Thanks for posting this. Have a question or suggestion? Please leave a comment to start the discussion. Please keep in mind that all comments are moderated and your email address will NOT be published.
Save my name, email, and website in this browser for the next time I comment. Notify me of followup comments via e-mail. You can also subscribe without commenting. This site uses Akismet to reduce spam. Learn how your comment data is processed. Gentoo Linux Installation Guide Because the final user can choose which components are to be installed, Gentoo Linux installation is a very difficult process for unexperienced users, but this tutorial uses for simplification a pre-build environment provided by a LiveDVD and a stage 3 tarball with minimal system software required to complete installation.
Boot Gentoo Live. If you liked this article, then do subscribe to email alerts for Linux tutorials. If you have any questions or doubts? The default values contained in the stage3 archive that is unpacked should be good enough. The following one is just an example:. Then continue with Installing the Gentoo base system. In order to download source code quickly it is recommended to select a fast mirror.
Portage will look in the make. It is possible to surf to the Gentoo mirror list and search for a mirror or mirrors that is close to the system's physical location as those are most frequently the fastest ones.
However, we provide a nice tool called mirrorselect which provides users with a nice interface to select the mirrors needed. Just navigate to the mirrors of choice and press Spacebar to select one or more mirrors. This file contains the sync information needed to update the package repository the collection of ebuilds and related files containing all the information Portage needs to download and install software packages.
Configuring the repository can be done in a few simple steps. First, if it does not exist, create the repos. Next, copy the Gentoo repository configuration file provided by Portage to the newly created repos. Take a peek with a text editor or by using the cat command. The inside of the file should be in. The default sync-uri variable value listed above will determine a mirror location based on a rotation.
This will aid in easing bandwidth stress on Gentoo's infrastructure and will provide a fail-safe in case a specific mirror is offline. It is recommended the default URI is retained unless a local, private Portage mirror will be used.
This needs to be done to ensure that networking still works even after entering the new environment. To copy this information, it is recommended to pass the --dereference option to the cp command.
Otherwise in the new environment the symbolic link would point to a non-existing file as the link's target is most likely not available inside the new environment.
In a few moments, the Linux root will be changed towards the new location. To make sure that the new environment works properly, certain filesystems need to be made available there as well. Now that all partitions are initialized and the base environment installed, it is time to enter the new installation environment by chrooting into it. This means that the session will change its root most top-level location that can be accessed from the current installation environment installation CD or other installation medium to the installation system namely the initialized partitions.
Hence the name, change root or chroot. From this point, all actions performed are immediately on the new Gentoo Linux environment. Of course it is far from finished, which is why the installation still has some sections left! Now that the new environment has been entered, it is necessary to mount the boot partition. This will be important when it is time to compile the kernel and install the bootloader:.
Next step is to install a snapshot of the Gentoo ebuild repository. This snapshot contains a collection of files that informs Portage about available software titles for installation , which profiles the system administrator can select, package or profile specific news items, etc.
Readers who have no network or bandwidth restrictions can happily skip down to the next section. This will fetch the latest snapshot which is released on a daily basis from one of Gentoo's mirrors and install it onto the system:. From this point onward, Portage might mention that certain updates are recommended to be executed. This is because system packages installed through the stage file might have newer versions available; Portage is now aware of new packages because of the repository snapshot.
Package updates can be safely ignored for now; updates can be delayed until after the Gentoo installation has finished. It is possible to update the Gentoo ebuild repository to the latest version.
The previous emerge-webrsync command will have installed a very recent snapshot usually recent up to 24h so this step is definitely optional. Suppose there is a need for the last package updates up to 1 hour , then use emerge --sync. This command will use the rsync protocol to update the Gentoo ebuild repository which was fetched earlier on through emerge-webrsync to the latest state.
On slow terminals, like some framebuffers or serial consoles, it is recommended to use the --quiet option to speed up the process:. When the Gentoo ebuild repository is synchronized, Portage may output informational messages similar to the following:. News items were created to provide a communication medium to push critical messages to users via the Gentoo ebuild repository.
To manage them, use eselect news. The eselect application is a Gentoo-specific utility that allows for a common management interface for system administration. In this case, eselect is asked to use its news module. A profile is a building block for any Gentoo system. These settings are all maintained by Gentoo's Portage developers.
You can see what profile the system is currently using with eselect , now using the profile module:. After viewing the available profiles for the amd64 architecture, users can select a different profile for the system:.
In order to select a pure bit environment, with no bit applications or libraries, use a no-multilib profile:. At this point, it is wise to update the system's world set so that a base can be established.
This following step is necessary so the system can apply any updates or USE flag changes which have appeared since the stage3 was built and from any profile selection:. USE is one of the most powerful variables Gentoo provides to its users.
Several programs can be compiled with or without optional support for certain items. Others can be compiled with or without SSL support. Some programs can even be compiled with framebuffer support svgalib instead of X11 support X-server. Most distributions compile their packages with support for as much as possible, increasing the size of the programs and startup time, not to mention an enormous amount of dependencies. With Gentoo users can define what options a package should be compiled with.
This is where USE comes into play. In the USE variable users define keywords which are mapped onto compile-options.
For instance, ssl will compile SSL support in the programs that support it. The default USE settings are placed in the make. Gentoo uses a complex inheritance system for its profiles, which we will not dive into at this stage. The easiest way to check the currently active USE settings is to run emerge --info and select the line that starts with USE:. USE flags can be globally removed by adding a - minus sign in front of the value in the the list. For example, to disable support for X graphical environments, -X can be set:.
All of the Gentoo packages are tagged with the license s the package falls under. This allows users to select software by specific licenses or groups of licenses prior to installing it.
The license groups defined in the Gentoo repository, managed by the Gentoo Licenses project , are:. The default value will only accept licenses that are explicitly approved by the Free Software Foundation, the Open Source Initiative, or that follow the Free Software Definition:. If systemd is desired, please consult the systemd article.
It contains instructions equivalent to the instructions in the following sections of this Handbook. Specifically, it will walk the reader through various init system commands systemctl and systemd-specific services such as timedatectl , hostnamectl , etc.
Select the timezone for the system. Later, when systemd is running, the timezone and related settings can be configured with the timedatectl command.
Locales specify not only the language that the user should use to interact with the system, but also the rules for sorting strings, displaying dates and times, etc.
Locales are case sensitive and must be represented exactly as described. The next step is to run the locale-gen command. To verify that the selected locales are now available, run locale -a. Once done, it is now time to set the system-wide locale settings.
Again we use eselect for this, now with the locale module. With eselect locale list , the available targets are displayed:. Setting the locale will avoid warnings and errors during kernel and software compilations later in the installation. A full Localization guide to provide additional guidance through the locale selection process. Before getting to configuring kernel sections, it is beneficial to be aware that some devices require additional firmware to be installed on the system before they will operate correctly.
This is often the case for network interfaces, especially wireless network interfaces commonly used in both desktop and laptop computers. Modern video chips from vendors like AMD, Nvidia, and Intel, often need external firmware files to be fully functional. On systems using graphics cards from these vendors, it is wise to emerge this firmware package in order to have it available before configuring and compiling the kernel.
In addition to discrete graphics hardware and network interfaces, CPUs also can require firmware updates. Typically this kind of firmware is referred to as microcode. Newer revisions of microcode are sometimes necessary to patch instability, security concerns, or other bugs in CPU hardware.
See the Microcode article for more information on how to apply microcode updates. Manual configuration is explained as the default choice since it is the best way to optimize an environment.
The core around which all distributions are built is the Linux kernel. It is the layer between the user programs and the system hardware. Gentoo provides its users several possible kernel sources. A full listing with description is available at the Kernel overview page. Choose an appropriate kernel source and install it using emerge :. However, this symbolic link will not be created by default. An easy way to create the symbolic link is to utilize eselect's kernel module.
In order to create a symbolic link called linux , use:. Manually configuring a kernel is often seen as the most difficult procedure a Linux user ever has to perform. Nothing is less true - after configuring a couple of kernels no one remembers that it was difficult! However, one thing is true: it is vital to know the system when a kernel is configured manually. Another source of system information is to run lsmod to see what kernel modules the installation CD uses as it might provide a nice hint on what to enable.
Now go to the kernel source directory and execute make menuconfig. This will fire up menu-driven configuration screen. The Linux kernel configuration has many, many sections. Let's first list some options that must be activated otherwise Gentoo will not function, or not function properly without additional tweaks.
We also have a Gentoo kernel configuration guide on the Gentoo wiki that might help out further. These ensure that a minimum of kernel features required for proper functioning is available:. Naturally the choice in the last two lines depends on the selected init system OpenRC vs.
It does not hurt to have support for both init systems enabled. Enabling support is possible, but goes beyond the scope of the handbook. Make sure that every driver that is vital to the booting of the system such as SCSI controller, etc. Next select the exact processor type. It is also recommended to enable MCE features if available so that users are able to be notified of any hardware problems.
Now go to File Systems and select support for the filesystems that will be used by the system. Do not compile the file system that is used for the root filesystem as module, otherwise the system may not be able to mount the partition.
The two compression options won't harm but are not definitely needed, neither does the PPP over Ethernet option, that might only be used by ppp when configured to do kernel mode PPPoE. With the configuration now done, it is time to compile and install the kernel. Exit the configuration and start the compilation process:. This is handled by the make install command:. In certain cases it is necessary to build an initramfs - an initial ram-based file system.
With an initramfs, these partitions can be mounted using the tools available inside the initramfs. Without an initramfs, there is a huge risk that the system will not boot up properly as the tools that are responsible for mounting the file systems need information that resides on those file systems. An initramfs will pull in the necessary files into an archive which is used right after the kernel boots, but before the control is handed over to the init tool.
Scripts on the initramfs will then make sure that the partitions are properly mounted before the system continues booting. See genkernel --help for more information. The resulting file can be found by simply listing the files starting with initramfs :. If a manual configuration looks too daunting, then consider using genkernel.
It will configure and build the kernel automatically. This means that when genkernel is used to build the kernel, the system will generally detect hardware it was built for support with at boot-time, just like the installation CD does. Note that genkernel does not automatically generate a custom kernel configuration the hardware on which it is being run.
Now, let's see how to use genkernel. This would make the entry in the file look like so:. Now, compile the kernel sources by running genkernel all. Be aware though, as genkernel compiles a kernel that supports almost all hardware, this compilation will take quite a while to finish! Once genkernel completes, a kernel, full set of modules and initial ram disk initramfs will be created. We will use the kernel and initrd when configuring a boot loader later in this document. Write down the names of the kernel and initrd as this information is used when the boot loader configuration file is edited.
The initrd will be started immediately after booting to perform hardware autodetection just like on the installation CD before the "real" system starts up. Distribution Kernels are ebuilds that cover the complete process of unpacking, configuring, compiling, and installing the kernel. The primary advantage of this method is that the kernels are upgraded to new versions as part of world upgrade without a need for manual action.
There are other methods available to customize the kernel config such as config snippets. Before using the distribution kernels, please verify that the correct installkernel package for the system is installed. When using systemd-boot formerly gummiboot , install:.
If in doubt:. System administrators who want to avoid compiling the kernel sources locally can instead use precompiled kernel images:. Once the kernel is installed, the package manager will automatically upgrade it to newer versions. The previous versions will be kept until the package manager is requested to clean up stale packages.
Please remember to periodically run:. Distribution kernels are now capable of rebuilding kernel modules installed by other packages. To view all available modules, run the following find command. For instance, to automatically load the 3c59x. The actual file name is insignificant to the loader. Continue the installation with Configuring the system. This file contains the mount points of those partitions where they are seen in the file system structure , how they should be mounted and with what special options automatically or not, whether users can mount them or not, etc.
Every line consists of six fields, separated by whitespace space s , tabs or a mixture. Each field has its own meaning:. Partition labels and partition UUIDs can be used to identify the block device's individual partition s , regardless of what filesystem has been chosen for the partition itself. While not always true for partition labels, using a UUID to identify a partition in fstab provides a guarantee that the bootloader will not be confused when looking for a certain volume, even if the filesystem would be changed in the future.
The naming for block device files depends on a number of factors, including how and in what order the disks are attached to the system. They also could show up in a different order depending on which of the devices are detected by the kernel first during the early boot process.
With this being stated, unless one intends to constantly fiddle with the disk ordering, using default block device files is a simple and straightforward approach. This is just an example, and should be modified according to the partitioning decisions made earlier in the installation. It needs to be checked during boot, so we would write down:.
Those people should substitute defaults with noauto. This does mean that those users will need to manually mount this partition every time they want to use it. Add the rules that match the previously decided partitioning scheme and append rules for devices such as CD-ROM drive s , and of course, if other partitions or drives are used, for those too. When auto is used in the third field, it makes the mount command guess what the filesystem would be.
This is recommended for removable media as they can be created with one of many filesystems. The user option in the fourth field makes it possible for non-root users to mount the CD. To improve performance, most users would want to add the noatime mount option, which results in a faster system since access times aren't registered those are not needed generally anyway.
This is also recommended for solid state drive SSD users, who should also enable the discard mount option ext4 and btrfs only for now which makes the TRIM command work.
This seems to be quite easy, but lots of users are having difficulties finding the appropriate name for their Linux PC. To speed things up, know that the decision is not final - it can be changed afterwards. In the examples below, the hostname tux is used within the domain homenetwork. To set the system hostname on systemd, run hostnamectl. An alternative to using neticrc is dhcpcd. See Dhcpcd for more details. There are many options available for configuring network interfaces. This section covers a only a few methods.
Choose the one which seems best suited to the setup needed. During the Gentoo Linux installation, networking was already configured. However, that was for the installation CD itself and not for the installed environment. Right now, the network configuration is made for the installed Gentoo Linux system. It uses a straightforward yet perhaps not intuitive syntax.
But don't fear, everything is explained below. DHCP is used by default. This is described later in Installing Necessary System Tools. If the system has several network interfaces, then the appropriate net. If after booting the system we find out that the assumption about the network interface name which is currently documented as eth0 was wrong, then execute the following steps to rectify this:. Next inform Linux about the network environment. Set the root password using the passwd command.
The root Linux account is an all-powerful account, so pick a strong password. Later an additional regular user account will be created for daily operations. Review the settings and change where needed. Edit it to configure and select the right keyboard. Take special care with the keymap variable. If the wrong keymap is selected, then weird results will come up when typing on the keyboard.
Edit it according to personal preference. Otherwise the system might show clock skew behavior. It's recommended to run systemd-firstboot --prompt --setup-machine-id to ensure the system is setup correctly, but the necessary steps can be run individually too. Some tools are missing from the stage3 archive because several packages provide the same functionality.
It is now up to the user to choose which ones to install. The first tool to decide on has to provide logging facilities for the system. Unix and Linux have an excellent history of logging capabilities - if needed, everything that happens on the system can be logged in log files.
This happens through the system logger. Others are available through Portage as well - the number of available packages increases on a daily basis. To install the system logger of choice, emerge it. On OpenRC, add it to the default runlevel using rc-update. Next is the cron daemon.
Although it is optional and not required for every system, it is wise to install one. A cron daemon executes scheduled commands. It is very handy if some command needs to be executed regularly for instance daily, weekly or monthly.
Installing one of them is similar to installing a system logger. To be able to access the system remotely after installation, sshd must be configured to start on boot. To add the sshd init script to the default runlevel on OpenRC:. If serial console access is needed which is possible in case of remote servers , agetty must be configured. Depending on the filesystems used, it is necessary to install the required file system utilities for checking the filesystem integrity, creating additional file systems etc.
If networking was previously configured in the Configuring the system step and network setup is complete, then this 'networking tools' section can be safely skipped.
In this case, proceed with the section on Configuring a bootloader. In order for the system to automatically obtain an IP address for one or more network interface s using netifrc scripts, it is necessary to install a DHCP client.
More information on dhcpcd can be found in the dhcpcd article. Now continue with Configuring the bootloader. With the Linux kernel configured, system tools installed and configuration files edited, it is time to install the last important piece of a Linux installation: the boot loader.
The boot loader is responsible for firing up the Linux kernel upon boot - without it, the system would not know how to proceed when the power button has been pressed.
In this section of the Handbook a delineation has been made between emerging the boot loader's package and installing a boot loader to a system disk. Here the term emerge will be used to ask Portage to make the software package available to the system. The term install will signify the boot loader copying files or physically modifying appropriate sections of the system's disk drive in order to render the boot loader activated and ready to operate on the next power cycle.
With a small amount of configuration, necessary before build time, GRUB2 can support more than a half a dozen additional platforms. The GRUB installer can perform this operation automatically with the --removable option.
Verify the ESP is mounted before running the following commands. This creates the default directory defined by the UEFI specification, and then copies the grubx To generate the final GRUB2 configuration, run the grub-mkconfig command:.
The output of the command must mention that at least one Linux image is found, as those are needed to boot the system. If an initramfs is used or genkernel was used to build the kernel, the correct initrd image should be detected as well.
If the files are indeed missing, go back to the kernel configuration and installation instructions. However, it lacks features when compared to GRUB. Of course, it is also used because some people know LILO and want to stick with it. Either way, Gentoo supports both bootloaders. In the configuration file, sections are used to refer to the bootable kernel. Make sure that the kernel files with kernel version and initramfs files are known, as they need to be referred to in this configuration file.
If an initramfs is necessary, then change the configuration by referring to this initramfs file and telling the initramfs where the root device is located:. If additional options need to be passed to the kernel, use an append statement. For instance, to add the video statement to enable framebuffer:. Users that used genkernel should know that their kernels use the same boot options as is used for the installation CD. For instance, if SCSI device support needs to be enabled, add doscsi as kernel option.
Such systems do not need to have additional also known as secondary bootloaders like GRUB2 in order to help boot the system. Using efibootmgr is really for those who desire to take a minimalist although more rigid approach to booting their system; using GRUB2 see above is easier for the majority of users because it offers a flexible approach when booting UEFI systems.
Be sure to read through the EFI stub kernel article before continuing. The kernel must have specific options enabled to be directly bootable by the system's UEFI firmware. It might be necessary to recompile the kernel. It is also a good idea to take a look at the efibootmgr article. With these changes done, when the system reboots, a boot entry called "Gentoo" will be available.
Syslinux is yet another bootloader alternative for the amd64 architecture. It supports MBR and, as of version 6. PXE network boot and lesser-known options are also supported. Although Syslinux is a popular bootloader for many it is unsupported by the Handbook.
Readers can find information on emerging and then installing this bootloader in the Syslinux article. Exit the chrooted environment and unmount all mounted partitions. Then type in that one magical command that initiates the final, true test: reboot. Do not forget to remove the bootable CD, otherwise the CD might be booted again instead of the new Gentoo system.
Once rebooted in the freshly installed Gentoo environment, finish up with Finalizing the Gentoo installation.
0コメント