Merge branch 'Lemanr-ops-f36-patch-60537' into 'f36'

Update System_Locale_and_Keyboard_Configuration.adoc

See merge request fedora/docs/fedora-linux-documentation/fedora-linux-sysadmin-guide!7

antora.yml

@@ -1,5 +1,5 @@
 ---
 name: fedora
-version: rawhide
+version: f36
 # Navigation is in the main 'fedora' component:
 # https://pagure.io/fedora-docs/release-docs-home

modules/system-administrators-guide/pages/Preface.adoc

@@ -83,7 +83,7 @@ xref:monitoring-and-automation/OProfile.adoc[OProfile] covers [application]*OPro
 
 xref:kernel-module-driver-configuration/intro-kernel-module-driver-configuration.adoc[Kernel, Module and Driver Configuration]::  This part covers various tools that assist administrators with kernel customization.
 +
-xref:kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader.adoc[Working with the GRUB 2 Boot Loader] der>> describes the GNU GRand Unified Boot loader (GRUB) version 2 boot loader, which enables selecting an operating system or kernel to be loaded at system boot time.
+xref:kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader.adoc[Working with the GRUB 2 Boot Loader] describes the GNU GRand Unified Boot loader (GRUB) version 2 boot loader, which enables selecting an operating system or kernel to be loaded at system boot time.
 +
 xref:kernel-module-driver-configuration/Manually_Upgrading_the_Kernel.adoc[Manually Upgrading the Kernel] provides important information on how to manually update a kernel package using the [command]#rpm# command instead of [command]#dnf#. Read this chapter if you cannot update a kernel package with the [application]*DNF* package manager.
 +

modules/system-administrators-guide/pages/_partials/entities.adoc

@@ -4,7 +4,7 @@
 :MAJOROS: Fedora
 :MAJOROSVER: Fedora Rawhide
 :OSORG: The Fedora Project
-:PKGOS: fc35
+:PKGOS: fc36
 :PRODUCT: Fedora Documentation
-:PRODVER: Rawhide
-:YEAR: 2021
+:PRODVER: 36
+:YEAR: 2022

modules/system-administrators-guide/pages/basic-system-configuration/System_Locale_and_Keyboard_Configuration.adoc

@@ -1,4 +1,3 @@
-
 :experimental:
 include::{partialsdir}/entities.adoc[]
 
@@ -249,6 +248,24 @@ Apart from keyboard layout (_map_), three other options can be specified:
 Replace _model_ with the keyboard model name,
 _variant_ and _options_ with keyboard variant and option components, which can be used to enhance the keyboard behavior. These options are not set by default. For more information on X11 Model, X11 Variant, and X11 Options see the `kbd(4)` man page.
 
+[[s2-If_Using_Gnome]]
+=== Consider this option if using gnome
+
+This should work if the following conditions apply:
+
+* Using gnome as the desktop envirnment
+
+* Your layout is not listed under Settings -> Keyboard -> Input Sources 
+
+In your terminal type in:
+
+`gsettings set org.gnome.desktop.input-sources show-all-sources true`
+
+after pressing return, try looking under your keyboard settings again as there should be a lot more options available.
+As the proper source for help is gnome in this case, here is more information from gnome:
+
+https://help.gnome.org/users/gnome-help/stable/keyboard-layouts.html.en
+
 [[sect-Keyboard_Configuration-Resources]]
 == Additional Resources
 

modules/system-administrators-guide/pages/kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader.adoc

@@ -10,7 +10,7 @@ indexterm:[GRUB 2,configuring GRUB 2]indexterm:[GRUB 2,reinstalling GRUB 2]index
 [[sec-Introduction_to_GRUB_2]]
 == Introduction to GRUB 2
 
-GRUB 2 reads its configuration from the `/boot/grub2/grub.cfg` file on traditional BIOS-based machines and from the `/boot/efi/EFI/fedora/grub.cfg` file on UEFI machines. This file contains menu information.
+GRUB 2 reads its configuration from the `/boot/grub2/grub.cfg` file. This file contains menu information.
 
 The GRUB 2 configuration file, `grub.cfg`, is generated during installation, or by invoking the [application]*/usr/sbin/grub2-mkconfig* utility, and is automatically updated by [command]#grubby# each time a new kernel is installed. When regenerated manually using [application]*grub2-mkconfig*, the file is generated according to the template files located in `/etc/grub.d/`, and custom settings in the `/etc/default/grub` file. Edits of `grub.cfg` will be lost any time [application]*grub2-mkconfig* is used to regenerate the file, so care must be taken to reflect any manual changes in `/etc/default/grub` as well.
 
