答案：

Solution:
[root@node1 ~]# mkdir /home/managers
[root@node1 ~]# chgrp sysmgrs /home/managers
[root@node1 ~]# chmod 2770 /home/managers
# Verification
[root@node1 ~]# ll -d /home/managers

答案：

See the solution below in Explanation.
Explanation:
Solution:
* Partition the disk:
fdisk /dev/sdb
Inside fdisk:
* n = new partition
* p = primary
* 1 = partition number
* accept defaults
* size +700M
* t = change type
* set Linux LVM type
* w = write changes
* Create the physical volume:
pvcreate /dev/sdb1
* Create the volume group:
vgcreate vg_data /dev/sdb1
* Create the logical volume:
lvcreate -L 500M -n lv_data vg_data
* Create the filesystem:
mkfs.xfs /dev/vg_data/lv_data
Detailed Explanation:
* The lab specifies a 700 MB partition and a 500 MB logical volume.
* pvcreate initializes the partition for LVM.
* vgcreate builds the storage pool.
* lvcreate allocates space from the volume group.
* mkfs.xfs creates the filesystem, which is standard on RHEL.

答案：

Solution:
# Note: Perform the following operations by SSHing into localhost as the user "wallah"
[root@node1 ~]# ssh wallah@localhost
# Prepare the relevant mapping directories
[wallah@node1 ~]$ sudo mkdir /opt/{file,progress}
[wallah@node1 ~]$ sudo chown wallah:wallah /opt/{file,progress}
# Start the container and map directories
# :Z changes the SELinux security context of the directory to allow container access.
[wallah@node1 ~]$ podman run -d --name ascii2pdf -v /opt/file:/dir1:Z -v /opt/progress:/dir2:Z pdf
[wallah@node1 ~]$ podman ps -a
# Create systemd service file
[wallah@node1 ~]$ mkdir -p ~/.config/systemd/user
[wallah@node1 ~]$ cd ~/.config/systemd/user/
[wallah@node1 ~]$ podman generate systemd -n ascii2pdf -f --new
[wallah@node1 user]$ ll
total 4
-rw-r--r--. 1 wallah wallah 770 Dec 13 01:07 container-ascii2pdf.service
# Stop and remove the existing ascii2pdf container
[wallah@node1 ~]$ podman stop ascii2pdf
[wallah@node1 ~]$ podman rm ascii2pdf
[wallah@node1 ~]$ podman ps -a
# Enable and start the container-ascii2pdf service
[wallah@node1 ~]$ systemctl --user daemon-reload
[wallah@node1 ~]$ systemctl --user enable --now container-ascii2pdf
# Check container status
[wallah@node1 ~]$ systemctl --user status container-ascii2pdf
[wallah@node1 ~]$ podman ps
# On node1, switch to the root user to perform the following operations
# Ensure that the services for the wallah user start automatically at system boot
[root@node1 ~]# loginctl enable-linger
[root@node1 ~]# loginctl show-user wallah
# Check to ensure the container starts on boot (mandatory operation)
[root@node1 ~]# reboot
[root@node1 ~]# ssh wallah@node1
[wallah@node1 ~]# podman ps

答案：

See the solution below in Explanation.
Explanation:
Solution:
Create the Quadlet file:
mkdir -p /etc/containers/systemd
cat > /etc/containers/systemd/sleepy.container < < 'EOF'
[Container]
Image=registry.access.redhat.com/ubi10/ubi
ContainerName=sleepy
Exec=sleep 3600
[Install]
WantedBy=multi-user.target
EOF
Reload and enable:
systemctl daemon-reload
systemctl enable --now sleepy.service
systemctl status sleepy.service
Detailed Explanation:
* Quadlet is the preferred modern way to manage Podman containers with systemd for new configurations.
* The .container file is translated into a systemd-managed service.
* RHEL 10 documentation notes that podman generate systemd still exists, but Quadlets are preferred for new setups. ( Red Hat Documentation )

答案：

Solution:
# su - natasha
Write the umask setting into the user's .bashrc file in the home directory:
bash
Copy code
echo 'umask 222' >> .bashrc
source .bashrc
Command explanation:
umask is used to control the default permissions for files and directories created by a user.
In umask:
The first digit is for special permissions and is usually 0 (can be omitted if not needed).
The second digit controls owner permissions.
The third digit controls group permissions.
The fourth digit controls permissions for others.