Referring to raspberry-and-volumio-979-not-responding-t4618.html
Was there something fundamentally bad about 80M?
Because the current latest commit for dynswap.sh (d2c83bf) says fallocate -l 512M.
Problem is, I ran out of memory again when I updated Volumio. Couldn’t even check any logs for messages,
because Volumio couldn’t write any, the disk being out of space.
I went in, disabled swap and deleted the swapfile, otherwise nano would not have disk space to save
the edit to make dynswap.sh say fallocate -l 80M.
So that’s why I’m asking, was there a problem with that amount or what, because this broke for me.