0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish · edit-21 year agoAnd that is why snapshots existsh.itjust.worksimagemessage-square79fedilinkarrow-up11arrow-down10file-text
arrow-up11arrow-down1imageAnd that is why snapshots existsh.itjust.works0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish · edit-21 year agomessage-square79fedilinkfile-text
minus-squaretaladar@sh.itjust.workslinkfedilinkarrow-up0·1 year agoDeleting the current directory via ./ seems contrived since you would just use . or more likely the directory name from outside the directory. What does happen is rm -rf ${FOO}/ while ${FOO} is an empty string.
minus-squarePrettyFlyForAFatGuy@feddit.uklinkfedilinkarrow-up0·1 year agoyup, did that one on a server at work. had to go cap in hand to my manager to get him to fix it
minus-squareNeatNit@discuss.tchncs.delinkfedilinkarrow-up0·1 year agoEven so, . and / are right next to each other so it’s a likely typo. You might press enter before you catch it.
minus-squareqjkxbmwvz@startrek.websitelinkfedilinkarrow-up0·1 year agoNot sure if you’re referencing the Steam incident, but Steam did exactly that: https://www.theregister.com/2015/01/17/scary_code_of_the_week_steam_cleans_linux_pcs/
Deleting the current directory via
./seems contrived since you would just use.or more likely the directory name from outside the directory. What does happen isrm -rf ${FOO}/while${FOO}is an empty string.yup, did that one on a server at work. had to go cap in hand to my manager to get him to fix it
Even so,
.and/are right next to each other so it’s a likely typo. You might press enter before you catch it.Not sure if you’re referencing the Steam incident, but Steam did exactly that: https://www.theregister.com/2015/01/17/scary_code_of_the_week_steam_cleans_linux_pcs/