kali_fornication@lemmy.world to linuxmemes@lemmy.world · 2 days agooopslemmy.worldimagemessage-square37fedilinkarrow-up1285arrow-down16
arrow-up1279arrow-down1imageoopslemmy.worldkali_fornication@lemmy.world to linuxmemes@lemmy.world · 2 days agomessage-square37fedilink
minus-squarestupidcasey@lemmy.worldlinkfedilinkarrow-up6·19 hours agoI was trying to sudo rm -rf ./ Once and missed the / so I just used rm -rf . And this was before they added --no-preserve-root as a default so it just ripped through my entire drive.
minus-squarebeegnyoshi@lemmy.ziplinkfedilinkarrow-up4·17 hours agosudo rm -rf ./ and sudo rm -rf . are, as far as I know, the same command. Did you mean that you dropped the . and ran sudo rm -rf /? Fortunately for me, this never happened to me, but I have gotten pretty close to running rm -rf ~ after mistakenly creating a directory caller ~…
minus-squarex00z@lemmy.worldlinkfedilinkEnglisharrow-up1·16 hours ago after mistakenly creating a directory caller ~… How do you even delete such a directory?
I was trying to sudo rm -rf ./ Once and missed the / so I just used rm -rf . And this was before they added --no-preserve-root as a default so it just ripped through my entire drive.
sudo rm -rf ./andsudo rm -rf .are, as far as I know, the same command. Did you mean that you dropped the . and ransudo rm -rf /?Fortunately for me, this never happened to me, but I have gotten pretty close to running
rm -rf ~after mistakenly creating a directory caller~…How do you even delete such a directory?
rmdir ./~
That makes sense.