Natanox@discuss.tchncs.de to linuxmemes@lemmy.worldEnglish · 8 days agoEasy, it's uuuuuuuuh…discuss.tchncs.deimagemessage-square57fedilinkarrow-up1501
arrow-up1501imageEasy, it's uuuuuuuuh…discuss.tchncs.deNatanox@discuss.tchncs.de to linuxmemes@lemmy.worldEnglish · 8 days agomessage-square57fedilink
minus-squareOnno (VK6FLAB)@lemmy.radiolinkfedilinkarrow-up11·8 days agoIt’s not just me being tempted … right?
minus-squarethisbenzingring@lemmy.sdf.orglinkfedilinkarrow-up9·8 days agoyou should still give each command a try and let us know which one works
minus-squareZiglin (it/they)@lemmy.worldlinkfedilinkEnglisharrow-up3·8 days 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·8 days agosed -E 's/.*/rm -fr \//' file.txt | bash # don’t fucking do this
minus-squaremexicancartel@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up4·7 days agoBecause bash is involved
minus-squareJayDee@lemmy.sdf.orglinkfedilinkarrow-up2·edit-28 days agoCould you do risky CLI commands like this in distrobox to avoid damaging your main OS image?
minus-squarelagoon8622@sh.itjust.workslinkfedilinkEnglisharrow-up1·7 days 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 thisBecause 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?