Please fill in the following information:

Issue description

Description: Learning materials updates and issues
Hi, I'm taking RH199 (9.3) in Chapter 4, guided exercise: Manage File System Permissions from the Command Line, using RHEL 9.3 the umask on the tutorial video is 0002 whereas the OS umask is 0022.  This creates a permissions discrepancy when following the video.  Step 6.2 creates an empty file with 'touch consultants1.txt' whereas step 9 says user consultants2 (:consultants) should be able to write content.  This is not possible when the umask of 0022 removed the write bit from group.  Umasks and the tech note about changing the umask in future RHEL 9+ aren't covered until the next section.  Also, in Chapter 5 running 'systemctl enable --now httpd' failed with 'AH5043 https; bad user name apache'.  I verified 'dnf install httpd' had been run but there was no apache user or group.  Fixed with the following command: 'useradd -c “Apache” -u 48 -g 48 -d /usr/share/httpd -s /sbin/nologin apache' but I'm not sure why this was necessary.

User further added:

 The point of Step 9 is stated at
https://rol.redhat.com/rol/app/courses/rh199-9.3/pages/ch04s02 Timestamp
4:15 when Ricardo says "our text has been added there, indicating of course
that the consultant2 user has the write permission to consultant1.txt".

The user consultant2 should be able to write to the file that was created
by user consultant1 because the permissions of the file have been changed
to owning group consultants at Timestamp 3:12. The write permission for
group on consultant1.txt is not a mistake in the video. The mistake is
that the touch command does not add that permission by default (which it
would if the umask was still 0002).

The steps you are referring to look like they've been added (incorrectly)
to address this issue but do not fix the problem or meet the learning
objectives of the exercise. Creating the consultant2.txt file isn't
required or part of the video because the consultant1 user would not be
able to create consultant1.txt if the folder permissions in step 4.2 were
incorrect (the folder is created by root and chown :consultants at
Timestamp 1:21).

Assuming the umask command should not be used at this stage because it has
not been addressed, the steps to fix the permissions in the guide should be:
Step 9.1 change to the /home/consultants directory
Step 9.2 ensure the owning group consultants has write permissions
(required for RHEL 9.1 or later): sudo chmod g+w consultant1.txt
Step 9.3 Ensure that the consultant2 can add content to the consultant1.txt
file (the video uses $ echo "text" >> consultant1.txt)

Additionally, the following steps in the guide are not required to meet the
stated learning objectives:

9.1 Change to the /home/consultants directory. Create an empty file called
consultant2.txt.

[consultant2@servera ~]$ cd /home/consultants/
[consultant2@servera consultants]$ touch consultant2.txt

10 (this is listed as .0 on the webpage, see attached image). List the
contents of the /home/consultants directory.

[consultant2@servera consultants]$ ls
consultant1.txt consultant2.txt 

Request Number – RHT2216474