/g/ - I shit you not, I have just accidentally rm -rf /* - Technology

Anonymous

10/27/25(Mon)12:04:51 No.107023604

File: 89da4bcb278f3ac46df622b9d(...).jpg (62 KB, 714x1000)

Anonymous 10/27/25(Mon)12:04:51 No.107023604 Archived

I shit you not, I have just accidentally rm -rf /* nuke my laptop while trying to remove all files from a directory. I realized I didn't input the dot when my vscode theme disappeared. I turned off my laptop and it won't boot.
I thought nowadays it asks you if you really wanna do this? I didn't lose anything important but FUCK

Anonymous
10/27/25(Mon)13:51:41 No.107024603

Anonymous 10/27/25(Mon)13:51:41 No.107024603

>>107023604
only gay shit like ubuntu and probably catchyos warn you

Anonymous
10/27/25(Mon)13:56:50 No.107024649

Anonymous 10/27/25(Mon)13:56:50 No.107024649

>>107023604
You can make fun of me for using a graphical file manager when I need to delete something as root, but I've never had this issue. Works on my machines.

Anonymous
10/27/25(Mon)14:03:48 No.107024700

Anonymous 10/27/25(Mon)14:03:48 No.107024700

>>107023604
Worst case there is photorec that one could run on some recovery iso, thought you'd need some external storage to recover the files into. There are probably some other methods one could use

Anonymous
10/27/25(Mon)14:06:16 No.107024729

Anonymous 10/27/25(Mon)14:06:16 No.107024729

>he doesn't have automatic btrfs snapshots

Anonymous
10/27/25(Mon)15:22:19 No.107025502

Anonymous 10/27/25(Mon)15:22:19 No.107025502

>>107023604
This happened to me because I didn't know you had to put -delete at the END of find.

>find -type f -delete -name shit.txt

Nuked my whole home directory

Anonymous
10/27/25(Mon)15:24:30 No.107025512

Anonymous 10/27/25(Mon)15:24:30 No.107025512

>>107023604
I did it on my phone twice. Termux.

Anonymous
10/27/25(Mon)15:27:12 No.107025531

Anonymous 10/27/25(Mon)15:27:12 No.107025531

>>107023604
if you are not shitting yourself over messing up as soon as you have added the -rf flags your -rf license should be revoked

Anonymous
10/27/25(Mon)15:27:13 No.107025533

Anonymous 10/27/25(Mon)15:27:13 No.107025533

>>107023604
haha OP I love froggo XD

Anonymous
10/27/25(Mon)15:28:46 No.107025542

Anonymous 10/27/25(Mon)15:28:46 No.107025542

>>107025533
did the bot break

Anonymous
10/27/25(Mon)15:44:31 No.107025644

Anonymous 10/27/25(Mon)15:44:31 No.107025644

File: 1736121660030428.png (593 KB, 850x567)

593 KB PNG

>>107023604

Anonymous
10/27/25(Mon)15:48:04 No.107025675

Anonymous 10/27/25(Mon)15:48:04 No.107025675

>>107023604
>vscode
linuk smelled the microsoft shit you're using, serves you right if you use vscode

Anonymous
10/27/25(Mon)16:46:34 No.107026226

Anonymous 10/27/25(Mon)16:46:34 No.107026226

you at least attached the right picture OP. admitting you fucked up is step 1 towards recovering from this

Anonymous
10/27/25(Mon)21:30:56 No.107028606

Anonymous 10/27/25(Mon)21:30:56 No.107028606

>>107025502
>path must precede expression

Anonymous
10/27/25(Mon)21:50:42 No.107028723

Anonymous 10/27/25(Mon)21:50:42 No.107028723

>>107024649
Never had this issue either, and I almost exclusively use terminal for shit like that. Basically never use the -f (--force) flag for rm, tho.

Anonymous
10/27/25(Mon)21:52:43 No.107028734

Anonymous 10/27/25(Mon)21:52:43 No.107028734

>>107023604
i think everyone has done this.
put this in your .bashrc

alias rm='__safe_rm'
__safe_rm() {
    local current_dir
    current_dir="$(pwd)"

    # Change this path to your actual username if needed
    if [[ "$current_dir" == "/home/user" || "$current_dir" == /home/user/* ]]; then
        echo "  rm is disabled in $current_dir"
        return 1
    fi

    command rm "$@"
}