Dope i will look into it because i carry my laptop to school with me thanks !
1 Like
Install “cmatrix” in one of the Qube VMs - in a terminal:
dnf install cmatrix
and then just run
cmatrix
I’m reasonably sure it will give you massive aura 
xD
PS: not sure if thats packaged in fedora, but it is in debian xD
2 Likes
Yeah, it’s available in Fedora as well.
1 Like
Dope ! i have another question if vaults should be made as app qubes why that is ? why not stand alone qubes if they don’t share storage wouldn’t that be more private ?
Why standalone over app qube? How do you comprehend “private” in terms of Qubes and in general?
1 Like
vault is just a funky name in Qubes OS to get users started I think. From what I recall the default vault Qube just has no netvm.
Can’t believe I google “different qubes os vm types appvm templatevm standalone vm” and my own website is on place 4… but might be worth reading xD How to Create Qubes OS VMs Using the Command Line
Part of Qubes security idea is that malware can not persist in parts of the filesystem that are ephemeral (removed after shutdown). An AppVM will only persist /home across shutdowns, not the rest of the / filesystem. If malware infects /bin/something, then it is deleted after shutdown.
Standalone Qube VMs are kinda something for coding environments imho, bcs there you want to often apt-get install something (maybe). Or at least my coding VMs are standalones..
Got tired of trying to find a good link to explain this so here is ChatGPT 5.6 sol on high:
TemplateVM
A TemplateVM is the master operating-system image used by one or more AppVMs. Its purpose is to centralise software installation and updates: install Firefox or system packages once in the TemplateVM, and every AppVM based on it receives them. Changes to the TemplateVM’s root filesystem are persistent, including installed packages, system libraries and system-wide configuration. AppVM user files are not stored in the TemplateVM, and you generally should not use it for browsing or everyday work because compromising a template could affect every qube based on it.
AppVM
An AppVM is the normal qube used for everyday activities such as work, banking, personal browsing or email. It borrows its operating system and installed software from a TemplateVM, while keeping its own separate user data. Files and configuration under /home, /usr/local and /rw are persistent, so documents, browser profiles, bookmarks, extensions and most application preferences survive shutdowns. Changes to the borrowed root filesystem—typically system files and packages installed directly with dnf or apt—are not persistent and disappear when the AppVM restarts; such software should normally be installed in the TemplateVM instead. The AppVM’s Qubes settings, such as its name, networking and firewall configuration, also persist.
StandaloneVM
A StandaloneVM has its own complete operating-system filesystem and does not borrow one from a TemplateVM. Its purpose is to support situations where the whole system must be independently configurable—for example, unusual software installations, a different operating system, development environments or applications that modify system directories extensively. Both its root filesystem and its user data are persistent, so installed packages, /etc configuration, application data and files all survive shutdowns. The trade-off is that it does not automatically inherit software updates from a TemplateVM, must be updated separately and generally consumes more disk space. No other AppVMs can be based on it.
Named disposable
A named disposable is a disposable qube with a permanent, user-chosen name, such as sys-usb or a disposable sys-firewall. Its purpose is to combine a fresh internal environment on every start with stable Qubes-level configuration, making it particularly useful for service qubes, persistent device assignments and policies that need to reference a fixed qube name. Files, malware, user data and changes made inside the running qube are not persistent and are discarded when it shuts down. However, the qube’s name and external Qubes configuration—such as memory allocation, network connection, features, assigned devices and policy references—remain, allowing the same named qube to be started again with a fresh filesystem.
Unnamed disposable
An unnamed disposable, usually given an automatic name such as disp1234, is a temporary single-use qube created for a particular task—for example, opening an untrusted PDF, visiting a suspicious link, testing software or handling an untrusted USB device. It starts from the clean state defined by its disposable template and is normally automatically shut down and deleted when its initial application closes. Nothing inside it is persistent: downloaded files, browsing history, malware, configuration changes and root-filesystem changes are all discarded, and the qube itself ceases to exist after shutdown. Data survives only when it is explicitly copied to another persistent qube or, in the special “edit in disposable” workflow, saved back to the source file.
2 Likes
THERE it is xD
1 Like