@@ -277,20 +277,13 @@ The file name `/etc/grub2.cfg` is a symlink to the `grub.cfg` file, whose locati
 
 Changes to `/etc/default/grub` require rebuilding the `grub.cfg` file as follows:
 
-* On BIOS-based machines, issue the following command as `root`:
+* On both UEFI-based and BIOS-based machines, issue the following command as `root`:
 
 [subs="attributes"]
 ----
 ~]#{nbsp}grub2-mkconfig -o /boot/grub2/grub.cfg
 ----
 
-* On UEFI-based machines, issue the following command as `root`:
-
-[subs="attributes"]
-----
-~]#{nbsp}grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
-----
-
 [[sec-Editing_a_Menu_Entry]]
 === Editing a Menu Entry
 
@@ -304,20 +297,13 @@ Where [option]`console=tty0` is the first virtual terminal and [option]`console=
 
 Changes to `/etc/default/grub` require rebuilding the `grub.cfg` file as follows:
 
-* On BIOS-based machines, issue the following command as `root`:
+* On both UEFI-based and BIOS-based machines, issue the following command as `root`:
 
 [subs="attributes"]
 ----
 ~]#{nbsp}grub2-mkconfig -o /boot/grub2/grub.cfg
 ----
 
-* On UEFI-based machines, issue the following command as `root`:
-
-[subs="attributes"]
-----
-~]#{nbsp}grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
-----
-
 [[sec-Adding_a_new_Entry]]
 === Adding a new Entry
 
@@ -361,9 +347,9 @@ Note that modifying the `/etc/default/grub` file does not have any effect on cre
 
 ====
 
-. On BIOS-based machines, copy the contents of `/boot/grub2/grub.cfg`, or, on UEFI machines, copy the contents of `/boot/efi/EFI/fedora/grub.cfg`. Put the content of the `grub.cfg` into the `/etc/grub.d/40_custom` file below the existing header lines. The executable part of the `40_custom` script has to be preserved.
+. Copy the contents of `/boot/grub2/grub.cfg`. Put the content of the `grub.cfg` into the `/etc/grub.d/40_custom` file below the existing header lines. The executable part of the `40_custom` script has to be preserved.
 
-. From the content put into the `/etc/grub.d/40_custom` file, only the `menuentry` blocks are needed to create the custom menu. The `/boot/grub2/grub.cfg` and `/boot/efi/EFI/fedora/grub.cfg` files might contain function specifications and other content above and below the `menuentry` blocks. If you put these unnecessary lines into the `40_custom` file in the previous step, erase them.
+. From the content put into the `/etc/grub.d/40_custom` file, only the `menuentry` blocks are needed to create the custom menu. The `/boot/grub2/grub.cfg` file might contain function specifications and other content above and below the `menuentry` blocks. If you put these unnecessary lines into the `40_custom` file in the previous step, erase them.
 
 This is an example of a custom `40_custom` script:
 
@@ -421,20 +407,13 @@ Alternatively, if you want to keep the files in the `/etc/grub2.d/` directory, m
 
 . Rebuild the `grub.cfg` file by running the [command]#grub2-mkconfig -o# command as follows:
 
-** On BIOS-based machines, issue the following command as `root`:
+* On both UEFI-based and BIOS-based machines, issue the following command as `root`:
 
 [subs="attributes"]
 ----
 ~]#{nbsp}grub2-mkconfig -o /boot/grub2/grub.cfg
 ----
 
-** On UEFI-based machines, issue the following command as `root`:
-
-[subs="attributes"]
-----
-~]#{nbsp}grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
-----
-
 [[sec-GRUB_2_Password_Protection]]
 == GRUB 2 Password Protection
 
@@ -508,20 +487,13 @@ After you have made changes in the template file the GRUB 2 configuration file m
 
 Rebuild the `grub.cfg` file by running the [command]#grub2-mkconfig -o# command as follows:
 
-* On BIOS-based machines, issue the following command as `root`:
+* On both UEFI-based and BIOS-based machines, issue the following command as `root`:
 
 [subs="attributes"]
 ----
 ~]#{nbsp}grub2-mkconfig -o /boot/grub2/grub.cfg
 ----
 
-* On UEFI-based machines, issue the following command as `root`:
-
-[subs="attributes"]
-----
-~]#{nbsp}grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
-----
-
 [[sec-Password_Encryption]]
 === Password Encryption
 
@@ -602,20 +574,13 @@ This method completely removes all GRUB 2 configuration files and system setting
 
 . Rebuild the `grub.cfg` file by running the [command]#grub2-mkconfig -o# command as follows:
 
-** On BIOS-based machines, issue the following command as `root`:
+* On both UEFI-based and BIOS-based machines, issue the following command as `root`:
 
 [subs="attributes"]
 ----
 ~]#{nbsp}grub2-mkconfig -o /boot/grub2/grub.cfg
 ----
 
-** On UEFI-based machines, issue the following command as `root`:
-
-[subs="attributes"]
-----
-~]#{nbsp}grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
-----
-
 . Now follow the procedure in xref:#sec-Reinstalling_GRUB_2[Reinstalling GRUB 2] to restore GRUB2 on the `/boot/` partition.
 
 [[sec-GRUB_2_over_a_Serial_Console]]
@@ -656,20 +621,13 @@ The first line disables the graphical terminal. Note that specifying the `GRUB_T
 
 Rebuild the `grub.cfg` file by running the [command]#grub2-mkconfig -o# command as follows:
 
