LICM common mistakes
LICM · Understand the traps and how to avoid them.
When asked to produce command output, the candidate recites the purpose of a command from memory instead of writing the exact invocation and its realistic output, for example answering 'use grep to find text' rather than giving the full pipeline and the lines it would print.
The Linux Community and a Career in Open Source material is largely conceptual, so candidates study definitions and never practise producing verifiable command results, then freeze when a task requires a concrete command line.
What to do instead
For every command you meet, practise writing the command, its arguments, and the expected output as one self-contained block. Drill until you can produce a working example for grep, find, cut, and sort without consulting notes, and check each example by running it on a real system.
The candidate describes the four freedoms of free software loosely as 'free of charge and open code', confusing free software with open source and omitting the freedom to run, study, redistribute, and improve the program.
The terms are used interchangeably in everyday speech, and candidates skim the licensing material because it seems non-technical, so the precise freedoms and the role of licences such as the GPL are never fixed in memory.
What to do instead
Memorise the four freedoms as a numbered list and tie each to a licence consequence: GPL requires derivative works to stay under the GPL, while permissive licences allow relicensing. Rehearse the distinction between 'free as in freedom' and 'free as in price' with one concrete example each.
The candidate navigates only with absolute paths, so when asked to move from /var/log to a sibling directory or to explain what cd .. does from a given location, they compute the wrong target or write a path that does not exist.
Beginners learn a handful of absolute paths by rote and never build a mental model of the directory tree, so relative paths and the special entries . and .. remain abstract.
What to do instead
Draw the filesystem tree on paper and trace each cd, using pwd after every move to confirm. Practise a sequence such as cd /var/log, cd ../lib, cd ../../etc and predict the result before checking it.
The candidate confuses reading a file with changing permissions on it, for example answering that chmod is needed to let a user view a file, or that chown grants read access, instead of distinguishing ownership, mode bits, and the access check.
Permissions are taught as a table of commands rather than as an evaluation order, so candidates cannot say which of owner, group, or other applies, or how read, write, and execute differ for files and directories.
What to do instead
Learn the check order: owner first, then group, then other, using the first match only. Practise decoding a mode such as rwxr-x--- into owner, group, and other rights, and state separately what read and execute mean on a directory versus a file.
The candidate uses redirection and pipes interchangeably, writing command > file when the output should be appended, or cmd1 | cmd2 when the second command needs a filename argument, and cannot explain the difference between > and >> or 2>.
The symbols look similar and candidates memorise them as decoration rather than as file-descriptor operations, so the mapping from descriptor 1 and 2 to stdout and stderr is never solid.
What to do instead
Anchor each operator to a descriptor: > sends stdout to a file and truncates it, >> appends, 2> sends stderr, and | connects stdout of one process to stdin of the next. Practise redirecting stdout and stderr to separate files in one command and verify with cat.
The candidate treats every command as if it ran as root, so answers omit sudo where a privileged operation is required, or add sudo where it is unnecessary, and they cannot say why a permission-denied error appeared.
Practice environments often run as root, so the distinction between an ordinary user and a privileged one never becomes visible, and the candidate never reads an error message to diagnose the cause.
What to do instead
Work deliberately as a non-root user. For each task, decide first whether it modifies system state, then add sudo only when needed, and read the resulting error text to confirm the cause. Rehearse the difference between a permission error and a missing-file error.
The candidate answers questions about package management by naming a tool without the correct subcommand or syntax, for example writing apt install without the update step or confusing apt with dpkg, and cannot state which distribution family each belongs to.
Package commands are learned by copying snippets, so the update, install, and remove phases blur together and the Debian versus Red Hat family split is never mapped explicitly.
What to do instead
Build a two-column table for Debian-family and Red Hat-family tools and fill in the exact command for refresh, install, remove, and query. Practise the full sequence on a test system, including the refresh step before installing, and note which tool works at the package level versus the repository level.
The candidate edits a configuration file or changes a service without verifying the result, so answers end at 'edit the file' and never include the reload, restart, or status check that proves the change took effect.
Study material often presents editing as the goal, and candidates never develop the habit of closing the loop with a verification step, which is exactly what scenario questions test.
What to do instead
Adopt a fixed three-step pattern for every configuration task: change, apply, verify. State the reload or restart command and the status or log check that confirms success, and practise reading the service status output to spot a failed start.
The candidate uses find, grep, and cut with the wrong option because they memorised short flags without their meanings, for example using grep -r when a filename pattern was wanted, or find -name when a content search was intended.
Options are learned as isolated facts rather than as answers to a question, so the candidate cannot map a stated goal to the correct tool and flag combination.
What to do instead
For each tool, write one sentence describing what it searches: find searches the filesystem by attributes, grep searches file contents by pattern, cut selects fields or characters. Then drill one canonical invocation per tool and predict the output before running it.
The candidate describes a process only by name and cannot explain how to inspect or control it, so questions about foreground and background jobs, signals, or finding a process identifier are answered with vague statements such as 'kill it'.
Process management is abstract until practised, and candidates who never use job control or send a signal have no concrete model of what a process identifier is or what a signal does.
What to do instead
Practise starting a long-running command, suspending it, resuming it in the background, listing jobs, and terminating it by identifier. Learn the difference between a polite termination signal and a forceful one, and state which command lists processes and which sends the signal.