That or I didn't fully read the output of it when I did.
Good to know I'm not the only one that goes through spamming those commands. Same goes for apt sometimes as well.
Speaking of apt and auto updating stuff. Ubuntu has been pushing "snaps" instead of the old "apt" way of doing things the past few years. It works I guess but it takes up a bunch more space and they don't auto clean up. My hdd space is low and whenever I'm all of sudden completely out of space, it's because a snap updated and now I have dead versions floating around.
I have this script I mostly took from Stack Overflow that cleans them out:
#!/bin/bash
# Removes old revisions of snaps
# CLOSE ALL SNAPS BEFORE RUNNING THIS
set -eu
snap list --all | awk '/disabled/{print $1, $3}' |
while read snapname revision; do
snap remove "$snapname" --revision="$revision"
done
Ex here's my current "df -h"
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 792M 28M 765M 4% /run
/dev/sda1 219G 205G 3.7G 99% /
tmpfs 3.9G 8.0M 3.9G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/loop1 9.0M 9.0M 0 100% /snap/canonical-livepatch/146
/dev/loop0 142M 142M 0 100% /snap/skype/214
/dev/loop2 92M 92M 0 100% /snap/gtk-common-themes/1535
/dev/loop4 56M 56M 0 100% /snap/core18/2344
/dev/loop3 114M 114M 0 100% /snap/core/13308
/dev/loop6 56M 56M 0 100% /snap/core18/2409
/dev/loop10 128K 128K 0 100% /snap/acrordrdc/62
/dev/loop9 296M 296M 0 100% /snap/vlc/2344
/dev/loop11 566M 566M 0 100% /snap/pycharm-community/286
/dev/loop12 347M 347M 0 100% /snap/wine-platform-runtime/309
/dev/loop8 82M 82M 0 100% /snap/gtk-common-themes/1534
/dev/loop13 304M 304M 0 100% /snap/wine-platform-5-stable/18
/dev/loop14 566M 566M 0 100% /snap/pycharm-community/281
/dev/loop15 323M 323M 0 100% /snap/wine-platform-6-stable/19
/dev/loop17 9.0M 9.0M 0 100% /snap/canonical-livepatch/138
/dev/loop18 878M 878M 0 100% /snap/intellij-idea-community/366
/dev/loop19 37M 37M 0 100% /snap/heroku/4092
/dev/loop20 128K 128K 0 100% /snap/bare/5
/dev/loop21 878M 878M 0 100% /snap/intellij-idea-community/372
/dev/loop22 100M 100M 0 100% /snap/wine-platform-3-stable/14
/dev/loop23 87M 87M 0 100% /snap/simplescreenrecorder/1
/dev/loop24 165M 165M 0 100% /snap/gnome-3-28-1804/161
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 792M 140K 792M 1% /run/user/1000
/dev/loop25 114M 114M 0 100% /snap/core/13425
/dev/loop16 142M 142M 0 100% /snap/skype/217
/dev/loop7 347M 347M 0 100% /snap/wine-platform-runtime/310
After running script:
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 792M 28M 765M 4% /run
/dev/sda1 219G 202G 6.0G 98% /
tmpfs 3.9G 8.0M 3.9G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/loop1 9.0M 9.0M 0 100% /snap/canonical-livepatch/146
/dev/loop2 92M 92M 0 100% /snap/gtk-common-themes/1535
/dev/loop6 56M 56M 0 100% /snap/core18/2409
/dev/loop10 128K 128K 0 100% /snap/acrordrdc/62
/dev/loop9 296M 296M 0 100% /snap/vlc/2344
/dev/loop11 566M 566M 0 100% /snap/pycharm-community/286
/dev/loop13 304M 304M 0 100% /snap/wine-platform-5-stable/18
/dev/loop15 323M 323M 0 100% /snap/wine-platform-6-stable/19
/dev/loop19 37M 37M 0 100% /snap/heroku/4092
/dev/loop20 128K 128K 0 100% /snap/bare/5
/dev/loop21 878M 878M 0 100% /snap/intellij-idea-community/372
/dev/loop22 100M 100M 0 100% /snap/wine-platform-3-stable/14
/dev/loop23 87M 87M 0 100% /snap/simplescreenrecorder/1
/dev/loop24 165M 165M 0 100% /snap/gnome-3-28-1804/161
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 792M 136K 792M 1% /run/user/1000
/dev/loop25 114M 114M 0 100% /snap/core/13425
/dev/loop16 142M 142M 0 100% /snap/skype/217
/dev/loop7 347M 347M 0 100% /snap/wine-platform-runtime/310
Went from 3.7GB free to 6GB free just by clearing out old snaps that don't auto remove. Also, they clutter up the output of "df"
"I have to wonder if people will ever understand that when you mess up where things were placed you're destroying their work. Maybe not..."
I think as long as we have Agile "needs a release every sprint to show momentum" development, this is going to continue. Saving exactly where things were is probably low priority and therefore kicked down the road to the backlog. Instead of getting a new version every few months that could disrupt you, now you get one ever two weeks.