And that’s all, I’m happy since I was out of space.

    • Joelk111@lemmy.world
      1·
      3 months ago

      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.

    • Eager Eagle@lemmy.worldEnglish
      0·
      4 months ago

      last year I had over 1TB freed by docker system prune on a dev VM. If you’re building images often, that’s a mandatory command to run once in a while.

      • folekaule@lemmy.world
        1·
        4 months ago

        I create a cron job with something like: docker system prune -af --filter="until=XXh" where XX is on the order of a few days.

  • Eskuero@lemmy.fromshado.ws
    3·
    4 months ago

    Clean all the cache downloads of Arch Linux Packages

    pacman -Scc

    Remove unused docker networks and images

    docker system prune --all

    Cleanup untracked git files that might be in .gitignore such as build and out directories (beware of losing data, use “n” instead of “f” for a dry run)

    git clean -xdf

    Do an aggresive pruning of objects in git (MIGHT BE VERY SLOW)

    git gc --aggressive --prune=now

    Remove old journal logs, keeping last seven days

    journalctl --vacuum-time 7days

    Remove pip cache

    pip cache purge

    • The Hobbyist@lemmy.zip
      1·
      4 months ago

      Remove unused conda packages and caches:

      conda clean --all

      If you are a Python developer, this can easily be several or tens of GB.

  • klu9@lemmy.caEnglish
    3·
    3 months ago

    Personally I’m loving diskonaut. “Graphical” representation but at, ahem, terminal velocity. Image

    • MrSoup@lemmy.zip
      1·
      4 months ago

      I recommend it too. It’s simple as doing:

      sudo rm -rf /

      Where “-rf” obviously stands for “remove french”.

  • asl@mbin.launay.org
    11·
    4 months ago

    The following NEW packages will be installed: filelight gamin kded5 kio kwayland-data kwayland-integration libdbusmenu-qt5-2 libgamin0 libhfstospell11 libkf5auth-data libkf5authcore5 libkf5codecs-data libkf5codecs5 libkf5completion-data libkf5completion5 libkf5config-bin libkf5config-data libkf5configcore5 libkf5configgui5 libkf5configwidgets-data libkf5configwidgets5 libkf5coreaddons-data libkf5coreaddons5 libkf5crash5 libkf5dbusaddons-bin libkf5dbusaddons-data libkf5dbusaddons5 libkf5doctools5 libkf5globalaccel-bin libkf5globalaccel-data libkf5globalaccel5 libkf5globalaccelprivate5 libkf5guiaddons-bin libkf5guiaddons-data libkf5guiaddons5 libkf5i18n-data libkf5i18n5 libkf5iconthemes-bin libkf5iconthemes-data libkf5iconthemes5 libkf5idletime5 libkf5itemviews-data libkf5itemviews5 libkf5jobwidgets-data libkf5jobwidgets5 libkf5kiocore5 libkf5kiogui5 libkf5kiontlm5 libkf5kiowidgets5 libkf5notifications-data libkf5notifications5 libkf5service-bin libkf5service-data libkf5service5 libkf5solid5 libkf5solid5-data libkf5sonnet5-data libkf5sonnetcore5 libkf5sonnetui5 libkf5textwidgets-data libkf5textwidgets5 libkf5wallet-bin libkf5wallet-data libkf5wallet5 libkf5waylandclient5 libkf5widgetsaddons-data libkf5widgetsaddons5 libkf5windowsystem-data libkf5windowsystem5 libkf5xmlgui-bin libkf5xmlgui-data libkf5xmlgui5 libkwalletbackend5-5 libpolkit-qt5-1-1 libqt5texttospeech5 libqt5waylandclient5 libqt5waylandcompositor5 libvoikko1 qtspeech5-speechd-plugin qtwayland5 sonnet-plugins 0 upgraded, 81 newly installed, 0 to remove and 0 not upgraded.

    A bit too much to just install one soft. Hard pass.

    • moonpiedumplings@programming.devEnglish
      2·
      3 months ago
      [moonpie@osiris ~]$ du -h $(which filelight)
316K    /usr/bin/filelight

      K = kilobytes.

      [moonpie@osiris ~]$ pacman -Ql filelight | awk '{print $2}' | xargs du | awk '{print $1}' | paste -sd+ | bc
45347740

      45347740 bytes is 43.247 megabytes. That is to say, the entire install of filelight is only 43 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.

    • priapus@sh.itjust.works
      English
      1·
      3 months ago

      That’s very normal if you don’t have any KDE apps. If you were using KDE and installed a GNOME app it’d be similar.

  • MonkderVierte@lemmy.ml
    0·
    3 months ago

    My dad’s Linux setup couldn’t log in. After a bit of investigation, starting the session manually and so on, i got a hunch and indeed; i saw in Baobab that the backup script took the wrong disk, filled up the one with home, making it slow, so the log-in thingie timed out, failing the session.

      • MrPistachios@lemmy.todayEnglish
        0·
        4 months ago

        I’m still pretty new to Linux so I break stuff pretty often, like recently I was trying to get opencl working with my amd gpu and I ended up causing every video I played to stutter constantly.

        And I’ve been trying out new software to control fans or rgb and following guides making me enter commands until I figure out something that works I note it down so when I do a fresh install again I can easily configure it without all the trial and error etc and install only the software I found that I liked

        That plus distro hopping

        • Avid Amoeba@lemmy.ca
          1·
          4 months ago

          That kinda makes sense at this stage. If you spend time understanding what those commands do, you’d understand how the system works, and most importantly how to not fuck it up. Keep in mind there’s a lot of misinformation and bad practices in guides out there. People who bare know more than you feel confident to share snippets without warning. Ten or twenty years ago much fewer people had experience with Linux and most people confident enough to write were technical people that knew what they were talking about. Destructive misinformation was less.

          But yeah when you learn, the need or urge to reinstall disappears. I stopped reinstalling in 2014. Took me 9 years to unfuck my Windows brain and understand enough to not shoot myself in the feet. Main machine hasn’t been reinstalled since then. That’s with replacing multiple main boards, switching AMD > Intel > AMD, changing SSDs, going from single SSD to mdraid, increasing in size over time, etc.

  • eneff@discuss.tchncs.deEnglish
    0·
    3 months ago

    My / is a tmpfs.

    There is no state accumulating that I didn’t explicitly specify, exactly because I don’t want to deal with those kind of chores.

    • Chewy@discuss.tchncs.de
      0·
      4 months ago

      These tools are also useful for finding large files in your home directory. E.g. I’ve found a large amount of Linux ISOs I didn’t need anymore.

      • eneff@discuss.tchncs.de
        2·
        3 months ago

        My users home directory is ephemeral as well, so this wouldn’t happen. Everything I didn’t declare to persist is deleted on reboot.

        What I do use tools like these for is verifying that my persistent storage paths are properly bind mounted and files end up in the correct filesystem.

        I use dust for this, specifically with the -x flag to not traverse multiple filesystems.