Linux fundamentals
Understand the operating system before relying on security tools.
The idea
Linux systems organize files, processes, users, and permissions through operating-system rules. A shell lets you issue commands and connect tools together. Start with navigation, reading text, inspecting identity, and understanding paths before administrative changes. Commands run with the privileges of the current account unless another mechanism grants more. A graphical interface or a security distribution does not remove the need to understand what each command will affect.
In practice
In a local training folder, inspect your current directory with pwd, list files with ls, and read a known text file before changing anything.
A common misunderstanding
Copying a command without understanding its path, privileges, and options can change more than intended.
Check your understanding
Why check the current directory first?
Think it through: Relative paths are resolved from it, so an otherwise correct command may affect the wrong location.
Know the context before the command
A fictional learner opens a terminal on a training VM. Before following an exercise, they identify the current account, directory, host, and intended file. These details determine what a command can affect. The same text run in a different directory or under an administrator account can have a different consequence.
Separate the shell from the operating system and individual programs. The shell interprets the command line, the operating system manages processes and access, and a utility performs a particular task. Understanding that division helps explain whether an unexpected result came from quoting, permissions, a missing file, or a program option.
Start with observation. Read a small known file, inspect directory contents, and examine process information before changing system configuration. Use the local manual and version information when behavior differs from a tutorial. Distributions share many concepts but may use different service managers, package tools, and defaults.
Make a reproducible first lab
Create a dedicated folder containing two fictional text files. Record its absolute path and the commands used to inspect it. Explain how a relative path changes when the current directory changes. Then document the owner and permissions of one file without altering unrelated locations.
Keep a short learning journal with the question, command, observed result, and interpretation. A command transcript alone is less useful if you cannot explain what it demonstrates. Avoid using elevated privileges merely to make an error disappear; first identify which access the task actually needs. These habits support later security work because investigations depend on precise system context and controlled changes, not just familiarity with a collection of terminal commands.
Keep exploring
References & further reading
Original explanations, with primary references for deeper study.
GNU Coreutils manualLinux man-pages: Process credentials