1,576
edits
Changes
Updates lab to include basic OS-level user management, and moves update task to the beginning of the lab.
=== Purpose / Objectives of Lab 3 ===
In this lab, you will practice working with the Linux command line by manipulating the file system in two separate investigations. You will also update your system at the end of this laband create a secondary user.
If you encounter technical issues, please contact your professor via e-mail or in your section's Microsoft Teams group.
# Your Seneca login credentials
= INVESTIGATION 1: Create the Directory Structure =[[Image:Ops705_lab3_fig1.png|thumb|right|250px|Figure 1. Square icons are directories, oval icons are empty text files.]]In this investigation, you'll create the directory structure and text files you see in the tree diagram below. You will do so entirely on the command line using the utilities and commands provided to you in the Week 3 lecture. You work will be done entirely in your home directory. To begin: # Start your Linux VM in AWS (this may take a few minutes)# Connect to the VM remotely using SSH (Refer to [[OPS705_Lab_2 | Lab 2]])# Navigate to your home directory with this command: <code>cd ~</code># In your home directory, recreate the directory tree in Figure 1. ''yourusername'' should be your own username home folder that already exists.# '''Do not remove lab2.txt''' = INVESTIGATION 2: Moving Files =In this investigation, you're tasked with moving a set of existing files. You will download and run a script, which will create a set of files in '''~/tmp'''. It is then your job to create the directory structure seen in Figure 2, and move the files from '''~/tmp''' to their proper location according to the file tree diagram. '''Do not delete and recreate files, and do not delete your work from Investigation 1.'''[[Image:Ops705_lab3_fig2.png|thumb|right|250px|Figure 2. Square icons are directories, oval icons are empty text files.]] # On your Linux VM, from your home directory, download script for this lab with the following command: <code>wget https://ict.senecacollege.ca/~chris.johnson/ops705/lab3_script.bash</code># Give the script execute permissions: <code>chmod u+x ~/lab3_script.bash</code># Run the script: <code>~/lab3_script.bash</code># Check that the files 13-17 have been created in '''~/tmp''' (These ''must'' come from the script, do not create them yourself)# Using Figure 2 as a model, create the '''~/shared''' directory structure# Using Figure 2 as a model, move the files from '''~/tmp''' to their proper location in '''~/shared''' = INVESTIGATION 3: Update Linux =
This investigation simply has you update your Red Hat Enterprise Linux (RHEL) installation. We'll cover package / software management and security best practices in a later lab.
To update the operating system, you'll need to have administrative access. There are two ways to do this: logging in to an admin account, or running a command as your regular user with temporary admin powers. We call this ''privilege elevation'' or ''elevating your privileges''. Only regular user accounts that belong to the admin group can do this. The name of the admin group changes depending on the distribution of Linux; for RHEL, it's the '''wheel''' group. The ''ec2-user'' account you use was automatically added to this group as part of the AWS deployment process.
First, let's login:
# Start your Linux VM in AWS (this may take a few minutes)
# Connect to the VM remotely via SSH using your ''ec2-user'' account. (Refer to [[OPS705_Lab_2 | Lab 2]])
Now, let's update the system:
* Here's the update command for this distro: <code>yum update</code>
You'll be disconnected from your remote session as the SSH server inside your VM shuts down.
It may take a few minutes for the VM to restart. You can track it's progress through the EC2 Instance page. One Once back up and running, log back in to confirm everything still works. = INVESTIGATION 2: Adding A New User =In this investigation, we'll create a second user on your Linux VM from the command line, using your Seneca username. This is a required first step before continuing with the lab. '''Replace ''yourusername'' with your Seneca username in each command.''' (For example: If your e-mail address is cjohnson99@myseneca.ca, your Seneca username is cjohnson99) To begin: # Start your Linux VM in AWS (this may take a few minutes)# Connect to the VM remotely via SSH using your ''ec2-user'' account. (Refer to [[OPS705_Lab_2 | Lab 2]])# To create your second user, run: <code>sudo useradd -G wheel ''yourusername''</code># Assign a password to this account: <code>sudo passwd ''yourusername''</code> (The session will ask you for your new password twice as a security precaution. When you type passwords on a Unix/Linux OS, the cursor remains blank and doesn't move. Just type it out carefully and hit Enter. It may take you a few tries the first time. You'll get used to it.)# Login to your new account: <code>su - ''yourusername''</code> ('''Warning:''' Do not skip this step!) Now, let's copy authentication information to your new account so you can log in directly next time. From your secondary ''yourusername'' acount: # Copy the authorized key file with this command: <code>sudo cp ~ec2-user/.ssh/authorized_keys ~/.ssh/authorized_keys</code> (It may ask for a password. Use the secondary user account password you just set up.)# Change the new file's ownership: <code>sudo chown ''yourusername'':''yourusername'' ~/.ssh/authorized_keys</code># Now, completely log out back to your local system. Type <code>exit</code> and press Enter to get back to your ''ec2-user'' account. Then, type <code>exit</code> and press Enter again to fully log out.# From your local machine, use the SSH command to login, but replace ''ec2-user'' before the @ symbol with ''yourusername''. It should log you in directly! Use that new account for the rest of this lab. = INVESTIGATION 3: Create the Directory Structure =[[Image:Ops705_lab3_fig1.png|thumb|right|250px|Figure 1. Square icons are directories, oval icons are empty text files.]]In this investigation, you'll create the directory structure and text files you see in the tree diagram below. You will do so entirely on the command line using the utilities and commands provided to you in the Week 3 lecture. You work will be done entirely in your secondary user's home directory. To begin: # Connect to the VM remotely via SSH using your secondary account.# Navigate to your home directory with this command: <code>cd ~</code># In your home directory, recreate the directory tree in Figure 1. ''yourusername'' should be your own username home folder that already exists.# '''Do not remove lab2.txt''' = INVESTIGATION 4: Moving Files =In this investigation, you're tasked with moving a set of existing files. You will download and run a script, which will create a set of files in '''~/tmp'''. It is then your job to create the directory structure seen in Figure 2, and move the files from '''~/tmp''' to their proper location according to the file tree diagram. '''Do not delete and recreate files, and do not delete your work from Investigation 1.'''[[Image:Ops705_lab3_fig2.png|thumb|right|250px|Figure 2. Square icons are directories, oval icons are empty text files.]] # On your Linux VM, from your home directory, download script for this lab with the following command: <code>wget https://ict.senecacollege.ca/~chris.johnson/ops705/lab3_script.bash</code># Give the script execute permissions: <code>chmod u+x ~/lab3_script.bash</code># Run the script: <code>~/lab3_script.bash</code># Check that the files 13-17 have been created in '''~/tmp''' (These ''must'' come from the script, do not create them yourself)# Using Figure 2 as a model, create the '''~/shared''' directory structure# Using Figure 2 as a model, move the files from '''~/tmp''' to their proper location in '''~/shared''' Voila, you're done!
= Lab Submission =