Ninad Pathak

You have `~/.bashrc` open beside `~/.profile`, and neither filename tells you which one shaped the terminal you just started. I couldn’t resist digging into how Bash chooses between them, because the answer depends on the kind of shell it opened. Getting that choice right helps explain why an alias appears in one terminal but a

A single `report.log.gz` and a `logs.tar.gz` can both look like compressed files, but only one is an archive of directory paths. I couldn’t leave that distinction alone, because it decides which command gives you the file you meant to create. Once the output’s shape is clear, you can match the command to keeping a source

A command like `sudo -u nobody id -un` runs as a different user than `sudo id -u`, even though both start the same way. I kept digging into what decides whether either request is allowed. That distinction helps you match sudo’s command form to the identity your task needs. The answer comes down to what

Bash keeps your history in two places, and the list that the history command prints is not the file the next shell reads. I ran history -c on a test session and printed the file straight afterwards, and every line was still in it. Clearing bash history means handling both stores, and the file is

man opens the manual page for a command from /usr/share/man, right there in the terminal. No network, and no browser tab. man -k found the page I could not name from its one-line description, and man -f listed two pages under the same name. The section number settles which one you get. What man reads,

tar turns a folder into a single file on any Linux system, and the same command compresses it on the way. Understanding the option string is the whole job, because tar -czvf stacks four unrelated jobs into one word. What the letters in tar -czvf are doing Read the string as four jobs rather than