Natanox@discuss.tchncs.de to linuxmemes@lemmy.worldEnglish · 2 months agoEasy, it's uuuuuuuuh…discuss.tchncs.deimagemessage-square58fedilinkarrow-up1513arrow-down14
arrow-up1509arrow-down1imageEasy, it's uuuuuuuuh…discuss.tchncs.deNatanox@discuss.tchncs.de to linuxmemes@lemmy.worldEnglish · 2 months agomessage-square58fedilink
minus-squareOnno (VK6FLAB)@lemmy.radiolinkfedilinkarrow-up11·2 months agoIt’s not just me being tempted … right?
minus-squarethisbenzingring@lemmy.sdf.orglinkfedilinkarrow-up10·2 months agoyou should still give each command a try and let us know which one works
minus-squareZiglin (it/they)@lemmy.worldlinkfedilinkEnglisharrow-up3·2 months agoIt’s sed with only a -E option that shouldn’t be dangerous since whatever the output nothing is done with it.
minus-squarelars@lemmy.sdf.orglinkfedilinkarrow-up2·2 months agosed -E 's/.*/rm -fr \//' file.txt | bash # don’t fucking do this
minus-squaremexicancartel@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up4·2 months agoBecause bash is involved
minus-squareJayDee@lemmy.sdf.orglinkfedilinkarrow-up2·edit-22 months agoCould you do risky CLI commands like this in distrobox to avoid damaging your main OS image?
minus-squarelagoon8622@sh.itjust.workslinkfedilinkEnglisharrow-up1·2 months agoDoesn’t Distrobox expose (parts of) the real filesystem though?
It’s not just me being tempted … right?
you should still give each command a try and let us know which one works
This is what VM’s are for.
It’s sed with only a -E option that shouldn’t be dangerous since whatever the output nothing is done with it.
sed -E 's/.*/rm -fr \//' file.txt | bash # don’t fucking do this
Because bash is involved
Could you do risky CLI commands like this in distrobox to avoid damaging your main OS image?
Doesn’t Distrobox expose (parts of) the real filesystem though?