Так уж получилось, что я себя вдруг почувствовал почти готовым к RHCSA. Но вот незадача, у меня есть ещё два с половиной месяца минимум до сдачи...
И тут ко мне в голову пришла хорошая идея - начать готовиться к следующему экзамену (пока не RHEL).
И тут ко мне в голову пришла хорошая идея - начать готовиться к следующему экзамену (пока не RHEL).
Такого я ещё не делал. Я привык концентрироваться на одном экзамене до его сдачи, но два месяца тратить впустую не хочется. Известно, что RHCSA экзамен сугубо практический, а это значит, что нужно поддерживать должный уровень наработанных навыков для успешной сдачи. Тут мы и подходим к главной идее. Я начну подготовку к следующему экзамену паралленьно нарабатывая навык для сдачи CSA. Это позволит мне познавать новый материал и одновременно держать необходимый уровень знаний и умений для сдачи.
Я снова попытался не выдумывать велосипед, но снова ничего не получилось. Ну не могу я просто следовать книжным лабораторкам. Они мне кажутся одновременно неполными и скучным. Поэтому я решил сделать "циклическую" (потом запатентую) лабу, которая включает в себя все (или почти все) необходимые для выполнения упражнения. В конце каждой лабы я планирую менять kickstart файл и начинать лабу сначала, устанавливая машину с него.
Ниже тот самый план, по которому планирую идти. Обкатано - работает.
- 
Install the new VM.
- 
Reset the root password.
- 
Change the hostname to exsz.rhcsalab.hi.
- 
Modify the shell prompt. Add the [vm] keyword.
- 
Configure a local repo.
- 
Set up a funny banner message.
- 
Create an at job to reboot the server at specific time.
- 
Disable the user to use at
- 
Create a cronjob to periodically archive home directory for non-root user
- 
Create a cronjob as root to perform an update of the server, send both standard and error outputs to /var/log/cronupdate.log file. Generate a standard log message as well.
- 
Create a cronjob without bounding to particular user to reboot the server
- 
Install some packages (vim, bash-completion), verify the history and undo the specific installation.
- 
Query the installed at package to- 
find the documentation
- 
the configuration files
- 
check dependencies
- 
check what have been changed since installation
 
- 
- 
Query the uninstalled nmap files
- 
Set up the correct timezone and NTP service
- 
Change the default SSH port and configure the Key based authentication.
- 
Change the GRUB to see all messaged during boot.
- 
Create a star archive of /etc directory with name initial.tgz.
- 
List all files in archive
- 
Extract at.deny to /tmp directory
- 
Make the initial.tgz unremovable.
- 
Add additional disks to vm (3x1GB)
- 
Create the following storage structure:- 
vdb (GPT)- 
vdb1 - 500Mb - SWAP
- 
vdb2 - 500MB - EXT4
 
- 
- 
vdc (MBR) - LVM- 
VG-TEST- 
LV-SWAP (40%)
- 
LV-EXT4-1 (30%)
- 
LV-EXT4-2 (30%)
 
- 
 
- 
 
- 
- 
Extend swap space with vdb1, LV-SWAP.
- 
Mount swap via fstab
- 
Create a file system (ext4) for vdb2, VG-TEST/LV-EXT4-1 and VG-TEST/LV-EXT4-2
- 
Set label ACCOUNT_DISK for vdb2
- 
Set default mount options for /dev/vdb2 (acl and extended attributes)
- 
Mount devices through fstab with all required parameters- 
vdb2 - /data/local/account
- 
VG-TEST/LV-EXT4-1 - /data/local/sales
- 
VG-TEST/LV-EXT4-2 - /data/local/common
 
- 
- 
Verify and mount network shares (NFS, CIFS) to /data/remote/$SHARE_NAME
- 
Mount network shares through fstab with all required parameters
- 
Find all files with SUID set
- 
Change the default user parameters as follows- 
Disable the creation of mail spool
- 
Add a welcoming file to user home directory by default
- 
Maximum number of days a password may be used should be set to 7
- 
Minimum acceptable password length should be set to 3
- 
Number of days warning given before a password expires should be set to 3
 
- 
- 
Create a shared group environment (locally)- 
Create two groups by two users- 
sales - bob, betty
- 
account - bill, beatrix
 
- 
- 
Verify changes in configuration files
- 
Make the account group owner of /data/local/account directory, and make the /data/local/sales owner of sales directory
- 
Bob should be a /data/local/sales owner
- 
Bill should be a /data/local/account owner
- 
Set the full permissions to user and group owner.
- 
No permissions to others. Others should get no permissions on newly created files also.
- 
Allow the group sales read files in account directory and vice versa
- 
Ensure that all new files inherit the group owner
- 
Ensure that only user owner is only allowed to remove their own files
- 
Allow bob to see the content of betty's home directory
 
- 
- 
Force the bob to reset his password on the next log on.
- 
List all local users with UIDs sorted alphabetically. How many of them?
- 
Make sure that Bill can use sudo command
- 
Try to use newgrp cmd
- 
Shrink LV-EXT4-2 by 10% and assign this space to LV-EXT4-1
- 
Initialise the vdd disk using MBR. Assign the whole space to VG-TEST.
- 
Extend the LV-EXT4-1 using 20% of free space
- 
Create new LV-XFS using 60% of free space on VG-TEST
- 
Set label SHARE_DISK for LV-XFS
- 
Mount LV-XFS as /data/local/share
- 
Create the partition on system vda disk and assign all free remaining space to it. Extend the LV-XFS using the 300Mb.
- 
Examine the bash history, clear the memory history and then remove the whole history.
- 
Setup an LDAP client and configure the authentication through srv1.rhcsalab.hi
- 
Download the certificate via scp
- 
Configure autofs- 
Create a masked indirect mount for /srv/homes on srv1.rhcsalab.hi to /homedirs
- 
Create a direct mount for /srv/share on srv1.rhcsalab.hi to /share
- 
Create an indirect mount for /dvd on srv1.rhcsalab.hi to /content/dvd
- 
Create a direct mount for SAMBA
 
- 
- 
Add the second network adapter bridged with srv2
- 
Configure the second network adapter to be able to ping 10.10.10.2/30
- 
Start the copy from /dev/zero to /dev/null with priority of 5 as a background shell job
- 
Review the list of jobs. Pause the shell job, let it continue, stop it properly
- 
Start the copy again and find the PID for this process
- 
Renice the priority to 10
- 
Kill the job
- 
Configure the journal persistence
- 
Reboot the system to rescue mode and unmount all custom disks from fstab
- 
Verify the last reboot logs
- 
Change the default boot target, verify and put it back
- 
Configure the syslogd rule to send all debug messages to /var/log/debug with buffer
- 
Change the default logrotate policy to keep up to 10 log files in backlog
- 
Apply the custom logrotate settings for /var/log/debug- 
Rotate the file daily
- 
Keep the 4 files of backlog
- 
Create the 600 files with root as owner
 
- 
- 
Install kernel, reboot and set the old kernel as a default
- 
Load cdrom module and verify it. Load it with some parameters (autoclose). Make it persistent.
- 
Change the umask to 027 only for root user
- 
Install Apache using the package group, change the port and directory, verify from 10.10.10.2
- 
Install SELinux man pages
- 
Verify if the logrotate configuration is working (both global and custom)
- 
Boot from the rescue disk and mount all entities in fstab back
- 
Reinstall GRUB
- 
Recreate initramfs
- 
Create a different kickstart
- 
SCP it to the server
- 
Reinstall VM with DVD and a new kickstart file
- 
Repeat )
 
 
Михаил, вы сдали экзамен?
ОтветитьУдалить