Updated section Installation to f44
pboy
BIN
modules/ROOT/assets/images/.DS_Store
vendored
BIN
modules/ROOT/assets/images/installation/grub-boot-screen-f44.png
Normal file
|
After Width: | Height: | Size: 10 KiB |
|
Before Width: | Height: | Size: 89 KiB After Width: | Height: | Size: 10 KiB |
|
Before Width: | Height: | Size: 173 KiB After Width: | Height: | Size: 10 KiB |
|
Before Width: | Height: | Size: 205 KiB |
|
Before Width: | Height: | Size: 262 KiB After Width: | Height: | Size: 127 KiB |
|
Before Width: | Height: | Size: 202 KiB After Width: | Height: | Size: 90 KiB |
|
Before Width: | Height: | Size: 172 KiB After Width: | Height: | Size: 73 KiB |
|
Before Width: | Height: | Size: 173 KiB After Width: | Height: | Size: 10 KiB |
|
Before Width: | Height: | Size: 295 KiB After Width: | Height: | Size: 165 KiB |
|
After Width: | Height: | Size: 261 KiB |
|
Before Width: | Height: | Size: 261 KiB After Width: | Height: | Size: 127 KiB |
|
|
@ -1,8 +1,8 @@
|
|||
= Fedora Server interactive local installation
|
||||
Peter Boy; Stephen Daley; Kevin Fenzi
|
||||
Peter Boy; Kevin Fenzi; Emmanuel Seyman
|
||||
:page-authors: {author}, {author_2}, {author_3}
|
||||
:revnumber: F37-F44
|
||||
:revdate: 2026-??-??
|
||||
:revnumber: F33-F44
|
||||
:revdate: 2026-04-28
|
||||
|
||||
:page-aliases: pages/installation-interactive-local.adoc
|
||||
|
||||
|
|
@ -27,7 +27,7 @@ This is the default method for manually installing Fedora if console access is a
|
|||
With all xref:index.adoc[preparations and installation plans] complete, insert the prepared installation medium and boot the server. After some time you get the boot menu screen.
|
||||
|
||||
.The Fedora boot screen
|
||||
image::installation/interactive-local-010.png[The boot screen]
|
||||
image::installation/interactive-local-010.png[]
|
||||
|
||||
The second option, _Test this media & install Fedora Server_, is selected as default. Before the first usage, testing the installation media is strongly recommended. Subsequent installations can dispense with this and select the first option.
|
||||
|
||||
|
|
@ -37,7 +37,8 @@ First, the program asks for the language to be used during the installation phas
|
|||
|
||||
Anaconda will display the following installation overview, with all available configuration options.
|
||||
|
||||
image::installation/interactive-local-020.png[Anaconda Installation Summary]
|
||||
.The Anaconda Installation Summary
|
||||
image::installation/interactive-local-020.png[]
|
||||
|
||||
|
||||
== Server installation steps
|
||||
|
|
@ -94,7 +95,8 @@ Alternatively, you may manually select a server repository directly.
|
|||
|
||||
=== Installation Destination
|
||||
|
||||
image::installation/interactive-local-050.png[Anaconda Installation Destination]
|
||||
.The Anaconda Installation Destination Screen
|
||||
image::installation/interactive-local-050.png[]
|
||||
|
||||
Select one or more disks on which to install Fedora Server. You have several options.
|
||||
|
||||
|
|
@ -119,7 +121,7 @@ The Advanced Custom option also opens up this option, but you have to perform al
|
|||
The _Add a disk_ enables you to include external storages, e.g. a SAN (Storage Attached Network) or other network attached drives as part of your Fedora Server install in this same configuration screen. However, this configuration is not covered here in this installation guide.
|
||||
|
||||
==== Automatic default configuration
|
||||
If you are satisfied with the Fedora Server default hard disk partitioning as described in the xref:installation/index.adoc#_what_default_partitioning_does[Server installation] introduction, you can leave _Automatic_ checked under __Storage Configuration__.
|
||||
If you are satisfied with the Fedora Server default hard disk partitioning as described in the xref:installation/index.adoc#_what_default_partitioning_does[Server installation] introduction, you can leave __Automatic__ checked under __Storage Configuration__.
|
||||
|
||||
[TIP]
|
||||
====
|
||||
|
|
@ -137,8 +139,8 @@ If you selected the option to free up space, a window will open after you click
|
|||
|
||||
Select _Custom_ Storage Configuration instead of _Automatic_ and select _Done_ in the upper bar. Anaconda will take you to the _Manual Partitioning_ form.
|
||||
|
||||
.Anaconda Manual Partitioning form
|
||||
image::installation/interactive-local-070.png[Anaconda Manual Partitioning form]
|
||||
.The Anaconda Manual Partitioning form
|
||||
image::installation/interactive-local-070.png[]
|
||||
|
||||
By clicking onto the + sign you can add partitions according to your storage concept.
|
||||
|
||||
|
|
@ -170,9 +172,6 @@ By default the installation program creates a DHCP configuration for each networ
|
|||
|
||||
In case of servers it is often preferable to configure a static IP address. This ensures a valid network connection at system start even if the DHCP server is defective. Select the network interface, activate the IPv4 or IPv6 tab. Switch from "Automatic (DHCP)" to "Manual" and add an IP specification.
|
||||
|
||||
NOTE: Post Fedora 36, NetworkManager stores the configuration exclusively in __/etc/NetworkManager/connected_systems/*.network__. The former /etc/sysconfig/network-scripts directory is no longer supported at all.
|
||||
|
||||
|
||||
|
||||
|
||||
=== Creating users
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
= Excursus: Configuring a software RAID upon interactive installation
|
||||
Peter Boy; Stephen Daley; Kevin Fenzi
|
||||
:page-authors: {author}, {author_2}, {author_3}
|
||||
:revnumber: F37-F42
|
||||
:revdate: 2025-08-20
|
||||
:revnumber: F37-F44
|
||||
:revdate: 2026-04-28
|
||||
|
||||
[abstract]
|
||||
This Exkurs describes the configuration of a _software RAID_ as part of an interactive Fedora Server Edition installation. In this case, the RAID capability is provided by operating system drivers and processed bei the computer CPU. It does not cover firmware raid (also called Windows RAID), which provide this capability via the computer internal firmware, nor hardware raid, where dedicated integrated hardware modules or adapters completely relieve the computer CPU of the raid processing.
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
= Virtualization
|
||||
Fredrik Arneving; Peter Boy; Jan Kuparinen
|
||||
:page-authors: {author}, {author_2}, {author_3}
|
||||
:revnumber: F35-F41
|
||||
:revdate: 2024-10-15
|
||||
:revnumber: F35-F44
|
||||
:revdate: 2026-04-28
|
||||
|
||||
:page-aliases: pages/virtualization-an-introduction.adoc
|
||||
|
||||
|
|
@ -49,14 +49,12 @@ Technically, KVM follows a different approach as XEN. It requires an already ins
|
|||
|
||||
Fedora was an early adoptor of **KVM/Qemu** and it is *natively supported by Fedora Server*.
|
||||
|
||||
=== Fedora recommended Virtualization
|
||||
|
||||
Fedora Project decided some time ago to replace XEN as the preferred virtualization and use KVM as default instead.
|
||||
|
||||
Due to the 'Type-2'-like concept of KVM, Fedora Server Edition is first installed and configured as usual. System software required for virtualization is not automatically installed. In a second step, virtualization capabilities are added (it can be added as an option during installation to combine both into one step on the surface. However, a subsequent, precisely fitting installation is very much preferrable).
|
||||
KVM is the default and recommended virtualisation technique in Fedora for a while.
|
||||
|
||||
== Adding Virtualization Support
|
||||
|
||||
Due to the 'Type-2'-like concept of KVM, Fedora Server Edition is first installed and configured as usual. System software required for virtualization is not automatically installed. In a second step, virtualization capabilities are added.
|
||||
|
||||
This step includes the xref:virtualization/installation.adoc[installation of the libvirt software and further configuration] steps. For example, external connectivity must be set up for virtual machines, e.g. through a virtual bridge or mac-vlan. Often, an internal network is also required for protected communication between the virtual machines or with the host system.
|
||||
|
||||
After Fedora Server is enabled for virtualization, one or more virtual machines can be installed. This might be Fedora Server, or any other Linux distribution.
|
||||
|
|
@ -98,12 +96,6 @@ The article xref::virtualization/vm-install-diskimg-fedoraserver.adoc[Creating a
|
|||
|
||||
There are several offerings available
|
||||
|
||||
* *ImageFactory*
|
||||
+
|
||||
This is the tool that Fedora Release Engineering currently uses to create the various Fedora VM images. You can install the program on your local hard drive and use it to create your own Fedora VM image. By default, it uses Fedora rpm packages and the various Fedora VM images are available in source code, which you can copy and customize to your specific requirements. This way you get an image that is as close as possible to the images provided by Fedora.
|
||||
+
|
||||
The article xref::tutorials/imagefactory.adoc[ImageFactory – How to Create a Virtual Machine Disk Image] describes the process in detail.
|
||||
|
||||
* *Virtual Builder*
|
||||
+
|
||||
The guestfs-tools, included in the xref::virtualization/installation.adoc#_installing_libvirt_virtualization_software[Adding Virtualization Support] installation task, include the __virt-builder__ tool to create a partly customized disk image (e.g. root password). You get a disk image file pretty quickly and importing it into KVM is easy and fast as well.
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
= Adding Virtualization Support
|
||||
Fredrik Arneving; Peter Boy; Jerry James
|
||||
:page-authors: {author}, {author_2}, {author_3}
|
||||
:revnumber: F38-F41
|
||||
:revdate: 2024-10-15
|
||||
:revnumber: F38-F44
|
||||
:revdate: 2026-04-28
|
||||
|
||||
:page-aliases: pages/virtualization-install.adoc
|
||||
|
||||
|
|
|
|||