I have an M1 MacBook Air. I use UTM to run a Debian 11 virtual machine.

After the initial setup, updating and upgrading, installing Firefox and a few small programs, (I almost called them apps, d'oh), the Debian.utm file size was about 6GB. Now, less than a month later, it's almost 9GB.

The VM size increases after each use. I haven't downloaded or installed anything close to 3GB worth. I have downloaded files, then put them into the trash and emptied the trash, could the trash not be emptying properly?

I have run ncdu, but nothing stands out. When I drill down into /usr and into each large folder, no sub folder is larger than a few 100MB. I can't see any big files lurking.

I've googled using many search terms, but I can't get past results that are about how to increase the size of a VM that is running out of room.

Thanks very much for reading this, any ideas?

I use these right now on Debian:

ncdu

ncdu (NCurses Disk Usage): A disk usage analyzer with an ncurses interface, providing a fast and easy-to-use overview of disk space utilization. Ideal for identifying large directories and files in a user-friendly terminal interface.

duf

duf (Disk Usage/Free): A modern disk usage/free utility with a beautiful interface written in Go. It provides a quick and easy way to check disk usage across various file systems with color-coded output.

tldr

tldr (Too Long; Didn't Read): Simplified and community-driven man pages. Provides practical examples for commands, making it easier to understand and use without wading through lengthy and detailed man pages.

nala

nala (Next-Generation APT Frontend): A modern frontend for the APT package manager, designed to provide a more readable and user-friendly output for package management tasks.

Speedtest-cli

Speedtest-cli: A command-line interface for testing internet bandwidth using speedtest.net. Allows you to quickly check your upload and download speeds directly from the terminal.

htop

htop: An interactive process viewer for Unix systems. It provides a real-time, color-coded display of system processes, making it easier to monitor and manage system resources.

powertop

powertop: A tool for diagnosing issues with power consumption and power management on Linux systems. It provides detailed information on power usage by various system components and applications.

thinkfan

thinkfan: A simple fan control program for ThinkPads. It helps manage the system's fan speed to balance cooling and noise levels based on the temperature sensors.

tlp

tlp (Linux Advanced Power Management): A power management tool for Linux. It provides various configurations and options to optimize battery life on laptops without requiring manual tweaks.

flatpak

Flatpak: A system for building, distributing, and running sandboxed desktop applications on Linux. It provides a universal app distribution system that works across various Linux distributions.

neofetch

Neofetch: A command-line system information tool written in bash. It displays an aesthetically pleasing summary of system information alongside your terminal prompt.

iftop

iftop: A real-time console-based network bandwidth monitoring tool. It shows a list of network connections from/to your system and the bandwidth usage for each connection.

nano

nano: A simple, user-friendly text editor for the command line. Known for its straightforward and easy-to-use interface, making it a go-to for quick text editing tasks.

Edit
Oh wow! Thank you all for your suggestions!

I was looking around and found cheat; it's defined as a cheat that allows you to create and view interactive cheatsheets on the command line. Hopefully, someone else might find it helpful as well.

Hi all,

I’m looking for advice re making a full snapshot/backup of a running Linux system (Debian).

In an ideal world, should an issue occur, I would like to be able to load a live USB with the backup, boot and write from that.

Timeshift seems to be an option but I’m wondering how the above would work in my case. A few questions.

1. My disk is fully encrypted with LUKS. Would this pose a problem?
2. I would like to write my backups to a veracrypt container. Would this pose any issue? I’m not sure how I would boot from a live USB in this case I could not decrypt the USB.

Essentially I’d like a step-by-step guide to backing up my full system (including all files in home) in such a way that I can easily roll back should the worst happen. Do any of you know of such a guide or can perhaps offer some help?

Recently, I upgraded my PC to Debian 12 and chose KDE as my Desktop Environment. For this fresh installation, I decided to maintain only the core packages managed by "apt" and started using Flatpak for my apps.

Some Flatpak apps perform flawlessly out of the box, such as LibreOffice and QGIS. They adjust the language to my localization and adopt the theming from my system effortlessly. However, others like Obsidian and Zotero require manual adjustment of settings by modifying the configuration files.

I understand that Flatpak applications are sandboxed, so I initially expected them not to recognize my system configuration files. However, I am puzzled as to why some apps do recognize them while others don't. I have attempted to read some documentation on Flatpak itself, and if I understand correctly, Flatpak has the capability to read from system configuration files. However, I haven't fully grasped how it accomplishes this (is there anything to do with portals?) and why it only applies to certain packages.

Introduction

I wanna say that I made several corrections, additions, and improvements just because I love you guys way more than I love the people at Reddit

• Please note that I'm merely a dedicated Linux user, I'm speaking from that point of view. I'm not a developer and not a programmer. These are just my opinions of 10+ years using Linux

• These are just some commentaries from a dude who happen to love the concept of STABILITY in general (autism represent) and would like to discuss how it works when it comes to Linux distributions. This is all based on my use-cases and on what I think is common sense. I have no knowledge of how open-source projects really work, and make no claims regarding how they should work.

• Only distributions that claim to be stable are under my scope. So Arch and Debian Unstable are clearly out the scope, but Slackware, CentOS, Debian Buster, and MX-Linux are clearly under the scope.

• All considerations are void if the malfunctioning is SOLELY a product of hardware, extremely rare conditions or your own lack of knowledge.

• Except when otherwise noted, non-compliance means the distribution is deemed not stable.

1 Deal Breakers

After a correct installation by the user on hardware that is expressly supported by the developers, a stable distribution should, in the period of 1 year (counted from the first boot):

1. Remains bootable, manageable and fully accessible.
2. Work with almost no maintenance or intervention (updates excluded)
3. Present no decrease in performance
4. Freeze at most once every two weeks
5. Have no package issue that cannot be solved by a simple command from its own package manager

2 Major Issues

Because of the complex nature of major issues, I'm not going to establish any criteria about them. Both stable and unstable distributions have critical problems that cannot have a fixed time-frame.

3 Minor Issues/Bugs/Annoyances/etc

Small issues are the ones that do not impede the usage of the machine, but provoke significant annoyances:

Examples:

1. Window switching is not working properly
2. The mouse stops working for 3 seconds every 15 minutes
3. For some reason, the letter "c" is sending "h" on the terminal
4. My configurations are not saved after reboot
5. My configurations are not being saved at all
6. I must change video output manually every time I switch monitors
7. I must change audio output manually every time I switch monitors
8. Some essential configuration is ridiculously hard to find
9. Configurations have no undo button
10. Configurations have no reset button
11. A certain package cannot be installed
12. A certain dependence cannot be installed (dependency hell)
13. There's a ridiculously accessible keyboard shortcut that makes your keyboard change layouts all the fucking time

3.1 Places for Research

Such minor issues must be solved within 30 days, as long as the user does their part and seek some of the following resources:

1. Google
2. Official websites
3. Official forums
4. Official warnings, newsletters, etc
5. Semi-official communities
6. FAQs
7. Manuals
8. Github Issues
9. Gitlab Issues
10. Other Venues to post issues

If the minor issue is not solved in 45+ days, the distribution will be deemed not stable, regardless of the behavior of the user.

4. Conclusion

It is my opinion that, if any of the major and minor requirements are not fulfilled according to their particular rules, the distribution in question should not be deemed not Stable.