-
Notifications
You must be signed in to change notification settings - Fork 0
General Info
Warning
I am no expert. This wiki does not cover all the details of Atomic Desktops and might not be 100% accurate on all the fine details. It's meant to be an easy resource to use when getting started with my image and Fedora Atomic Desktops in general.
It's a modified ublue image for Fedora Atomic Desktops.
It's essentially a Linux Distribution that has a read-only root filesystem. This basically means you can't modify the system files*.
Here's a nice video explanation: https://youtube.com/watch?v=9hiPFEUoUyI
Tip
Usually Distros will actually let the /etc directory writable (like fedora atomic does) because sometimes you have to write stuff in there (udev rules usually).
It's a method of distributing software used in tools such as Docker and Podman. This same sort of system is used by Fedora Atomic Desktops.
For our purposes here an image is basically a Fedora Linux Root System that can we swapped out with another. This basically lets you make drastic changes without the fear of breaking your system. For example, changing from Gnome to KDE Plasma without reinstalling your OS and keeping all your user files.
All of these names essentially mean the same thing. "Image Based OS" is a bit more specific but for our case it's the same as all the others. It's just another way of doing an Immutable Distro.
This is the package manager used by Fedora Atomic Desktops. The apps installed as a native package.
A way of installing sandboxed graphical apps on Linux without modification to system files. This is the main way graphical apps are meant to be installed on BlueCat. More info here.
A command line package manager usually used on MacOS but also available for Linux. It installs packages without modifying the root file system. It's the main way CLI apps are meant to be installed on BlueCat. See more info here.