I freed 30GB using Filelight
-
dustYes, it's
duin Rust + more.Isn't that a wayland notification daemon already?
Edit: no, that's dunst.
Btw, how do you do the background color thing?
-
Isn't that a wayland notification daemon already?
Edit: no, that's dunst.
Btw, how do you do the background color thing?
I was confused what you meant by background colour thing so I went to
dustdocs haha.Now I got you. It's a codeblock so it shows in monospace font. Look up .md formatting for tips.
In this case its a word between backticks `
-
I was confused what you meant by background colour thing so I went to
dustdocs haha.Now I got you. It's a codeblock so it shows in monospace font. Look up .md formatting for tips.
In this case its a word between backticks `
Ah, right, it's the
inline code. Mindslip. Thanks! -
Personally I'm loving diskonaut. "Graphical" representation but at, ahem, terminal velocity.
Jesus, that rustup folder is HUGE
-
Personally I'm loving diskonaut. "Graphical" representation but at, ahem, terminal velocity.
-
flatpak install flathub org.kde.filelight
-
https://github.com/imsnif/diskonaut
No package for my distro, I "installed" an AppImage with AM (which is also how I discovered it)
-
I freed 50gb by running 'docker system prune'...
I'm new to docker and all of my shit stopped working recently. Just wouldn't load. Took about a half hour to find out that old images were taking up about 63GB on my 100GB boot partition, resulting in it being completely full.
I added the command to prune 3 month old images to my update scripts.
-
[moonpie@osiris ~]$ du -h $(which filelight) 316K /usr/bin/filelightK = kilobytes.
[moonpie@osiris ~]$ pacman -Ql filelight | awk '{print $2}' | xargs du | awk '{print $1}' | paste -sd+ | bc 45347740(45347740 bytes is 43.247 megabytes).
KDE packages have many dependencies, which cause the packages themselves to be extremely tiny. By sharing a ton of code via libraries, they save a lot of space.
-
And that's all, I'm happy since I was out of space.
I normally use
rmfor that. Orwipefsif I'm feeling particularly spicy. -
I normally use
rmfor that. Orwipefsif I'm feeling particularly spicy.Filelight is about finding the folders you don't use that take a lot of space. Basically an easier way to look into which folder takes up what.
-
Lol I had no idea it relied on so much. Its just built into KDE. Really great app overall.
Basically all KDE apps have the same dependency set. So install one and the next ones will only install the app most likely. On KDE itself you'd already have these.
-
Filelight is about finding the folders you don't use that take a lot of space. Basically an easier way to look into which folder takes up what.
Wooosh
-
Jesus, that rustup folder is HUGE
-
[moonpie@osiris ~]$ du -h $(which filelight) 316K /usr/bin/filelightK = kilobytes.
[moonpie@osiris ~]$ pacman -Ql filelight | awk '{print $2}' | xargs du | awk '{print $1}' | paste -sd+ | bc 45347740(45347740 bytes is 43.247 megabytes).
KDE packages have many dependencies, which cause the packages themselves to be extremely tiny. By sharing a ton of code via libraries, they save a lot of space.
-
And that's all, I'm happy since I was out of space.
Personally I'm a huge fan of dust
-
I'm new to docker and all of my shit stopped working recently. Just wouldn't load. Took about a half hour to find out that old images were taking up about 63GB on my 100GB boot partition, resulting in it being completely full.
I added the command to prune 3 month old images to my update scripts.
Yeah, it's really not called out in the docs. I found out the same way.
-
Isn't that a wayland notification daemon already?
Edit: no, that's dunst.
Btw, how do you do the background color thing?
Now someone needs to do a rewrite of dunst in rust called runst to make the confusion complete.
-
(This is a joke donât do this or youâll ruin your computer)
You can run it without causing any problems if you add the
--no-preserve-rootflag as well of course -
Fclones is a great tool, but it's for finding duplicate files and replacing them with sym-/hard-/reflinks.
I recommend using the --cache option to make subsequent runs extremely quick.
--cache option
I will check this out!
