• celeste@feddit.org
    link
    fedilink
    English
    arrow-up
    10
    ·
    2 days ago

    Look at those eyes! They yearn foe destruction! Also have you tried this in macOS yet?

    • Aganim@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      2 days ago

      Breaking MacOS is easy, if the fork bomb doesn’t work just create a function which recursively writes files until the disk is full. Unless they fixed it in the past 5 years, at that point even when the OS is set to delete files directly, it will still fail to delete anything. I couldn’t even remove anything with sudo rm -f, that just triggered a ‘not enough space to remove file’ error message.

      Found that out the hard way when a program borked itself and filled the entire drive with log files until there was not even a single byte left. Fortunately I had a very small file in the bin, clearing that still worked and those few bytes were enough to be able to perform file deletes again. Never bothered to find out why MacOS behaved that way as I was able to ditch that OS entirely not long after, but perhaps somebody else knows.

      • mic_check_one_two@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        4
        ·
        2 days ago

        Yeah, the “disk too full to delete” thing is still a problem on MacOS. Usually you can solve it by booting into safe mode, because that has fewer startup processes. That usually gives you enough wiggle room to clear your trash can and go from there. But yeah, the worst case scenario basically requires a drive reformat.