You don't need to become a sysadmin. You need the slice of Linux that unblocks firmware work: moving fast, reading logs, reaching a remote machine, and automating the boring flash-and-test loop.
Recipes you'll use weekly
Hunting through logs. A device prints thousands of lines and the one error matters. grep -i "error\|panic\|wdt" serial.log finds it; piping build output through a filter beats scrolling. Learn pipes and redirection once and every future debugging gets faster.
→ Searching, transforming and inspecting data
→ Shell basics and text processing
Talking to serial from the terminal. screen /dev/ttyUSB0 115200 (or minicom) gets you a monitor without opening an IDE. When a port disappears after a reboot, knowing how to list devices and check permissions saves an hour of replugging cables.
→ Permissions, users and processes
Reaching remote machines. SSH into a build server or a gateway in the field, copy firmware over with scp, forward a port to see a remote dashboard locally. Most "the server is broken" moments are a wrong path, a dead service, or a full disk — all diagnosable over SSH.
Automating the loop. Flashing ten boards by hand is how mistakes happen. A five-line shell loop that builds, flashes, and captures each board's first minute of logs turns a painful afternoon into a coffee break.
→ Pipes, processes and automation
Start at Linux Fundamentals for the OS side, then the command-line tools above for speed. Post your useful one-liners, serial-port recipes, SSH quirks, or WSL fixes. Tag with linux or terminal.