| |
@@ -14,7 +14,7 @@
|
| |
[[pxe-overview]]
|
| |
== PXE Installation Overview
|
| |
|
| |
- Preboot Execution Environment, or PXE, is a techonology that allows computers to boot directly from resources provided over the network. Installing Fedora over the network means you don't have to create media, and you can install to multiple computers or virtual machine simultaneously. The process involves a number of components and features working together to provide the resources required.
|
| |
+ Preboot Execution Environment, or PXE, is a techonology that allows computers to boot directly from resources provided over the network. Installing {PRODUCT} over the network means you don't have to create media, and you can install to multiple computers or virtual machine simultaneously. The process involves a number of components and features working together to provide the resources required.
|
| |
|
| |
.PXE-capable computer
|
| |
Most modern computers have the capability to network boot. Typically, a function key pressed during boot will bring up a boot selection menu. In environments designed for unattended administration, systems will often be configured to first attempt booting from the network, then boot from local storage, and the installation server is configured to only offer the installation when required. Your computer's manual will provide specific instructions on setting boot priorities.
|
| |
@@ -32,7 +32,7 @@
|
| |
The kernel is the core of any Linux operating system, and the initramfs provides the kernel with required tools and resources. These files are also provided by tftp.
|
| |
|
| |
.Package repository
|
| |
- A Fedora repository must be available for the installation. The example in this section uses the public Fedora mirrors as the repository source, but you can also use a repo on the local network provided by NFS, FTP, or HTTP. Repositories can be configured using the [option]#inst.repo=# boot option; see xref:advanced/Boot_Options.adoc#sect-boot-options-sources[Specifying the Installation Source] for details.
|
| |
+ A {PRODUCT} repository must be available for the installation. The example in this section uses the public {PRODUCT} mirrors as the repository source, but you can also use a repo on the local network provided by NFS, FTP, or HTTP. Repositories can be configured using the [option]#inst.repo=# boot option; see xref:advanced/Boot_Options.adoc#sect-boot-options-sources[Specifying the Installation Source] for details.
|
| |
|
| |
//A link to mirrormanager and some instructions to other guides too. All the elaboration on installation methods might be going to far, but we can ref. --Pete
|
| |
|
| |
@@ -252,7 +252,7 @@
|
| |
|
| |
HTTP/HTTPS boot is a technology that allows computers to boot directly from resources provided over the network. When used in conjunction with HTTPS the authenticity of the server is validated, and the use of HTTP offers a more reliable transport mechanism than PXE's TFTP. Installing Fedora this way avoids creating install media and allows multiple computers to install simultaneously. Many current UEFI implementations, including the EDK2 based firmware shipping with fedora's virtualization solutions, can directly boot from HTTP sources. A UEFI boot entry may be manually added that specifies a HTTP source via firmware menus. Alternatively, a DHCP server may automatically provide the required HTTP path.
|
| |
|
| |
- .Enrolling Certificatesll
|
| |
+ .Enrolling Certificates
|
| |
While many machines are capable of HTTPS boot as well as HTTP, they will frequently need to have a certificate authority (CA) enrolled first. The CA is used to validate the certificates presented by the HTTPS server. This may be accomplished by enrolling the appropriate files from the fedora provided ca-certificates for public mirrors or the local HTTPS boot server's certificate.
|
| |
|
| |
|
| |
rffontenelle
commented 2 years ago
Use PRODUCT instead of "Fedora" (like in many places), and fix typo in "Enrolling Certificates"