Vinay Garg Assistant Professor

Teaching Linux to students who have only used Windows

The first lab is not about commands. It is about making the terminal feel less like a punishment.

A dark terminal window with a prompt, a file listing and a blinking cursor

In short

  • The first lab is not about commands. It is about making the terminal feel survivable.
  • Students who are allowed to break a throwaway directory stop fearing accidental damage.
  • One honest hour on man and --help removes most of the room's dependence on the teacher.
  • Assess the reasoning written down, not the list of commands memorised.

25 years

teaching computing at Multani Mal Modi College, Patiala

since 2000

14 weeks

one semester of Linux labs

course plan

3

mistakes almost every beginner makes in the first hour

classroom observation

Every year a room of students who have never opened a terminal is asked to learn Linux in fourteen weeks. Every year the same three things go wrong in the first hour: the wrong shell, the wrong path, and the quiet belief that a black window means they have broken something.

Start with what a terminal actually is

Before the first command, I show them that the terminal is a conversation with a program, and that the program answers. Type date, get the date. Type whoami, get yourself. Nothing is being installed, nothing is at risk, and the fear drops enough to learn in.

Give them a home to break

The second lab creates a throwaway directory and invites deliberate destruction: copy files, rename them, delete a whole tree, restore it from a copy. Students who are allowed to break something deliberately stop being afraid of breaking something accidentally.

  • Paths explained as directions, not syntax: ., .., ~.
  • Permissions shown with a real mistake — a script that will not run because it is not executable.
  • One honest hour on man and --help, so the room stops needing me for every flag.

Assessment that tests thinking

Instead of asking for a list of commands, I give a broken situation: a service that will not start, a log with three plausible errors, and one hour. The marks are for the reasoning they write down, not for the fix. Most of them find the fix anyway.

Twenty-five years in, the pattern has not changed. Confidence is the prerequisite, not the outcome.

Sources

Frequently asked questions

How do you teach Linux to students who have only used Windows?

Start with what a terminal is rather than with commands: type date, get the date. Then give students a throwaway directory they are invited to destroy, so the fear of breaking something goes away before the syllabus begins.

Which distribution is best for a first Linux lab?

Any mainstream one with a package manager students can read. Ubuntu or Debian are the least surprising: the documentation matches what they see, and a mistake is usually recoverable with one command.

How long before students are comfortable in the terminal?

Roughly three lab sessions, if the first two include deliberate mistakes and a real task — copying, renaming, permissions — rather than a list of flags to memorise.

Should students use a graphical desktop at all?

Yes, at the start. A desktop makes the system legible, and the terminal becomes a faster way to do a thing they already understand, instead of a foreign country.

Vinay Garg

Vinay Garg

Assistant Professor of Computer Science at Multani Mal Modi College, Patiala. Twenty-five years of teaching web programming, and a habit of building the things I teach about.