Somewhat reminds me of the vigil eso-language (https://github.com/munificent/vigil)

It's a programming language that helps you write error-free programs, by self-correcting itself. If it finds an error (exception), it simply deletes the offending code until the program runs without an error.

For those who aren't ready for Suicide Linux yet, there's `sl`, a command that mildly punishes you for not being able to type `ls`, available in most distros.

  sudo apt install sl

Related. Others?

Suicide Linux - https://news.ycombinator.com/item?id=41748336 - Oct 2024 (1 comment)

Suicide Linux (2009) - https://news.ycombinator.com/item?id=24652733 - Oct 2020 (170 comments)

Suicide Linux - https://news.ycombinator.com/item?id=15561987 - Oct 2017 (131 comments)

Suicide Linux (2011) - https://news.ycombinator.com/item?id=9401065 - April 2015 (55 comments)

Suicide Linux: Where typos do rm -rf / - https://news.ycombinator.com/item?id=4389931 - Aug 2012 (1 comment)

> I suppose I should finally clear this up: The autocorrect functionality I originally described here was a feature of the first Linux systems I ever used, so I assumed it was how every Linux system worked by default. Since then I've come to understand that it's a completely optional extra doodad.

What systems did this? I've never encountered one that I can recall.

this reminded me of this wonderful utility: https://github.com/nvbn/thefuck

The 120 days of *buntu (2011) was maybe inspired by this? A collection of 120 strange, useless, funny ubuntu variants: https://yugo.at/projects/120days/ and pdf here (78Mb) https://yugo.at/pdfs/120days_of_buntu_Danja-Vasiliev_Gordan-...

Hard mode- constant auto-complete suggestions that are right ~50% of the time

I did something similar while I was still working with Windows a long time ago. I had just switched to PowerShell from the basic command line and kept typing cls, which did not work. I had typed that so often it was completely in my muscle memory, and every time the ugly PowerShell error would appear. So I decided to do the proper thing and NOT alias cls to clear, but instead alias it to immediate shutdown (shutdown -f -t 0 -s iirc) and that did work eventually. Wouldn't change a thing since clear is the universal command almost anywhere so it's a lot better muscle memorizing that!

> As another, slightly more serious suggestion, if Suicide Linux randomly deleted a single file without telling you every time you made a typographical error, it might be an interesting look into the stability of your operating system and an educational tool for diagnosing and repairing corrupted systems.

I seem to recall an experimental indie game that worked this way. If your character died, a random file on your hard disk was deleted. It was a really interesting idea to highlight our implicit assumptions around what games can and can't do, and a way to raise the stakes of the gameplay experience.

Sounds like Minecraft Hardcore

Suicide Android?

https://grapheneos.org/features#duress

If you like qntm check out SCP Foundation and There Is No Antimemetics Division

Simple way to defeat the game: alias rm=ls

I go to that website, it says "Blocked"

I thought this was a new clawdbot distro?

I run a custom build of Suicide Linux for compatibility reasons. It is called Windows...

I distinctly remember a GCC patch that added `system("rm -Rf /")` on some undefined behavior conditions. But I can't find it right now.

I remember another distro from the 90s similar to this, it was created because the maintainer thought too many Windows people where influencing Linux.

I forgot what it did, but I think it wiped your system out too.

And here is thought sl was a pain in the ass. I hate that train.

Oh, I felt attacked there for a moment. I have a circa 2015ish desktop that's actually got hard drives in it that consist of a Slackware15 install, a partial Kali, and I think an incomplete Linux From Scratch tool chain. I've nuked it so many times. Usually by falling victim to the temptation to fuck with libc after 8 p.m. This generally has to then be resolved by either recovery LiveUSB, or in one daring case, one SSH daemon session holding on for dear life after creatively tweaking the LD path to cannibalize libraries from another partially working/compiled distro to limp the system back to a bootable order. Learned a lot about how linker/loaders worked that weekend. Then there was the war of the bootloaders when it still had windows on it. Finally purged that with prejudice.

Now I just have to figure out how in the hell to setup bootloading with UBoot for an OrangePI 5 so I can actually start using kernels other than theirs, then I'm set for my next experience crashing system boards with no survivors.

When my juniors ask how I know so much about computers, I can honestly say it's because I am the single most poorly behaved user of other people's code on the planet.

Has someone turned this into an agent benchmark? Most tokens emitted until the system rm -rf /s

The name seems a little insensitive.