Updated article Postinstallation Tasks.

modules/ROOT/pages/installation/postinstallation-tasks.adoc

@@ -1,8 +1,8 @@
 = Post Installation Tasks
 Peter Boy; Stephen Daley; Kevin Fenzi
 :page-authors: {author}, {author_2}, {author_3}
-:revnumber: F36-F43
-:revdate: 2024-10-15
+:revnumber: F36-F44
+:revdate: 2026-04-28
 
 :page-aliases: pages/sysadmin-postinstall.adoc
 
@@ -14,19 +14,21 @@ This guide offers a recommended checklist of tasks to ensure the safe and reliab
 
 // Before publishing, comment out the warning.
 // Comment in again when start to update.
-[WARNING]
-====
-This document is not approved yet and may be incomplete and/or incorrect. 
+//[WARNING]
+//====
+//This document is not approved yet and may be incomplete and/or incorrect. 
 
-*Status of this document*: Updated to f44.
+//*Status of this document*: Updated to f44.
 
-ToDo:
+//ToDo:
 
-* Update images from F43 toF44
-* Update complete text
-====
+//* Update images from F43 toF44
+//* Update complete text
+//====
 
-To perform the administrative tasks described here, you need either any Linux or any macOS desktop or laptop. On Windows computers, you need at least Windows 10 1809 or additional programs such as Putty.
+The following descriptions assume that the administrator is working at their workstation and accessing the server via SSH. However, most of the configuration instructions described can also be executed on the server console.
+
+SSH is included by default on Linux and macOS. Windows 10 requires at least version 1809 or the additional program putty.
 
 == Simplified access for the administrative account
 
@@ -322,16 +324,18 @@ Depending on how you decided on data storage during installation, different supp
 
 a. If you have chosen the _Default_ partitioning and are content with the basic principle of creating logical volumes for user and any other payload data, there is nothing to do at the moment. The creation of these logical volumes happens in the context of the installation of the corresponding application software. 
 +
-You may ensure that the volume group – default name `fedora` – fills the complete disk. Using Cockpit, in the section `Devices` choose the volume group. At the top of the new window it shows its total capacity.
+You may ensure that the volume group – default name `fedora` – fills the complete disk. Using Cockpit, in the section `Storage` you see the available devices and their partitioning as well as Volume Group and Logical Volumes.
 
-b. If you have chosen the _Default_ partitioning but are _not content_ with the basic principle of creating Logical volumes for user and any other payload data you have now to extend the existing root logical volume to accomodate your data. Cockpit provides an easy way for this. Choose _Grow_. Determine the new size as needed.
+b. If you have chosen the _Default_ partitioning but are _not content_ with the basic principle of creating Logical volumes for user and any other payload data but prefer to store everything in one big filesystem,  you have now to extend the existing root logical volume to accomodate your data. 
 +
 [CAUTION]
 ====
 This is not a recommended procedure! Don't complain in case of issues.
 ====
++
+Cockpit provides an easy way for this. On the right side of the 'root' filesytem line select the 3 dot button. Choose _Grow_ for the logical volume. Determine the new size as needed.
 
-c. If you have decided for a stricter _separation of system and payload data_ and created a small Volume Group for system data, you may have already created an additional partition and Volume Group in Anaconda. Otherwise you have to create it here.
+c. If you have decided for a stricter _separation of system and payload data_ by using a separate volume group for each, you may have already created an additional partition and Volume Group in Anaconda. Otherwise you have to create it now.
 +
 Select `Storage` in Cockpit's main menu and then your drive  in the right column. Select `Create new partition` and fill in the upcomming form accordingly. In the box "Devices" select from the Menu "Create LVM2 volume group" and fill in the upcomming form accordingly.
 

modules/ROOT/partials/installation/post-install/install-fail2ban.adoc

@@ -1,8 +1,8 @@
 // Text excerpt about installing fail2ban
 // consumer postinstallation-tasks.adoc (main), hetzner-dc.adoc
-The software monitors the log files for authentication errors. In case of multiple retries from the same IP address, it reconfigures the firewall on the fly to block the source IP  This is to prevent brute force methods for cracking passwords and bots checking for weak passwords. However, a system administrator may also lock himself out, if if they happen to make a mistake. Therefore, you can exclude destinct IP addresses, e.g. the administrators desktop, from blocking. 
+The software monitors the log files for authentication errors. In case of multiple retries from the same IP address, it reconfigures the firewall on the fly to block the source IP.  This is to prevent brute force methods for cracking passwords and bots checking for weak passwords. However, a system administrator may also lock himself out, if they happen to make a mistake. Therefore, you can exclude destinct IP addresses, e.g. the administrators desktop, from blocking. 
 
-a. Installation of the software and the required Postfix
+a. Installation of the software 
 +
 [source,]
 ----

modules/ROOT/partials/installation/post-install/manage-dnf-updates.adoc

@@ -1,5 +1,6 @@
 // Text excerpt about managing system updates.
 // consumer postinstallation-tasks.adoc (main), hetzner-dc.adoc
+//
 Fedora includes a tool, dnf-automatic, which supports several modes of update automation: 
 do not apply, notify admin, apply and notify admin, apply without notification. In particular, alternatives 2 and 3 are definitely worth considering. A general principle might be: Alternative 2 is the minimum choice for almost any system, alternative 3 is not at all suitable for critical systems that must not fail under any circumstances.