Please code in Linux. Do not worry about the AWS since that is just Amazon Web Services used for cloud computing. I need the syntax commands and steps below.

Part 2: Scripting, Paths, and Arguments, Oh My! (4 pts) 1. In your Labo4 folder, create a folder called scripts . Inside that folder, create two scripts, one named marco and one named polo. 2. For now, have marco and polo print a statment to standard output when they are run - This is from marco and This is from polo respectively. 3. Add the folder these scripts are located in to your PATH. (2 pts) First use the export command in you terminal to test you have properly added to the PATH. Write this command in your lab notes. o If you really mess this up, log out ( exit) your AWS Linux connection and ssh back in. You can refer to here to verify it looks how it used to. Test that marco and polo can now be run in any directory. Add your working export command to your home directory's profile. o If you really mess up, there is a backup profile file here. You can copy and paste the contents. 4. Modify marco so that when it is run, it should save the current working directory in a file so that polo can reference it. (1 pt) Hint: If marco can be ran in any directory and polo can be run in any directory, should the path to the file be relative or absolute? 5. Modify polo so that when it is run, it echos the command the user needs to go to the directory marco was called in. Part 2: Scripting, Paths, and Arguments, Oh My! (4 pts) 1. In your Labo4 folder, create a folder called scripts . Inside that folder, create two scripts, one named marco and one named polo. 2. For now, have marco and polo print a statment to standard output when they are run - This is from marco and This is from polo respectively. 3. Add the folder these scripts are located in to your PATH. (2 pts) First use the export command in you terminal to test you have properly added to the PATH. Write this command in your lab notes. o If you really mess this up, log out ( exit) your AWS Linux connection and ssh back in. You can refer to here to verify it looks how it used to. Test that marco and polo can now be run in any directory. Add your working export command to your home directory's profile. o If you really mess up, there is a backup profile file here. You can copy and paste the contents. 4. Modify marco so that when it is run, it should save the current working directory in a file so that polo can reference it. (1 pt) Hint: If marco can be ran in any directory and polo can be run in any directory, should the path to the file be relative or absolute? 5. Modify polo so that when it is run, it echos the command the user needs to go to the directory marco was called in