Week 4 at a Glance
- If you haven’t done so already, complete the installations of openSUSE twice (one for KDE and one for GNOME)
- Optionally: Complete activities 4-1 and 4-2
- With your own Linux computer, you can now use GUI editors. Knowing the terminal window editors (e.g. vi and vim) is always a good thing, but if you wish to use a GUI editor, you may do so.
- Set up your system for SSH or VNC acccess
- Read Chapter 5 - Linux Operations & Administration 1st Edition Authors: Nadine Basta, Dustin Finamore, Alfred Basta, Serge Palladino - Publisher: Cengage Learning
- Watch a YouTube video: How to Understand Linux File and Directory Permissions: Linux Server Training 101
- Watch a YouTube video Setting and exporting environment variables
- Watch a YouTube video: Bash Scripting Basics Part 1
- Participate in the Discussion Board for Chapter 5
- Complete all ten activities in Chapter 5 - Linux Operations & Administration 1st Edition Authors: Nadine Basta, Dustin Finamore, Alfred Basta, Serge Palladino - Publisher: Cengage Learning
- Take the Chapter 5 Reading Quiz – Quiz generated from the following publisher test pool. - Linux Operations & Administration 1st Edition Authors: Nadine Basta, Dustin Finamore, Alfred Basta, Serge Palladino - Publisher: Cengage Learning
- Configure IRC for your own Linux system(s)
Intro:
This chapter is partially on writing scripts. System administration often involves completing the same steps multiple times (such as what I do each semester to create accounts for students in my classes). One way would be to blindly type the same commands over-and-over, month-after-month. The more "interesting" way is to write a script once to do the work for you, and then not have to complete all of the steps each time. (Ideally, I prefer to write a script that runs regularly that does things without needing me to be near the keyboard at all).
For small programs, I would use bash (or my own favorite shell tcsh) to do something. If I know I am trying to build a medium-sized or large-sized program, or if the program grows too big, I switch to a different language, such as Python (which is taught in CIS 133).