-* On BIOS-based machines, issue the following command as `root`:
+* On both UEFI-based and BIOS-based machines, issue the following command as `root`:
 
 [subs="attributes"]
 ----
 ~]#{nbsp}grub2-mkconfig -o /boot/grub2/grub.cfg
 ----
 
-* On UEFI-based machines, issue the following command as `root`:
-
-[subs="attributes"]
-----
-~]#{nbsp}grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
-----
-
 [NOTE]
 ====
 

modules/system-administrators-guide/pages/monitoring-and-automation/System_Monitoring_Tools.adoc

@@ -134,12 +134,15 @@ The `Processes` tab of the [application]*System Monitor* tool allows you to view
 
 To start the [application]*System Monitor* tool, either select menu:Applications[System Tools > `System Monitor`pass:attributes[{blank}]] from the Activities menu, or type [command]#gnome-system-monitor# at a shell prompt. Then click the `Processes` tab to view the list of running processes.
 
-[[fig-sysinfo-processes]]
-.System Monitor — Processes
-
-image::system-monitor-processes.png[The Processes tab of the System Monitor application.]
-
-For each listed process, the [application]*System Monitor* tool displays its name (`Process Name`), current status (`Status`), percentage of the memory usage (`% CPU`), nice value (`Nice`), process ID (`ID`), memory usage (`Memory`), the channel the process is waiting in (`Waiting Channel`), and additional details about the session (`Session`). To sort the information by a specific column in ascending order, click the name of that column. Click the name of the column again to toggle the sort between ascending and descending order.
+For each listed process, the [application]*System Monitor* tool displays its name (`Process Name`),
+user (`User`),
+percentage of the CPU usage (`% CPU`),
+process ID (`ID`),
+memory usage (`Memory`),
+total disk read and write (`Disk read total` and `Disk write total`),
+current disk read and write (`Disk read` and `Disk write`),
+and prioritiy (`Priority`).
+To sort the information by a specific column in ascending order, click the name of that column. Click the name of the column again to toggle the sort between ascending and descending order.
 
 By default, the [application]*System Monitor* tool displays a list of processes that are owned by the current user. Selecting various options from the View menu allows you to:
 

site.yml

@@ -6,7 +6,7 @@ content:
    - url: .
      branches: HEAD
    - url: https://pagure.io/fedora-docs/release-docs-home.git
-     branches: master
+     branches: f36
 ui:
   bundle:
     url: https://asamalik.fedorapeople.org/ui-bundle.zip