Changes

← Older edit

Tutorial11: Shell Scripting - Part 1

463 bytes added, 20:36, 4 September 2023

no edit summary

{{Admon/caution|DO NOT USE THIS VERSION OF THE LAB. This page will no longer be updated.|'''New version here:''' https://seneca-ictoer.github.io/ULI101/A-Tutorials/tutorial11 '''Andrew's students please go here:''' http://wiki.littlesvr.ca/wiki/OPS145_Lab_10}}

=INTRODUCTION TO SHELL SCRIPTING=

|- valign="top" style="padding-left:15px;"

|colspan="2" |'''Slides:'''<ul><li>Week 10 11 Lecture 1 Notes: [https://~~matrix~~wiki.cdot.senecacollege.ca/~~~chris.johnson~~uli101/~~ULI101~~slides/ULI101-~~Week10~~11.1.pdf | PDF] | [https://~~matrix~~wiki.cdot.senecacollege.ca/~~~chris.johnson~~uli101/~~ULI101~~slides/ULI101-~~Week10~~11.1.pptx PPTX] Week 10 11 Lecture 2 Notes:</li><li> [https://~~matrix~~wiki.cdot.senecacollege.ca/~~~chris.johnson~~uli101/~~ULI101~~slides/ULI101-~~Week10~~11.2.pdf | PDF]] | [https://~~matrix~~wiki.cdot.senecacollege.ca/~~~jason.carman~~uli101/slides/ULI101-~~Week10~~11.2.pptx PPTX] </li></ul>

=INVESTIGATION 1: CREATING A SHELL SCRIPT=

'''ATTENTION''': ~~Effective '''May 9, 2022''' - this~~ This online tutorial will be required to be completed by '''Friday in week 12 by midnight'''~~ ~~to obtain a grade of '''2%''' towards this course

In this investigation, you will learn how to create and run a '''Bash Shell script'''.

# Issue the following linux command to '''add''' execute permissions for your shell script: chmod u+x hello

# Issue the following to run your shell script: ./hello Did your shell script run?

# Issue the following Linux command to run a checking script: ~uli101/~~week10~~week11-check-1

# If you encounter errors, make corrections and '''re-run''' the checking script until you receive a congratulations message, then you can proceed.

::In the next investigation, you will learn to create and run shell scripts that use '''variables''', '''positional''' and '''special parameters'''. You will also learn how to add a '''she-bang line''' at the top of a shell script to force it to run in a specified shell. Proceed to the next investigation.

# Exit your Matrix session, and log back into your Matrix session.

# Re-run the '''hello.bash''' shell script by just using the name. What did you notice? The setting of the '''PATH''' environment variable only worked in the current session only. If you exit the current Matrix session, then the recently changed settings for environment variables will be lost. You will in a future tutorial how to set environment variables in '''start-up''' files.

# Issue the following Linux command to run a checking script: ~uli101/~~week10~~week11-check-2 | more If you encounter errors, make corrections and '''re-run''' the checking script until you receive a congratulations message, then you can proceed. Unlike '''Environment variables''' that are used to set the environment of the shell or shell scripts, '''User-created''' variables are "customized" that the user can set or allow a user to set the variables' values. Let's create a Bash shell script that contain '''user-created variables'''.

# Use a text editor to create a Bash shell script called '''user-variables.bash'''

# Add the following lines to the beginning of the ''user-variables.bash'' file: #!/bin/bash read -p "Enter your Full Name: " name read -p "Enter your age (in years): " age echo "Hello $name - You are $age years old"

# Issue the '''chmod''' command to add execute permissions for the user for the '''dog-years.bash''' file.

# Issue the following to run the '''dog-years.bash''' Bash shell script: ./dog-years.bash Enter your age to see what happens.

# Issue the following to run a checking script: ~uli101/~~week10~~week11-check-3 | more If you encounter errors, make corrections and '''re-run''' the checking script until you receive a congratulations message, then you can proceed.

:In the next investigation, you will use '''control-flow statements''' to allow your shell scripts to perform differently under different situations.

# Issue the following Linux command to add execute permissions for your shell script: chmod u+x for-2.bash [[Image:for-2.png|thumb|right|175px|Output of a shell script using the '''for''' loop without a '''list'''.]]

# Run your shell script by issuing: ./for-2.bash 10 9 8 7 6 5 4 3 2 1 How does this differ from the previous shell script? You will learn in a couple of weeks more examples of using loop statements. Let's run a '''checking-script''' to confirm that both your '''for-1.bash''' and '''for-2.bash'''

# Issue the following Linux command to run a checking script: ~uli101/~~week10~~week11-check-4 | more If you encounter errors, make corrections and '''re-run''' the checking script until you receive a congratulations message, then you can proceed.

= LINUX PRACTICE QUESTIONS =

simulate a quiz:

https://~~ict~~wiki.cdot.senecacollege.ca/~~~murray.saul~~uli101/~~uli101~~files/uli101_week10_practice.docx

Your instructor may take-up these questions during class. It is up to the student to attend classes in order to obtain the answers to the following questions. Your instructor will NOT provide these answers in any other form (eg. e-mail, etc).

:OUTPUT:

_________________________________________________________________________________

Author: Murray Saul

License: LGPL version 3

Link: https://www.gnu.org/licenses/lgpl.html

_________________________________________________________________________________

[[Category:ULI101]]

Andrew

Bureaucrats, Administrators

1,234

edits

CDOT Wiki β

Changes

Tutorial11: Shell Scripting - Part 1

CDOT Wiki ^β