What it is and Why

This guided workshop in multiple units is your first encounter with the Linux shell, commonly called the "command line interface (CLI)". It is a computer language the user can speak to any Unix system. In six units of 1 to 2 hours of work each, this workshop opens up the newcomer to "talk" freely in a text terminal. This is an essential step in your Linux journey.

Starting as a purely text-based Unix clone Linux has evolved to be a full-fledged operating system with many different graphical user interfaces (GUI) to choose from. It is a free alternative to other operating systems such as Microsoft Windows or Apple's macOS, both of which are proprietary. The Free Software license opens Linux entirely different possibilities. Linux originated in the world of big servers and overtime replaced Unix. For example, all the world's 500 fastest super-computers run Linux. Surprisingly Linux has also taken over the micro and embedded computer fields like IOT and SBC (Raspberry Pi) as well. Linux is also desktop-ready for some time, although the numbers have only recently started to grow.

Experienced system administrators maintain their machines from the command prompt. They compile code, install programs, troubleshoot them in operation, automate routine tasks; all in the text-based environment. Unix relies heavily on text, whether in the form of configuration files or as scripts. Not surprisingly Unix came with an elaborate system of pattern matching in text called 'regular expressions'. The Unix command language is also a programming language. One can write interactive programs in this language which are called shell scripts. Or one may paste other specialized programs together in to these scripts making it the "glue" to hold those programs together.

GUIs are convenient for the end-user but they don't tell you exactly what they do behind the screen. Once something unexpected happens or if you have a task for which there is no option in the GUI, you are stuck. In addition to that the text terminal doesn't require the overhead a GUI needs which is a critical factor in remote system administration.

Learning outcomes

After completing this workshop, students will be able to:

  • interrogate the operating system environment about its key parameters
  • refer the built-in help mechanisms
  • navigate in the Unix file hierarchy
  • create and maintain directories and files
  • edit text files using a modal editor
  • communicate with other users using command tools
Content

The workshop consists of the following six units:

  1. Introduction, Your first log in: Some background on software licencing and you claim your individual shell account in the practice computer.
  2. A session in the Shell: In this unit you will go through a longer terminal session and get a better chance to understand the shell. You start by exploring the system environment and then move on to screen handling. So the commands are limited to getting information from the system - no real interaction.
  3. The built-in help system: Right in the original concept of Unix in 1969 a help system was built in, which was called "on-line help" in those days.
  4. Files, files,..: In the design of the Unix operating system the files are more than mere containers for data. We will walk through the and cover commands to understand the meta information of files and directories and learn to navigate the file system.
  5. Text editors: Next to files text is is a major topic in Unix. In this unit we look at how to edit text. The objective of this unit is to understand what a modal text editor is and why a terminal based text editor has to be modal. Then we start learning the single-key commands used in the original Unix editor ed and its successor Vi, the cult editor in the Unix world.
  6. Talking to others: In this unit you will get to know those original tools for interact with the others, and above all how to mail worked and still does - in the command line.

Each unit contains a video introducing the concepts and demonstrating the assignments. The students are expected to do those assignments and submit them. Some assignments are computer marked. There are also manually graded assignments. Once you submit such an assignment send a message to the teachers asking for grading.

Prerequisites

The participants need to have:

  • a laptop or a PC with a supported version of a desktop operating system like Linux, macOS or Windows. Tablet computers and smartphones are unsuitable. (They may be useful for passive reference in-between, but not for hands-on participation.)
  • The latest version of a mainstream browser running. Open Source browsers like Firefox and the Brave browser are encouraged. 
  • a stable Internet connection
  • a good user-level experience with any computer system.
Teaching method

The content of the workshop is to the most part hands-on, best suited to be delivered through practicals. The theory behind them will be apparent as you do the practicals. Therefore we take a problem-based training approach, also called "inverted classroom". You get the assignments and supporting material before the recording is published. You are supposed to try out, ideally finish, the assignments before watching the recording. Communicate your problems you had and give feedback through the forum.

Assessment

Your progress through the workshop will be continually assessed:

  • All activities have a state Done or Not done. Some are to be flagged Done by you, others are auto-detected.
  • Some activities are graded, either by the teachers or by your colleagues in the peer-review assessment of graded by the teachers.
  • The assignments marked by the teachers have due dates. Late submissions carry a penalty of 20% of max. points. You can re-submit twice. Re-submission also carry a penalty of 20%. The penalties are not cumulative. Added 7 Feb.: The best marks of the attempts go to the grade book.
  • The tests too can be re-submitted twice - subjected to 33% penalty for the question that has been corrected. Added 7 Feb.: The best marks of the attempts go to the grade book.

Note that the order you can do the assignments is restricted through preconditions.

Hint: You can keep track on the deadlines and your progress in the blocks in the right-hand side drawer of the course homepage.

Course completion

To successfully complete the workshop you are required to complete all activities and earn a 60% average marks or more in the graded activities.

Workload

1-2 hours per unit x 6 units = ~10 hours average in total

අවසන් වරට නවීකරණය කරන ලද: සෙනසුරාදා, 11 අප්‍රේල් 2026, 10:36 PM