What is a server?
A server has no screen, no keyboard and no mystery: it is a computer like any other, with the job of answering the others. We'll look under the hood and read the output of two commands to prove it.
- Course
- Tutorial 2 of 35
- Time
- 15 min to read
- Tested with
- Commands: tested on Debian 13.7 (trixie)
What you will be able to do
- Explain that a server is a role, not a type of machine.
- Say why most servers run Linux.
- Read the output of two simple commands.
- Describe the exchange between a client and a server.
Before you start: Why build your own server?.
Contents

When people say "my site is on a server", you picture a big blinking cabinet. What is a server, really? A role: the one a computer plays when it answers requests from other computers. Let\'s see what that changes, down to reading a real machine\'s reply. If you\'re still wondering whether to build one, read Why build your own server? first.
A server is a role
A server is a computer with a job: it waits for requests and answers them. It\'s not a special kind of machine, it\'s the work a machine does. Think of a waiter: taking orders and bringing dishes is the job, whoever does it. In the same way, a computer becomes a server when it starts serving the others.
Your old laptop can play that role, and so can a huge machine in a data center (a giant hall full of servers). Only the role counts. But how do you talk to a machine tucked away in a corner?
A computer with no screen or keyboard
Most of the time, a server is an ordinary computer with the screen, keyboard and mouse taken away. It sits in a corner and you talk to it from afar. So the machine itself has no windows to click. You send it text over the internet or your home network, and it answers with text.
That\'s plainer than a desktop full of icons, but faster to control from afar. You still need a system that runs entirely on text, and that\'s where Linux comes in.
Why Linux
An operating system is the main program of a computer, the one that makes all the others work. Linux is one, like Windows or macOS. Most servers use it because it is free, light and built to run for months without a restart. It comes in several flavors called distributions. This course uses Debian, known for being stable.
That leaves a place to type the text: the terminal.
The terminal and the command
The terminal is a window where you type instructions instead of clicking. Each instruction is called a command. Picture a service counter: you slide a note with your request under the glass, and the clerk slides back a note with the answer. The terminal is that counter, and the command is the note you slide.
In practice, you type a command, press Enter, and the machine answers with text. Many commands, especially those that change something, say nothing when all goes well. That surprises most people at first. Two commands are enough to see a terminal for real.
Two commands to see for yourself
Here are the two commands, in order:
cat /etc/os-releaseshows the name of the distribution.uptimeshows how long the machine has been running.
They change nothing: they only display information.
No need to type them now. The "On the server" blocks below show what a server answers, and reading is enough. Connecting to a real server is covered in What is SSH?. On your own computer, these commands would answer with your own values.
In the first one, cat shows the content of a file, here /etc/os-release, which names the distribution.
cat /etc/os-releasePRETTY_NAME="Debian GNU/Linux 13 (trixie)"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.7
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"Two lines are enough: NAME gives the name of the distribution, and VERSION gives its number and nickname (13, trixie). The others repeat the same thing or give help links.
The second, uptime, says how long the machine has run without interruption.
uptime 22:34:05 up 77 days, 10:17, 0 users, load average: 2.84, 2.42, 2.41Here, 77 days without a restart: that\'s the whole point of a server. The numbers after load average measure how busy the machine is. The lower they are, the calmer it is.
Client and server
These two commands form an exchange: a request goes out, an answer comes back. The two roles answer each other:
- The client is the one that asks.
- The server is the one that answers.
The same computer can be a client in one exchange and a server in another. When you open a web page, your browser is the client: it sends a request, and the site's server receives it and sends the page back.
This back and forth repeats thousands of times a day, without you seeing it. To talk to a remote server, you use SSH: a protected connection where nobody can read your commands in transit (see What is SSH?). But what does a server do between two requests?
What a server does all day
A server runs services: programs that wait for one specific kind of request and answer it. It waits, answers, then waits again. Here are the most common:
- a website service sends pages to browsers;
- a file service stores and returns your documents and photos;
- a backup service receives copies of your data, often at night;
- a mail service receives and sends messages.
One machine can run several at once, so a single small server can do a lot of jobs.
What comes next
You now know that a server is a role, that you control it with text, and that it serves clients. What\'s left is where to get one. The next article compares VPS or dedicated server, the two ways to rent a machine that is ready to go.