Linux Foundations
A program works in one terminal and fails in another. Before blaming its code, you need to know whether it received the same input, ran as the same user, and could reach the same files. The environment is part of the explanation, not just the place you happened to run the command.
That’s why our vulnerability research series starts with Linux. We’ll learn to inspect files, permissions, processes, and the shell, then preserve enough evidence for someone else to repeat an observation. You don’t need to memorize every command. You need to know which question a command answers and where to look when the result surprises you.
Prerequisites
Section titled “Prerequisites”Finish Welcome & Course Map, What Is a Virtual Machine?, the one setup path that matches your host, and Prepare Your Course Workspace before you start here. You should be able to open the Ubuntu terminal, find the course directories, stop a command with Ctrl+C, and restore the clean VM snapshot. We’re assuming no prior Linux command knowledge at all, so if that list looks fine, you’re ready.
Module sequence
Section titled “Module sequence”- Linux and the operating system
- Shell, identity, and expansion
- Navigating the Linux filesystem
- File identity and metadata
- Filesystem investigation lab
- Users, groups, and permissions
- Processes, jobs, and signals
- Input, output, pipes, and redirection
- Pipelines, search, and text evidence
- Finding documentation and installing software
- Linux investigation lab