From a23ec81a17369bad1cd15ec87fce60773951e45a Mon Sep 17 00:00:00 2001 From: nishaaaaaant Date: Sat, 13 Apr 2024 16:03:56 -0400 Subject: [PATCH 1/2] #1867 fix spacing issue --- docs/books/admin_guide/01-presentation.md | 2 +- docs/books/admin_guide/04-advanced-commands.md | 10 +++++----- docs/books/admin_guide/08-process.md | 10 +++++----- docs/books/admin_guide/09-backups.md | 12 ++++++------ docs/books/admin_guide/10-boot.md | 16 ++++++++-------- docs/books/admin_guide/11-tasks.md | 6 +++--- docs/books/admin_guide/12-network.md | 8 ++++---- docs/books/learning_ansible/01-basic.md | 12 ++++++------ docs/books/learning_ansible/02-advanced.md | 14 +++++++------- .../learning_ansible/03-working-with-files.md | 12 ++++++------ docs/books/learning_ansible/04-ansible-galaxy.md | 8 ++++---- docs/books/learning_ansible/05-deployments.md | 16 ++++++++-------- .../06-large-scale-infrastructure.md | 8 ++++---- .../03-data-entry-and-manipulations.md | 10 +++++----- .../templates-automation-packer-vsphere.md | 4 ++-- 15 files changed, 74 insertions(+), 74 deletions(-) diff --git a/docs/books/admin_guide/01-presentation.md b/docs/books/admin_guide/01-presentation.md index 711cdf7112..2e6c5fcd12 100644 --- a/docs/books/admin_guide/01-presentation.md +++ b/docs/books/admin_guide/01-presentation.md @@ -15,7 +15,7 @@ In this chapter you will learn about GNU/Linux distributions. :heavy_check_mark: Recount the history of UNIX and GNU/Linux. :heavy_check_mark: Choose the right Linux distribution for your needs. :heavy_check_mark: Explain the philosophy of Free and Open-source Software. -:heavy_check_mark: Discover the usefulness of the shell. +:heavy_check_mark: Discover the usefulness of the shell. :checkered_flag: **generalities**, **linux**, **distributions** diff --git a/docs/books/admin_guide/04-advanced-commands.md b/docs/books/admin_guide/04-advanced-commands.md index 10fe4410b9..94c904dada 100644 --- a/docs/books/admin_guide/04-advanced-commands.md +++ b/docs/books/admin_guide/04-advanced-commands.md @@ -10,13 +10,13 @@ Advanced commands provide greater customization and controls in more specialized **Objectives**: In this chapter, future Linux administrators will learn: -:heavy_check_mark: some useful commands not covered in the previous chapter. -:heavy_check_mark: some advanced commands. +:heavy_check_mark: some useful commands not covered in the previous chapter. +:heavy_check_mark: some advanced commands. -:checkered_flag: **user commands**, **Linux** +:checkered_flag: **user commands**, **Linux** -**Knowledge**: :star: -**Complexity**: :star: :star: :star: +**Knowledge**: :star: +**Complexity**: :star: :star: :star: **Reading time**: 20 minutes diff --git a/docs/books/admin_guide/08-process.md b/docs/books/admin_guide/08-process.md index 2a1a73e3e4..789a36805a 100644 --- a/docs/books/admin_guide/08-process.md +++ b/docs/books/admin_guide/08-process.md @@ -10,14 +10,14 @@ In this chapter, you will learn how to work with processes. **Objectives**: In this chapter, future Linux administrators will learn how to: -:heavy_check_mark: Recognize the `PID` and `PPID` of a process; -:heavy_check_mark: View and search for processes; -:heavy_check_mark: Manage processes. +:heavy_check_mark: Recognize the `PID` and `PPID` of a process; +:heavy_check_mark: View and search for processes; +:heavy_check_mark: Manage processes. :checkered_flag: **process**, **linux** -**Knowledge**: :star: :star: -**Complexity**: :star: +**Knowledge**: :star: :star: +**Complexity**: :star: **Reading time**: 20 minutes diff --git a/docs/books/admin_guide/09-backups.md b/docs/books/admin_guide/09-backups.md index 3b1d6602dc..6d017f06ca 100644 --- a/docs/books/admin_guide/09-backups.md +++ b/docs/books/admin_guide/09-backups.md @@ -10,14 +10,14 @@ In this chapter you will learn how to back up and restore your data with Linux. **Objectives**: In this chapter, future Linux administrators will learn how to: -:heavy_check_mark: use the `tar` and `cpio` command to make a backup; -:heavy_check_mark: check their backups and restore data; -:heavy_check_mark: compress or decompress their backups. +:heavy_check_mark: use the `tar` and `cpio` command to make a backup; +:heavy_check_mark: check their backups and restore data; +:heavy_check_mark: compress or decompress their backups. -:checkered_flag: **backup**, **restore**, **compression** +:checkered_flag: **backup**, **restore**, **compression** -**Knowledge**: :star: :star: :star: -**Complexity**: :star: :star: +**Knowledge**: :star: :star: :star: +**Complexity**: :star: :star: **Reading time**: 40 minutes diff --git a/docs/books/admin_guide/10-boot.md b/docs/books/admin_guide/10-boot.md index 27e98c7421..47edc9f083 100644 --- a/docs/books/admin_guide/10-boot.md +++ b/docs/books/admin_guide/10-boot.md @@ -9,16 +9,16 @@ In this chapter, you will learn how the system starts. **** **Objectives**: In this chapter, future Linux administrators will learn: -:heavy_check_mark: The different stages of the booting process; -:heavy_check_mark: How Rocky Linux supports this boot by using GRUB2 and systemd; -:heavy_check_mark: How to protect GRUB2 from an attack; -:heavy_check_mark: How to manage the services; -:heavy_check_mark: How to access logs from `journald`. +:heavy_check_mark: The different stages of the booting process; +:heavy_check_mark: How Rocky Linux supports this boot by using GRUB2 and systemd; +:heavy_check_mark: How to protect GRUB2 from an attack; +:heavy_check_mark: How to manage the services; +:heavy_check_mark: How to access logs from `journald`. -:checkered_flag: **users** +:checkered_flag: **users** . -**Knowledge**: :star: :star: -**Complexity**: :star: :star: :star: +**Knowledge**: :star: :star: +**Complexity**: :star: :star: :star: **Reading time**: 20 minutes **** diff --git a/docs/books/admin_guide/11-tasks.md b/docs/books/admin_guide/11-tasks.md index 38225e4abb..189c930c75 100644 --- a/docs/books/admin_guide/11-tasks.md +++ b/docs/books/admin_guide/11-tasks.md @@ -10,9 +10,9 @@ In this chapter you will learn how to manage scheduled tasks. **Objectives**: In this chapter, future Linux administrators will learn how to: -:heavy_check_mark: Linux deals with the tasks scheduling; -:heavy_check_mark: restrict the use of **`cron`** to certain users; -:heavy_check_mark: schedule tasks. +:heavy_check_mark: Linux deals with the tasks scheduling; +:heavy_check_mark: restrict the use of **`cron`** to certain users; +:heavy_check_mark: schedule tasks. :checkered_flag: **crontab**, **crond**, **scheduling**, **linux** diff --git a/docs/books/admin_guide/12-network.md b/docs/books/admin_guide/12-network.md index 5ebb3d9d41..3a493d8fed 100644 --- a/docs/books/admin_guide/12-network.md +++ b/docs/books/admin_guide/12-network.md @@ -11,10 +11,10 @@ In this chapter you will learn how to work with and manage the network. **Objectives**: In this chapter you will learn how to: :heavy_check_mark: Configure a workstation to use DHCP; -:heavy_check_mark: Configure a workstation to use a static configuration; -:heavy_check_mark: Configure a workstation to use a gateway; -:heavy_check_mark: Configure a workstation to use DNS servers; -:heavy_check_mark: Troubleshoot the network of a workstation. +:heavy_check_mark: Configure a workstation to use a static configuration; +:heavy_check_mark: Configure a workstation to use a gateway; +:heavy_check_mark: Configure a workstation to use DNS servers; +:heavy_check_mark: Troubleshoot the network of a workstation. :checkered_flag: **network**, **linux**, **ip** diff --git a/docs/books/learning_ansible/01-basic.md b/docs/books/learning_ansible/01-basic.md index 67f667ddf8..7779b59d89 100644 --- a/docs/books/learning_ansible/01-basic.md +++ b/docs/books/learning_ansible/01-basic.md @@ -13,14 +13,14 @@ In this chapter you will learn how to work with Ansible. **Objectives**: In this chapter you will learn how to: -:heavy_check_mark: Implement Ansible; -:heavy_check_mark: Apply configuration changes on a server; -:heavy_check_mark: Create first Ansible playbooks; +:heavy_check_mark: Implement Ansible; +:heavy_check_mark: Apply configuration changes on a server; +:heavy_check_mark: Create first Ansible playbooks; -:checkered_flag: **ansible**, **module**, **playbook** +:checkered_flag: **ansible**, **module**, **playbook** . -**Knowledge**: :star: :star: :star: -**Complexity**: :star: :star: +**Knowledge**: :star: :star: :star: +**Complexity**: :star: :star: **Reading time**: 30 minutes diff --git a/docs/books/learning_ansible/02-advanced.md b/docs/books/learning_ansible/02-advanced.md index b93e26d418..03169889f0 100644 --- a/docs/books/learning_ansible/02-advanced.md +++ b/docs/books/learning_ansible/02-advanced.md @@ -10,15 +10,15 @@ In this chapter you will continue to learn how to work with Ansible. **Objectives**: In this chapter you will learn how to: -:heavy_check_mark: work with variables; -:heavy_check_mark: use loops; -:heavy_check_mark: manage state changes and react to them; -:heavy_check_mark: manage asynchronous tasks. +:heavy_check_mark: work with variables; +:heavy_check_mark: use loops; +:heavy_check_mark: manage state changes and react to them; +:heavy_check_mark: manage asynchronous tasks. -:checkered_flag: **ansible**, **module**, **playbook** +:checkered_flag: **ansible**, **module**, **playbook** -**Knowledge**: :star: :star: :star: -**Complexity**: :star: :star: +**Knowledge**: :star: :star: :star: +**Complexity**: :star: :star: **Reading time**: 30 minutes diff --git a/docs/books/learning_ansible/03-working-with-files.md b/docs/books/learning_ansible/03-working-with-files.md index 8bf20f57aa..93a45a981a 100644 --- a/docs/books/learning_ansible/03-working-with-files.md +++ b/docs/books/learning_ansible/03-working-with-files.md @@ -10,14 +10,14 @@ In this chapter you will learn how to manage files with Ansible. **Objectives**: In this chapter you will learn how to: -:heavy_check_mark: modify the content of file; -:heavy_check_mark: upload files to the targeted servers; -:heavy_check_mark: retrieve files from the targeted servers. +:heavy_check_mark: modify the content of file; +:heavy_check_mark: upload files to the targeted servers; +:heavy_check_mark: retrieve files from the targeted servers. -:checkered_flag: **ansible**, **module**, **files** +:checkered_flag: **ansible**, **module**, **files** -**Knowledge**: :star: :star: -**Complexity**: :star: +**Knowledge**: :star: :star: +**Complexity**: :star: **Reading time**: 20 minutes diff --git a/docs/books/learning_ansible/04-ansible-galaxy.md b/docs/books/learning_ansible/04-ansible-galaxy.md index 4764fd805e..2532cb99a5 100644 --- a/docs/books/learning_ansible/04-ansible-galaxy.md +++ b/docs/books/learning_ansible/04-ansible-galaxy.md @@ -10,13 +10,13 @@ In this chapter you will learn how to use, install, and manage Ansible roles and **Objectives**: In this chapter you will learn how to: -:heavy_check_mark: install and manage collections. -:heavy_check_mark: install and manage roles. +:heavy_check_mark: install and manage collections. +:heavy_check_mark: install and manage roles. :checkered_flag: **ansible**, **ansible-galaxy**, **roles**, **collections** -**Knowledge**: :star: :star: -**Complexity**: :star: :star: :star: +**Knowledge**: :star: :star: +**Complexity**: :star: :star: :star: **Reading time**: 40 minutes diff --git a/docs/books/learning_ansible/05-deployments.md b/docs/books/learning_ansible/05-deployments.md index 1da7a15c58..07cc46d314 100644 --- a/docs/books/learning_ansible/05-deployments.md +++ b/docs/books/learning_ansible/05-deployments.md @@ -10,16 +10,16 @@ In this chapter you will learn how to deploy applications with the Ansible role **Objectives**: In this chapter you will learn how to: -:heavy_check_mark: Implement Ansistrano; -:heavy_check_mark: Configure Ansistrano; -:heavy_check_mark: Use shared folders and files between deployed versions; -:heavy_check_mark: Deploying different versions of a site from git; -:heavy_check_mark: React between deployment steps. +:heavy_check_mark: Implement Ansistrano; +:heavy_check_mark: Configure Ansistrano; +:heavy_check_mark: Use shared folders and files between deployed versions; +:heavy_check_mark: Deploying different versions of a site from git; +:heavy_check_mark: React between deployment steps. -:checkered_flag: **ansible**, **ansistrano**, **roles**, **deployments** +:checkered_flag: **ansible**, **ansistrano**, **roles**, **deployments** -**Knowledge**: :star: :star: -**Complexity**: :star: :star: :star: +**Knowledge**: :star: :star: +**Complexity**: :star: :star: :star: **Reading time**: 40 minutes diff --git a/docs/books/learning_ansible/06-large-scale-infrastructure.md b/docs/books/learning_ansible/06-large-scale-infrastructure.md index 16cb1f6a75..9da0f7024a 100644 --- a/docs/books/learning_ansible/06-large-scale-infrastructure.md +++ b/docs/books/learning_ansible/06-large-scale-infrastructure.md @@ -10,13 +10,13 @@ In this chapter you will learn how to scale your configuration management system **Objectives**: In this chapter you will learn how to: -:heavy_check_mark: Organize your code for large infrastructure; -:heavy_check_mark: Apply all or part of your configuration management to a group of nodes; +:heavy_check_mark: Organize your code for large infrastructure; +:heavy_check_mark: Apply all or part of your configuration management to a group of nodes; :checkered_flag: **ansible**, **config management**, **scale** -**Knowledge**: :star: :star: :star: -**Complexity**: :star: :star: :star: :star: +**Knowledge**: :star: :star: :star: +**Complexity**: :star: :star: :star: :star: **Reading time**: 30 minutes diff --git a/docs/books/learning_bash/03-data-entry-and-manipulations.md b/docs/books/learning_bash/03-data-entry-and-manipulations.md index 32b1cfb025..77f00f7f3e 100644 --- a/docs/books/learning_bash/03-data-entry-and-manipulations.md +++ b/docs/books/learning_bash/03-data-entry-and-manipulations.md @@ -17,12 +17,12 @@ In this chapter you will learn how to make your scripts interact with users and **Objectives**: In this chapter you will learn how to: -:heavy_check_mark: read input from a user; -:heavy_check_mark: manipulate data entries; -:heavy_check_mark: use arguments inside a script; -:heavy_check_mark: manage positional variables; +:heavy_check_mark: read input from a user; +:heavy_check_mark: manipulate data entries; +:heavy_check_mark: use arguments inside a script; +:heavy_check_mark: manage positional variables; -:checkered_flag: **linux**, **script**, **bash**, **variable** +:checkered_flag: **linux**, **script**, **bash**, **variable** **Knowledge**: :star: :star: **Complexity**: :star: :star: diff --git a/docs/guides/automation/templates-automation-packer-vsphere.md b/docs/guides/automation/templates-automation-packer-vsphere.md index 9f4e3fe33d..d8f0194cb4 100644 --- a/docs/guides/automation/templates-automation-packer-vsphere.md +++ b/docs/guides/automation/templates-automation-packer-vsphere.md @@ -6,8 +6,8 @@ contributors: Steven Spencer, Ryan Johnson, Pedro Garcia, Ganna Zhyrnova # Automatic template creation with Packer and deployment with Ansible in a VMware vSphere environment -**Knowledge**: :star: :star: :star: -**Complexity**: :star: :star: :star: +**Knowledge**: :star: :star: :star: +**Complexity**: :star: :star: :star: **Reading time**: 30 minutes From 351a2525d8f89e5b065b4ae0b2c63ef7d81c1bd9 Mon Sep 17 00:00:00 2001 From: nishaaaaaant Date: Sat, 13 Apr 2024 16:35:31 -0400 Subject: [PATCH 2/2] #1867 fix markdown violations --- docs/index.md | 4 +- docs/labs/index.md | 2 +- docs/labs/security/index.md | 70 +++++++++++-------- .../labs/security/lab3-auditing_the_system.md | 2 +- docs/labs/security/lab8-iptables.md | 2 +- .../lab8-system_and_process_monitoring-I.md | 12 ++-- .../lab3-bootup_and_startup.md | 6 +- .../lab6-the_file_system.md | 12 ++-- .../lab7-the_linux_kernel.md | 4 +- docs/release_notes/8-changelog.md | 1 - docs/release_notes/8_5.md | 52 +++++++------- docs/release_notes/8_6.md | 12 ++-- docs/release_notes/8_7.md | 6 +- docs/release_notes/8_9.md | 8 +-- docs/release_notes/9_0.md | 15 ++-- docs/release_notes/9_1.md | 2 +- 16 files changed, 105 insertions(+), 105 deletions(-) diff --git a/docs/index.md b/docs/index.md index bced3a0c0a..05b51cbc8a 100644 --- a/docs/index.md +++ b/docs/index.md @@ -4,7 +4,7 @@ title: Home # Rocky Linux Documentation -## Welcome! +## Welcome Welcome to the documentation hub for Rocky Linux; we are glad you're here. We have several contributors adding content, and that content is growing all the time. Here you will find documents on how to build Rocky Linux itself, as well as documents on various subjects that are important to the Rocky Linux community. Who makes up that community you ask? @@ -18,7 +18,7 @@ This home page will give you an introduction to the documentation website and ho Now, you are on the home page of the documentation. If you glance at the top menu (which is always available, including on mobile devices) you can see the main structure showing the top-level sections of the documentation site. If you click on each top menu item (try 'Guides' for example) then on the left side, you will see the list of *sub-sections* for each main section. Guides has many topics of interest. -When you open a document, on the right side you will see a 'Table of contents' with clickable navigation links for that document (for mobile devices try landscape orientation). For long documents, such as the [Release Notes](release_notes/8_8.md), the table of contents allows you to move around the document with ease. If you are reading a long document and want to go back to the top press pg up and you will see a `Back to top` button appear at the top of the screen. +When you open a document, on the right side you will see a 'Table of contents' with clickable navigation links for that document (for mobile devices try landscape orientation). For long documents, such as the [Release Notes](release_notes/8_8.md), the table of contents allows you to move around the document with ease. If you are reading a long document and want to go back to the top press ++page-up++ and you will see a `Back to top` button appear at the top of the screen. The main sections of the documentation site are: diff --git a/docs/labs/index.md b/docs/labs/index.md index 7c1e93e6db..46d2f8330d 100644 --- a/docs/labs/index.md +++ b/docs/labs/index.md @@ -6,4 +6,4 @@ title: Tutorial Labs What are **Labs** and how do they differ from longer-form documentation like **Books**? Well **Labs** are for step by step processes that can further your understanding. They include exercises to test your knowledge. The intention of these labs is to be purely for educational and instructional purposes. They will help you understand particular system administration topics, stimulate experimentation, and encourage collaboration in a safe and simulated lab environment. -Do you have experience in a subject that translates into a lab? That is great! We would love your participation here. Getting involved is just like getting involved with any of Rocky Linux documentation -- head over to the [Mattermost Documentation channel](https://chat.rockylinux.org/rocky-linux/channels/documentation), join the conversation, let us know what you want to write, and we will help you on your way. +Do you have experience in a subject that translates into a lab? That is great! We would love your participation here. Getting involved is just like getting involved with any of Rocky Linux documentation -- head over to the [Mattermost Documentation channel](https://chat.rockylinux.org/rocky-linux/channels/documentation), join the conversation, let us know what you want to write, and we will help you on your way. diff --git a/docs/labs/security/index.md b/docs/labs/security/index.md index 9ee2a8e09a..f8c8e9f823 100644 --- a/docs/labs/security/index.md +++ b/docs/labs/security/index.md @@ -13,58 +13,66 @@ title: List of Security Labs ### Lab 2: Patching the System 1. Updating and Patching -1. Configuring and using dnf -1. Third party solutions +2. Configuring and using dnf +3. Third party solutions ### Lab 3: Auditing the System + 1. A simple home grown integrity checker -1. Tripwire -1. Integrity checking and viewing reports -1. Fine tuning tripwire +2. Tripwire +3. Integrity checking and viewing reports +4. Fine tuning tripwire ### Lab 4: Gathering information + 1. netstat -1. lsof -1. nmap -1. rpcinfo -1. tcpdump -1. telnet +2. lsof +3. nmap +4. rpcinfo +5. tcpdump +6. telnet ### Lab 5: Local Security + 1. Cracking the system through the boot loader -1. Password protecting the boot loader -1. Disabling un-necessary tty’s -1. Disabling reboot via CTRL+ALT+DEL -1. Enforcing password prompting in single user-mode -1. Set-UID programs -1. John the ripper +2. Password protecting the boot loader +3. Disabling un-necessary tty’s +4. Disabling reboot via CTRL+ALT+DEL +5. Enforcing password prompting in single user-mode +6. Set-UID programs +7. John the ripper ### Lab 6: A staged Hack + 1. The PATH ### Lab 7: TCP wrappers + 1. Tcp_wrappers ### Lab 8: Iptables + 1. Iptables essentials -1. Basic Packet Filtering -1. Basic Packet Forwarding +2. Basic Packet Filtering +3. Basic Packet Forwarding ### Lab 9: Cryptography + 1. GnuPG -1. Key Administration -1. Revocation certificates -1. Digital signatures -1. Encrypting and decrypting files -1. sshd -1. ssh -1. scp -1. Authenticating via Public-Key -1. ssh-agent +2. Key Administration +3. Revocation certificates +4. Digital signatures +5. Encrypting and decrypting files +6. sshd +7. ssh +8. scp +9. Authenticating via Public-Key +10. ssh-agent ### Lab 10: Kernel Level Security + 1. Installing GRsecurity -1. gradm -1. ACLs -1. GRsecurity Learning mode -1. SElinux +2. gradm +3. ACLs +4. GRsecurity Learning mode +5. SElinux diff --git a/docs/labs/security/lab3-auditing_the_system.md b/docs/labs/security/lab3-auditing_the_system.md index 426be27979..2460f18d85 100644 --- a/docs/labs/security/lab3-auditing_the_system.md +++ b/docs/labs/security/lab3-auditing_the_system.md @@ -492,7 +492,7 @@ Initializing the database is the Tripwire terminology for, taking an initial “ ## Exercise 3 -**Integrity checking and viewing reports** +### Integrity checking and viewing reports In this exercise you will learn how to run an integrity check of the system and view the reports that Tripwire generates for you. diff --git a/docs/labs/security/lab8-iptables.md b/docs/labs/security/lab8-iptables.md index 9d9553e853..84c6d22a0b 100644 --- a/docs/labs/security/lab8-iptables.md +++ b/docs/labs/security/lab8-iptables.md @@ -54,7 +54,7 @@ Out of the box, three independent tables are defined in most Linux Kernels. The ### CHAINS -A chain is a list of rules which can match a set of packets. Each rule specifies what to do with a packet that matches. Each table contains a number of built-in chains and may also contain user-defined chains. +A chain is a list of rules which can match a set of packets. Each rule specifies what to do with a packet that matches. Each table contains a number of built-in chains and may also contain user-defined chains. ### TARGETS diff --git a/docs/labs/systems_administration_I/lab8-system_and_process_monitoring-I.md b/docs/labs/systems_administration_I/lab8-system_and_process_monitoring-I.md index 5979716e2d..0e456d0c73 100644 --- a/docs/labs/systems_administration_I/lab8-system_and_process_monitoring-I.md +++ b/docs/labs/systems_administration_I/lab8-system_and_process_monitoring-I.md @@ -436,7 +436,7 @@ The following steps show how to use `ps` to display basic process information. (process ID) old priority 0, new priority -10 ``` - Replace "" (above) with the actual PID of the running process. + Replace `` (above) with the actual PID of the running process. 4. Monitor the resource utilization for the `find/md5sum` process, using `top` (or `htop`). Type: @@ -460,7 +460,7 @@ The following steps show how to use `ps` to display basic process information. 2338530 (process ID) old priority -10, new priority 10 ``` - Replace the "" (above) with the actual PID of the running process. + Replace the `` (above) with the actual PID of the running process. !!! question @@ -682,7 +682,7 @@ This exercise covers managing processes with `fg` and `bg` ps -p ``` - Replace with the actual process ID obtained from step 2. + Replace `` with the actual process ID obtained from step 2. !!! question @@ -872,7 +872,7 @@ Like `kill`, `killall` is a command to terminate processes by name instead of PI echo | sudo tee /sys/fs/cgroup/cpu/mygroup/cgroup.procs ``` - Replace with the actual PID of the process. + Replace `` with the actual PID of the process. 4. Check if the process has been moved to the "mygroup" `cgroup`. @@ -892,7 +892,7 @@ Like `kill`, `killall` is a command to terminate processes by name instead of PI ### Managing processes with `renice` -#### To adjust the priority of a running process using `renice` +#### To adjust the priority of a running processes using `renice` 1. Identify a running process with a specific PID and priority using `ps`. @@ -910,7 +910,7 @@ Like `kill`, `killall` is a command to terminate processes by name instead of PI renice -p ``` - Replace with the new priority value you want to set, and with the actual PID of the process. + Replace `` with the new priority value you want to set, and `` with the actual PID of the process. 3. Verify that the process' priority has changed using `ps`. diff --git a/docs/labs/systems_administration_II/lab3-bootup_and_startup.md b/docs/labs/systems_administration_II/lab3-bootup_and_startup.md index c4187450c1..806967c684 100644 --- a/docs/labs/systems_administration_II/lab3-bootup_and_startup.md +++ b/docs/labs/systems_administration_II/lab3-bootup_and_startup.md @@ -25,7 +25,7 @@ Estimated time to complete this lab: 50 minutes ## Boot process overview -The exercises in this lab will begin from the booting-up process down to the logging in of the user. These steps will examine and try to customize parts of the boot-up processes. The high-level steps in the boot process are: +The exercises in this lab will begin from the booting-up process down to the logging in of the user. These steps will examine and try to customize parts of the boot-up processes. The high-level steps in the boot process are: ### Summary of steps @@ -234,7 +234,7 @@ Once the first process runs, it then goes on to start other services, daemons, p ...... ``` -9. Use `ls` and `file` commands to learn more about the relationship of the traditional `init` program to the `systemd` program. Type: +9. Use `ls` and `file` commands to learn more about the relationship of the traditional `init` program to the `systemd` program. Type: ```bash [root@localhost ~]# ls -l /usr/sbin/init && file /usr/sbin/init @@ -389,7 +389,7 @@ The exercises in this section will show you how to configure system/user process [root@localhost ~]# pgrep -a crond ``` - If `pgrep` finds a matching process name, it will list the PID of `crond`. + If `pgrep` finds a matching process name, it will list the PID of `crond`. 2. Use `systemctl` to start the `crond.service` unit. Type: diff --git a/docs/labs/systems_administration_II/lab6-the_file_system.md b/docs/labs/systems_administration_II/lab6-the_file_system.md index 58590dd763..4bcde0a639 100644 --- a/docs/labs/systems_administration_II/lab6-the_file_system.md +++ b/docs/labs/systems_administration_II/lab6-the_file_system.md @@ -645,7 +645,7 @@ You'll add the `/dev/loop1` physical volume (PV) that was prepped and created ab Volume group "rl" successfully extended ``` -3. Run the `vgdisplay` command again to view your changes. Type: +3. Run the `vgdisplay` command again to view your changes. Type: ```bash [root@localhost ~]# vgdisplay @@ -934,7 +934,7 @@ The previous exercises walked through preparing a block/storage device for use o This exercise will cover how to `mount` and `umount` the file systems that we created in the previous exercise. -### `mount` +### `mount` command The `mount` command is used for attaching the filesystem created on a device to the file hierarchy. @@ -1056,7 +1056,7 @@ The `mount` command is used for attaching the filesystem created on a device to 4. With real disk or storage devices, the previous steps will be enough to make the system automatically and correctly mount all the new file systems and apply any special mount options. - BUT, because we've been using special pseudo-block devices (loop devices) in this lab, we must complete an additional important task to ensure that the correct loop devices are automatically recreated after the system reboots. + BUT, because we've been using special pseudo-block devices (loop devices) in this lab, we must complete an additional important task to ensure that the correct loop devices are automatically recreated after the system reboots. To do this we'll create a custom systemd service unit to help with this. @@ -1160,15 +1160,15 @@ Implementing and enforcing the use of disk quotas provides a way to ensure that - Decide what your soft and hard limits will be. - Decide what the grace periods will be (i.e. if there will be any at all). -*Hard Limit* +#### *Hard Limit* The hard limit defines the absolute maximum amount of disk space that a user or group can use. Once this limit is reached, no further disk space can be used. -*Soft Limit* +#### *Soft Limit* The soft limit defines the maximum amount of disk space that can be used. However, unlike the hard limit, the soft limit can be exceeded for a certain amount of time. That time is known as the grace period. -*Grace Period* +#### *Grace Period* The grace period is the time during which the soft limit may be exceeded. The grace period can be expressed in seconds, minutes, hours, days, weeks, or months, thus giving the system administrator a great deal of freedom in determining how much time to give users to get their disk usage below their soft limit. diff --git a/docs/labs/systems_administration_II/lab7-the_linux_kernel.md b/docs/labs/systems_administration_II/lab7-the_linux_kernel.md index 43887ba8aa..ad3662389e 100644 --- a/docs/labs/systems_administration_II/lab7-the_linux_kernel.md +++ b/docs/labs/systems_administration_II/lab7-the_linux_kernel.md @@ -71,7 +71,7 @@ The choice of when to make a particular feature available as a module or to comp There are generally three methods by which the kernel can be managed on Linux distributions. These are: -1. Using the prepackaged version of the kernel from the distributions vendor. e.g. using kernel-.*.rpm. This is the safest, easiest and most preferred recommended. +1. Using the prepackaged version of the kernel from the distributions vendor. e.g. using kernel-``.*.rpm. This is the safest, easiest and most preferred recommended. 2. Via patching. Using patch files like - patch-kernel.version.gz. @@ -395,7 +395,7 @@ In this exercise you will build a new kernel from source, by configuring, compil /boot/vmlinuz- ``` - Replace with the version number of your custom kernel. + Replace `` with the version number of your custom kernel. For the sample kernel we are using in this guide, the filename would be vmlinuz-6.*-custom. So here’s the exact command for this example: ```bash diff --git a/docs/release_notes/8-changelog.md b/docs/release_notes/8-changelog.md index 59be6e2084..4e750e6aa9 100644 --- a/docs/release_notes/8-changelog.md +++ b/docs/release_notes/8-changelog.md @@ -14,4 +14,3 @@ Changelog data for Rocky Linux versions is currently a work in progress. This do Updates released since upstream are posted across our current architectures. We strongly recommend that all users apply *all* updates, including the content released today, on your existing Rocky Linux machines. This can be done by running `dnf upgrade`. All Rocky Linux components are built from the sources hosted at [git.rockylinux.org](https://git.rockylinux.org). In addition, SRPMs are being published alongside the repositories in a corresponding "source" directory. You can find these on any of our mirrors. These source packages match every binary RPM we release. - diff --git a/docs/release_notes/8_5.md b/docs/release_notes/8_5.md index 555a06c650..355fc4e055 100644 --- a/docs/release_notes/8_5.md +++ b/docs/release_notes/8_5.md @@ -4,15 +4,14 @@ title: Release 8.5 # Release Notes for Rocky Linux 8.5 -### Thank You +## Thank You Thank you for supporting Rocky Linux. These are the release notes for Rocky Linux 8.5, available for x86_64 and aarch64 (ARM) architectures. ->There was an amazing amount of work and collaboration that went into this release. The Rocky Release Engineering team went far and above the call of duty to make 8.5 a reality so quickly. Please send them gratitude, happy thoughts, and lotsa beers at our first available moment! +>There was an amazing amount of work and collaboration that went into this release. The Rocky Release Engineering team went far and above the call of duty to make 8.5 a reality so quickly. Please send them gratitude, happy thoughts, and lotsa beers at our first available moment! — Gregory Kurtzer - ### Major Changes For a full listing of all changes which occurred upstream, please reference the [Release Notes for Red Hat Enterprise Linux 8.5](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.5_release_notes/overview#overview-major-changes). @@ -25,14 +24,12 @@ There were some things that we had to get in order and resolved, but it is with As with any security related diligence, it is important to be able to validate the Secure Boot shim is exactly what you expect and that it is properly activated. After installing Rocky Linux 8.5, please log in and run these commands to validate our secure boot shim: -``` - -$ sudo dnf install -y keyutils - -$ sudo keyctl show %:.platform +```bash +sudo dnf install -y keyutils -$ sudo mokutil --sb +sudo keyctl show %:.platform +sudo mokutil --sb ``` These commands should produce output similar to the following: @@ -59,28 +56,28 @@ SecureBoot enabled #### New Modules - * Ruby 3.0 - * nginx 1.20 - * Node.js 16 +* Ruby 3.0 +* nginx 1.20 +* Node.js 16 #### Updated Components - * PHP to version 7.4.19 - * Squid to version 4.15 - * Mutt to version 2.0.7 +* PHP to version 7.4.19 +* Squid to version 4.15 +* Mutt to version 2.0.7 #### Compilers and Development tools - * GCC Toolset 11 - * LLVM Toolset 12.0.1 - * Rust Toolset 1.54.0 - * Go Toolset 1.16.7 +* GCC Toolset 11 +* LLVM Toolset 12.0.1 +* Rust Toolset 1.54.0 +* Go Toolset 1.16.7 #### OpenJDK updates - * Open Java Development Kit 17 (OpenJDK 17) is now available. For more information about the features introduced in this release and changes in the existing functionality, see OpenJDK features. - * OpenJDK 11 has been updated to version 11.0.13. For more information about the features introduced in this release and changes in the existing functionality, see Release notes for OpenJDK 11.0.13. - * OpenJDK 8 has been updated to version 8.0.312. For more information about the features introduced in this release and changes in the existing functionality, see Release notes for OpenJDK 8.0.312. +* Open Java Development Kit 17 (OpenJDK 17) is now available. For more information about the features introduced in this release and changes in the existing functionality, see OpenJDK features. +* OpenJDK 11 has been updated to version 11.0.13. For more information about the features introduced in this release and changes in the existing functionality, see Release notes for OpenJDK 11.0.13. +* OpenJDK 8 has been updated to version 8.0.312. For more information about the features introduced in this release and changes in the existing functionality, see Release notes for OpenJDK 8.0.312. #### Fastest Mirrors @@ -92,9 +89,9 @@ This change means that a Repository URL is no longer required when using Boot-on #### Packages Added - * In the plus repository, thunderbird with PGP support was added - * In the plus repository, openldap-servers was added - * In the rockypi repository, rasperrypi2 kernel was added for raspberry specific aarch64 support +* In the plus repository, thunderbird with PGP support was added +* In the plus repository, openldap-servers was added +* In the rockypi repository, rasperrypi2 kernel was added for raspberry specific aarch64 support For a complete comparison of packages and their versions between Rocky Linux and Red Hat Enterprise Linux, please consult our [RepoCompare](https://repocompare.rockylinux.org) site. @@ -112,8 +109,8 @@ Migrations to Rocky Linux 8.5 are supported from various Enterprise Linux distri To update your installation of Rocky Linux 8.4 Stable to 8.5, type: -``` -$ sudo dnf -y upgrade +```bash +sudo dnf -y upgrade ``` ### Known Issues @@ -123,4 +120,3 @@ Please see [Chapter 5 - Bug Fixes](https://access.redhat.com/documentation/en-us #### Reporting Bugs Please report any bugs you encounter to the Rocky Linux Bug Tracker. We also welcome you to join our community in any way you wish be it on our [Forums](https://forums.rockylinux.org), [Mattermost](https://chat.rockylinux.org), [IRC on Libera.Chat](irc://irc.liberachat/rockylinux), [Reddit](https://reddit.com/r/rockylinux), [Mailing Lists](https://lists.resf.org), or any other way you wish to participate! - diff --git a/docs/release_notes/8_6.md b/docs/release_notes/8_6.md index 50772e8c7a..16fe6a7d0f 100644 --- a/docs/release_notes/8_6.md +++ b/docs/release_notes/8_6.md @@ -8,7 +8,7 @@ tags: # Release Notes For Rocky Linux 8.6 -## Major Changes +## Major Changes For a complete list of major changes, please see the upstream listing [here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.6_release_notes/overview#overview-major-changes). @@ -16,11 +16,11 @@ Below are some highlights. ### Security - * `fapolicyd`: updated to version 1.1. Includes the ability to use `/rules.d` and `/trust.d` directories, the ability to use `fagenrules` script, and new options for the `fapolicyd-cli`command. - * OpenSSH server now supports drop-in configurations. This means you can use the `Include` directive in `sshd_config` similar to what is now available for `ssh_config`. - * `pcsc-lite` package: rebased to upstream version 1.9.5 with new enhancements and bug fixes. - * SELinux: You can now verify versions of installed policy modules by using the `--checksum` option with the `semodule` command. - * SCAP Security Guide (SSG) packages: rebased to version 0.1.60, and OpenSCAP packages have been rebased to version 1.3.6. +* `fapolicyd`: updated to version 1.1. Includes the ability to use `/rules.d` and `/trust.d` directories, the ability to use `fagenrules` script, and new options for the `fapolicyd-cli`command. +* OpenSSH server now supports drop-in configurations. This means you can use the `Include` directive in `sshd_config` similar to what is now available for `ssh_config`. +* `pcsc-lite` package: rebased to upstream version 1.9.5 with new enhancements and bug fixes. +* SELinux: You can now verify versions of installed policy modules by using the `--checksum` option with the `semodule` command. +* SCAP Security Guide (SSG) packages: rebased to version 0.1.60, and OpenSCAP packages have been rebased to version 1.3.6. ### Web and Programming diff --git a/docs/release_notes/8_7.md b/docs/release_notes/8_7.md index 688b90a347..abf43746fc 100644 --- a/docs/release_notes/8_7.md +++ b/docs/release_notes/8_7.md @@ -105,11 +105,11 @@ For more on these changes, visit the [upstream page](https://access.redhat.com/d * GCC 12 and later supports `_FORTIFY_SOURCE` level 3 * GDB rebased to version 11.2 -#### Module Streams +#### Module-Streams * New module stream `maven:3.8` -#### Additional Changes +#### Additional-Changes * DNS stub resolver option now supports `no-aaaa` option * Rust Toolset rebased to version 1.62.1 @@ -132,5 +132,3 @@ For more on these changes, visit the [upstream page](https://access.redhat.com/d ## Reporting Bugs Please report any bugs you encounter to the [Rocky Linux Bug Tracker](https://bugs.rockylinux.org/). We also welcome you to join our community in any way you wish be it on our [Forums](https://forums.rockylinux.org), [Mattermost](https://chat.rockylinux.org), [IRC on Libera.Chat](irc://irc.liberachat/rockylinux), [Reddit](https://reddit.com/r/rockylinux), [Mailing Lists](https://lists.resf.org), or any other way you wish to participate! - - diff --git a/docs/release_notes/8_9.md b/docs/release_notes/8_9.md index 8c999f0a6f..dbf0cc423b 100644 --- a/docs/release_notes/8_9.md +++ b/docs/release_notes/8_9.md @@ -28,7 +28,7 @@ To install Rocky Linux 8.9, head to the [download page](https://rockylinux.org/d ### Breaking changes -* The optional `guest-agents` group, previously available within both the *Minimal Install* and *Custom Operating System* base environments in anaconda, is no longer available for selection as additional software for those environments. If you require the `guest-agents` group, it is available in either the *Server* or *Server with GUI* base environments. If you install *Minimal Install* or *Custom Operating System* and still want guest-agents, you can do so by installing the package target directly in Kickstart, or by installing it with DNF after installation has completed (i.e., dnf install @guest-agents). +* The optional `guest-agents` group, previously available within both the *Minimal Install* and *Custom Operating System* base environments in anaconda, is no longer available for selection as additional software for those environments. If you require the `guest-agents` group, it is available in either the *Server* or *Server with GUI* base environments. If you install *Minimal Install* or *Custom Operating System* and still want guest-agents, you can do so by installing the package target directly in Kickstart, or by installing it with DNF after installation has completed (i.e., dnf install @guest-agents). #### Live Images @@ -50,13 +50,13 @@ Listed below are security-related highlights in the latest Rocky Linux 8.9 relea * OpenSCAP rebased to version 1.3.8. * ANSSI-BP-028 SCAP security profiles updated to version 2.0. -* SCAP Security Guide now contains improved rules to provide more consistent interactive user configuration and the DISA STIG profile supports `audit_rules_login_events_faillock`. +* SCAP Security Guide now contains improved rules to provide more consistent interactive user configuration and the DISA STIG profile supports `audit_rules_login_events_faillock`. ### Dynamic programming languages, web and database servers For a detailed list of the changes in this category see the [upstream link here](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.9_release_notes/new-features#new-features-dynamic-programming-languages-web-and-database-servers). -* Node.js 20 is now available as a new module stream. +* Node.js 20 is now available as a new module stream. ### Compilers and development tools @@ -66,7 +66,7 @@ For details on the changes in this category see the [upstream link here](https:/ * Valgrind 3.21 * SystemTap 4.9 -* elfutils 0.189 +* elfutils 0.189 #### Updated performance monitoring tools diff --git a/docs/release_notes/9_0.md b/docs/release_notes/9_0.md index f148705908..74852e50be 100644 --- a/docs/release_notes/9_0.md +++ b/docs/release_notes/9_0.md @@ -53,7 +53,6 @@ The main networking related changes are listed below. For detailed coverage of t Several dynamic programming, version control and web related application suites listed next have been updated to newer versions in Rocky Linux 9.0. For a complete list of changes and descriptions, please see [this upstream link](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.0_release_notes/New-features#enhancement_dynamic-programming-languages-web-and-database-servers). - #### Dynamic Programming * **Node.js 16** @@ -143,26 +142,26 @@ The Rocky Linux team does not recommend upgrades from one major version to the n ## Installing -To install Rocky Linux 9.0, head to the [download page](https://rockylinux.org/download/) and download the version you need for your architecture. +To install Rocky Linux 9.0, head to the [download page](https://rockylinux.org/download/) and download the version you need for your architecture. A complete installation walk-through for Rocky Linux 9.0 is available on the [Rocky Linux documentation website here](https://docs.rockylinux.org/guides/installation/). While this is covered in the installation walk-through (above), it is important that you verify your download against the CHECKSUM for that file to make sure there is no corruption or tampering. You can do this with the following steps assuming that you've downloaded the file on another machine using Linux: - * In the directory where you've downloaded the ISO image for your target architecture, download the CHECKSUM file as well. Example: +* In the directory where you've downloaded the ISO image for your target architecture, download the CHECKSUM file as well. Example: - ``` + ```bash curl https://download.rockylinux.org/pub/rocky/9/isos/x86_64/CHECKSUM -o CHECKSUM ``` - * Then issue the command: +* Then issue the command: - ``` + ```bash sha256sum -c CHECKSUM --ignore-missing ``` - * If you get back the following on the command line, your file has been verified. Note we are assuming the minimal ISO below, but it may be the DVD ISO as well: +* If you get back the following on the command line, your file has been verified. Note we are assuming the minimal ISO below, but it may be the DVD ISO as well: - ``` + ```bash Rocky-9.0-x86_64-minimal.iso: OK ``` diff --git a/docs/release_notes/9_1.md b/docs/release_notes/9_1.md index 4d0b9de5a9..970441b21d 100644 --- a/docs/release_notes/9_1.md +++ b/docs/release_notes/9_1.md @@ -32,7 +32,7 @@ More information on the artifacts produced by the Cloud Special Interest Group, Prior to installing, [ensure your CPU is compatible with this procedure!](https://docs.rockylinux.org/gemstones/test_cpu_compat/) -To install Rocky Linux 9.1, head to the [download page](https://rockylinux.org/download/) and download the version you need for your architecture. +To install Rocky Linux 9.1, head to the [download page](https://rockylinux.org/download/) and download the version you need for your architecture. ## Known Issues