Linux Beginner Quick Start Notes

Who This Is For

If you are truly starting to use Linux on a remote server for the first time, this is a good first note to read.

The goal is not to learn every command at once. The goal is to build a small but stable workflow so you can:

• Know what to check after logging into a server.
• Stop getting lost in paths and permissions.
• Know which commands to check first when processes, services, or logs look wrong.
• Keep your work alive after a disconnect instead of starting over.

The Minimal Model For Remote Linux Work

You can first understand remote-server work as this chain:

local computer -> SSH login -> shell commands -> files / directories -> processes / services -> logs / ports

Then add one very important session-keeping tool:

Do not panic when SSH disconnects -> tmux keeps the session alive

If you remember this model first, Linux becomes much clearer for beginners.

What To Do After First Logging Into A Server

The easiest beginner mistake is not "not knowing commands". It is not knowing where you are, who you are, and what you are allowed to do.

So after logging in, I recommend checking these first:

whoami
pwd
ls -la
uname -a

These answer:

• whoami: which user am I?
• pwd: which directory am I in?
• ls -la: what files are here, including hidden files?
• uname -a: what kind of system is this roughly?

If you have sudo permission, also check:

sudo -l
hostname

Ten Core Commands To Learn First

Command	Purpose	Beginner mental model
pwd	Show the current directory	Run it whenever you are unsure where you are
ls -la	List directory contents	See hidden files and permissions together
cd	Change directory	Move yourself to another place
mkdir	Create a directory	Make a new folder
cp	Copy files	Copy before changing; safer than overwriting directly
mv	Move or rename	Handles both moving and renaming
rm	Delete files	Real deletion, no recycle bin
cat / less	View file content	cat for short files, less for long files
find	Search for files	Useful when you do not know where something is
du -sh	Check directory size	Common for disk usage troubleshooting

Learning these first already covers many everyday operations.

Paths, Files, And Directories

Absolute And Relative Paths

• Absolute paths start from the root directory, such as /home/user/project.
• Relative paths start from the current directory, such as ./project or ../project.

Remember these common symbols:

• .: current directory
• ..: parent directory
• ~: current user's home directory
• /: root directory

If you often get lost in paths, read:

• Output Absolute Paths

Hidden Files

In Linux, files or directories starting with . are usually hidden, for example:

.ssh
.bashrc
.gitconfig

So I recommend using:

ls -la

instead of only ls.

Create, Copy, Move, And Delete

mkdir demo
cp file.txt file.bak
mv old.txt new.txt
rm old.log

The most useful habits here are:

• Copy a backup before making large changes.
• Before deleting, check pwd and ls once more.

Commands Not To Use Carelessly At First

These commands are not forbidden, but they are risky before you are confident about the target path:

• rm -rf
• chmod -R 777
• chown -R
• Overwrite, move, or delete operations with sudo

The reason is simple: if the path is wrong, the damage is often not "one file broke", but "a large area became messy".

Permissions: Learn To Read First

For now, remember three things:

1. Linux distinguishes the current user from root.
2. Many system directories and service operations need sudo.
3. Wrong file permissions can break SSH, scripts, and config files.

Check your current identity:

whoami
id

Check file permissions:

ls -l

One common permission problem is SSH private key permissions. For that, read:

• Connect To A Remote Server With An SSH Private Key

Processes, Services, And Logs

When a service does not start, a program hangs, or a port cannot be reached, do not guess first. Check in this order:

1. Is the process running?
2. Is the service status correct?
3. What do the logs say?

Check Processes

ps -ef
ps -ef | grep python
top

To stop a process:

kill <pid>
kill -9 <pid>

Do not use kill -9 as the default. Try normal kill first, and only escalate after confirming the process cannot exit normally.

Check systemd Services

Many Linux distributions manage services with systemd.

Common commands:

sudo systemctl status ssh
sudo systemctl restart ssh
sudo systemctl enable ssh

On Ubuntu / Debian, systemctl is usually the first entry point for checking services such as Docker, SSH, Nginx, and Jupyter.

Check Logs

Service logs:

sudo journalctl -u ssh -n 100 --no-pager

Regular log files:

tail -f app.log
less app.log

If you are not familiar with output redirection and writing logs to files, read:

• Redirect Error Output

Minimal Workflow On A Remote Server

1. Connect With SSH

If SSH is not configured yet, read:

• Configure SSH From Scratch
• Connect To A Remote Server With An SSH Private Key

2. Keep The Session With tmux

tmux is worth learning early on remote servers.

Minimal usage:

tmux new -s work

Detach without ending the task:

Ctrl+b d

Attach again:

tmux attach -t work

If you often run long tasks, remote training, or long environment installations, tmux is basically not optional.

Topic page:

• Tmux Terminal Multiplexer Introduction

3. Use Port Forwarding For Remote Services

If a service only listens on localhost on the remote machine and your local browser cannot access it, think of port forwarding before exposing the service publicly.

One easy starting point:

• VS Code Port Forwarding

File Search And Disk Troubleshooting

Two common remote-server problems are:

• Where is the file?
• What filled the disk?

Remember these two entry points first:

find .
du -sh .

More detailed notes:

• Linux find Command Explained
• Check File Or Directory Disk Usage

What To Read Next

When you can do the following, your Linux basics have started:

• Log into a remote server with SSH.
• Know which directory and user you are using.
• Perform basic file operations.
• Keep a session alive with tmux.
• Check service status and basic logs.
• Use find, du, and port forwarding for common problems.

Then branch by need:

• Want to learn Git workflows: read Git Beginner Quick Start Notes.
• Want to learn Docker: read Docker Installation And Basic Configuration.
• Mainly configuring Linux on Windows: read WSL Usage Guide.
• Want to run Notebook remotely: read Jupyter Remote Server Connection Guide.

Five Final Suggestions For Beginners

• Before every modifying command, check whoami, pwd, and ls.
• Avoid using root for everyday development on remote machines.
• If you are unsure why a service did not start, check systemctl and logs before reinstalling.
• Put long-running tasks in tmux.
• For path, permission, process, and port problems, check the current state first instead of guessing.