Computer Science Knowledge Base

Userspace

7 min read

This is the good old operating system you know and love. This is where applications, your desktop, and %90 of computing is done.

Package managers

These systems are designed to help a user manage packages (applications and services that run on an OS). These are common on linux systems, but less common on windows. They give advantages over just normally just installing applications because you can manage versions, updates, and uninstalling more easliy:

There is an alternative to package managers that are essentially containerized forms of package managers:

Distro’s

Distro’s or distributions is the name given to different “flavours” of operating systems (really only applies to linux since there’s 1 version of macos and 1 version of windows). A distro is what you actually install to your computer and includes a kernel, and all the default userspace packages and configurations.

There are many different distro’s, but generally there are some groups of “similar” ones that do thing in a similar way and have similar setups. Packages can have a wide range of formats and which ones are supported is often tied to the type of distro you use

Debian

The most popular type of linux distro. Can use raw binaries or .deb files for packages. Typically uses apt as a package manager:

Arch

Considered to be the bleeding edge, and also typically the hardest learning curve. Tends to use pacman in conjunction with AUR (Arch user repository) to get it’s packages:

Fedora

Often considered the more “corporate” type of distro:

LFS (Linux from scratch)

Linux from scratch is exactly what it sounds like. You build your system from nothing and basically create “your own distro”

Processes

A running program. They are essentially enclosed processes that have a bunch of state. When a process is made it will have a PID you can use to identify the process. While each process is seperate you can technically “pipe” the contents of processes between each other, typically using STDIN and STDOUT:

Terminal/Shell

The shell is the name given to the system that lets you start and stop processes. The terminal is just the visualization of the shell that you interact with. When you start processes via clicking on a shortcut this still goes through the shell, but you likely won’t see the terminal representation.

Shells:

Terminals

Additional references

Streams

Streams is the name given to the system used to communicate with processes through the shell. There are 2 main types (and also STDERR you can look into yourself)

std

STDIN

The INput stream that the terminal and commands use

STDOUT

The OUTput stream that is what you as a user often read when a command is finished

Piping

You can PIPE the output (stdout) of one command (command1), or some text to the input (stdin) of another command (command2):

command1 | command2

This means command2 will run using the output of command1 as input

Sudo/permissions

Some folders and files are locked to “admins”, on linux you need to use the command sudo to allow access. On windows you need to use the gui prompt.

File System

This is the system that is used to keep track of your files. People use this term to refer to multiple things (including both the way things are stored, and the file structure itself), but this just simply refers to the actual process of how your files are stored.

Further on we will talk about the file system structures that are common on operating systems, and that is not about how something is stored, but where things are commonly stored (though sometimes people still just call it the file system)

File System Structure

This is the standard used to describe where you should look in a file system for certain things (i.e. installed apps, default configurations etc.)

File System Formats

This is the way in which the file system actually stores it’s data. This can impose limitations (like 4Gb file size limits for FAT32) and enable features (rolling backups/snapshots for BTRFS for some setups) depending on which you chose:

Display Server

Controls what you actually see, without this nothing will render to the screen (examples are x server and wayland). In order for a GUI to appear whatever application is running will need to run through the display server

Desktop Environments

The name given to the collection of systems that run to give a linux distribution it’s “look and feel”. This includes things like a start menu (or not), a search bar (or not), desktop icons (or not), taskbar/app dock (or not), the file explorer and many other features that make a distribution look and feel different. Note that sometimes distro’s with the same desktop environment will look different because they can often be styled with custom themes using CSS.

Window Manager

Controls the borders of GUI windows [the minimize, maximize and close buttons], as well as their positions and dimensions. These are usually part of desktop environments but you can install custom ones:

File Manager

What allows you to visually traverse your file system

Helpful reference videos

Graph View

Backlinks

  • No backlinks found