Pantherina@feddit.de to linuxmemes@lemmy.world · 11 months agolol sudo rm -rf /feddit.deimagemessage-square126fedilinkarrow-up11.32Karrow-down122
arrow-up11.3Karrow-down1imagelol sudo rm -rf /feddit.dePantherina@feddit.de to linuxmemes@lemmy.world · 11 months agomessage-square126fedilink
minus-squareBonehead@kbin.sociallinkfedilinkarrow-up19·11 months agoAnd that’s why every rm command should start life as an ls command and then change the command and options while not touching the target directory. Takes a little longer, but saves so much hassle when you do fuck up.
minus-squareNaibofTabr@infosec.publinkfedilinkEnglisharrow-up8·11 months agoThis is the best advice in the whole thread. Check what you’re doing before you do it.
minus-squarenaonintendois@programming.devlinkfedilinkarrow-up5·11 months agoRm was updated to actually log a warning in the -rf / cases, so that’s less likely to happen anymore. Still not a bad habit to use ls though
minus-squareredcalcium@lemmy.institutelinkfedilinkarrow-up2·11 months agonot if you use /*. gp was totally screwed with their typo.
And that’s why every rm command should start life as an ls command and then change the command and options while not touching the target directory. Takes a little longer, but saves so much hassle when you do fuck up.
This is the best advice in the whole thread.
Check what you’re doing before you do it.
Rm was updated to actually log a warning in the
-rf /cases, so that’s less likely to happen anymore. Still not a bad habit to use ls though/* still works I think
not if you use
/*. gp was totally screwed with their typo.