The `du -sh ~` command (disk usage, summary, human-readable) is the direct tool for reporting the total space consumed by a specific directory, in this case the user’s home. `df` shows filesystem-level usage, `ls` shows file details but not aggregate size, and `mount` shows what is mounted, not usage.

The ‘Permission denied’ error when trying to execute a script directly (`./deploy.sh`) typically means the execute (`x`) permission is missing for the user. `chmod +x` adds this permission. Using `bash deploy.sh` works but is a workaround, not a fix. A shebang is important but not the cause of this specific error if `bash script.sh` works.

`top` provides an interactive, continuously updating dashboard of system processes, defaulting to a sort by CPU usage. `ps aux` gives a static snapshot. `vmstat` reports system-wide virtual memory statistics, and `free` shows memory usage, but neither focuses on individual processes interactively.

The `w` command (or `who`) shows who is logged on and from where. Following this with `ps -u [username]` (or similar) shows the processes owned by that specific user, revealing their active commands. `id` shows your own identity, `last` shows login history, and `/etc/passwd` is the user database, not current sessions.

The `tar -xzvf` command extracts (`x`) a gzipped (`z`) tar archive verbosely (`v`) from the specified file (`f`). This is the standard one-step method. After extraction, using `ls` to list the new directory’s contents and looking for documentation files like README or INSTALL is standard practice for installation guidance.

The fundamental best practice is to create a backup before modifying critical configuration files. This allows for a quick and safe rollback if the edit introduces an error or undesired behavior. The choice of editor is personal preference; testing should be done in a staging environment first; and changing a setting in multiple unspecified places is not a standard practice.

The `while read -r line; do … done < file` construct is the robust and standard method. The `-r` option prevents backslash interpretation, and input redirection (`< file`) is efficient. The `for` loop with command substitution will split on all whitespace, not lines. Piping with `cat` works but is less efficient. The last option incorrectly tries to reopen the file on each loop iteration.

The correct `find` syntax uses `-name “*.conf”` to match the extension and `-mtime -7` to match files modified less than 7 days ago. `-mtime 7` would mean exactly 7 days. The `-newer` predicate requires a reference file. Using `ls` with grep is fragile and not the purpose of `ls`.

`ping` is the fundamental tool for testing basic IP-level connectivity (reachability) and measuring round-trip latency. `nslookup` tests DNS resolution only. `netstat` shows local listening ports. `traceroute` maps the network path, which is useful but usually comes after confirming basic connectivity with `ping`.

The `du -sh ~` command (disk usage, summary, human-readable) is the direct tool for reporting the total space consumed by a specific directory, in this case the user’s home. `df` shows filesystem-level usage, `ls` shows file details but not aggregate size, and `mount` shows what is mounted, not usage.0