[SIZE="5"]Its a Request to a LINUX Friendlier to have the Step Provided in Screenshorts[/SIZE]01. Login to server X as root.
02. Create an archive of /etc using gzip compression. Save the file as
/tmp/etc.tar.gz.
03. Copy the /tmp/etc.tar.gz file from your server X to the /backup directory on
your desktop X machine.
04. Extract the compressed archive to /backup on desktop X.
05. Print all usernames that begin with the letter r.
06. Print all usernames that begins with the letter g.
07. Print all accounts whose shells (last column) are /sbin/nologin
08. Print all accounts that have a UID or GID (third or fourth columns) of O.
09. Print all accounts that have a UID or GID in the range of 10-19.
10. List all files in /usr/share/doc that end with the number four.
11. Print all lines in /etc/hosts that have a number in them.
12. Print the line in /etc/hosts that has a 127.0.0.1
13. Run the following command as student, and redirect STDOUT to /tmp/output.txt
and redirect STDERR to /tmp/error.txt.
14. Run the following command as student, and redirect both STDOUT and STDERR to
the /tmp/all.txt file.
15. Sort the /etc/passwd file and send it to the default printer
16. Print out lines in /etc/passwd that have a three digit number between colons
(
17. a. What is its current IP Address?
b. What is its current CIDR subnet mask?
c. What is its current default gateway?
d. What is its current hostname?
e. What are its current DNS servers?
18. Run the first script to mis-configure your networking:
Lab-break-net 1
19. Symptom: A web browser is unable to access the web page at
http://instructor.remote.test
20. Apply the three steps: TEST, CHECK, FIX to identify and resolve the problem.
21. Run the second script to mis-configure your networking:
Lab-break-net 2
22. Symptom: A web browser is unable to access the web page at
http://instructor.remote.test
23. Apply the three steps: TEST, CHECK, FIX to identify and resolve the3 problem.
24. Create a new partition and ext4 file system that is 400 MB in size. The file
system should persistently mount under /data.
25. Persistently and a swap partition that is 200 MB in size.
26. Create a volume group called vg1 of 500 MB on serverX.
Create a logical volume called lv1 of 200 MB on vg1.
Format the logical volume with ext4 and mount it under /data.
27. Create a group called sysadmin.
Create two users called u1 and u2 and set the password to redhat.
sysadmin should be the secondary group of u1 and u2.
Create another user called guest who is not a member of sysadmin and who
should not have any login shell.
28. Create a directory called /database whose group owner should be sysadmin.
Sysadmin group member should have full access on /database and others should
have no access on it.
29. Schedule a cron job for u1, so that a disk free report is mailed to u2 every
day at 7:30 p.m.
30. You will now set up the automounter to automatically mount an NFS export on a
specified direct5ory on demand.
• The NFS server is instructor.example.com
• The NFS export on the server is /var/ftp/pub
• The automatic mount point on your station should be /server/public
• Use an indirect map (not /net) to implement this
• Validate that the automount works by changing directory to the mount point and accessing the files in the share.
Perform the following steps:
1. Create/modify autofs service configuration files.
2. Reload the automounter.
3. Access the share.
31. Using ACLs to Grant and Limit Access
This lab uses users and groups created earlier on server X. If you do not
already have the users and groups defined, run lab-add-users on server X.
Graduate students need a collaborative directory titled /opt/research,
where they can store generated research results. Only members of the groups
profs and grads should be able to create new files in the directory, and new
files should have the following properties:
• The directory should be owned by user root.
• New files should be group owned by the group grads.
• Professors (members of the group profs) should automatically have read/write access to new files.
• Summer interns (members of the group interns) should automatically have read-only access to new files.
• Other users (not a member of groups profs, grads, or interns) should not be able to access the directory and its contents at all.
