Suicide Linux • Hacker News Board

Re: Suicide Linux

#41

Post by lloeki » Thu, Oct 26, 2017, 10:56 PM UTC

inamberclad wrote: post #31

lloeki wrote: post #30

> The reaction from the OS is actually rather underwhelming. Somehow related, a coworker at a previous place unmounted some disks on an old AIX production box. It took him a solid minute to realise he had mistakenly unmounted / due to a typo (yes it was possible) as old processes with already opened files were happily serving stuff and only new attempts at opening files were beginning to produce errors. Also, a simil…

Does that last one come from here? http://www.toodarkpark.org/computers/humor/shoot-self-in-foo...

Nope, real life occurrence. A variant includes mashing Enter on a valid rm line but on AZERTY keyboards that may mean fat fingering the nearby asterisk key.

Re: Suicide Linux

#42

Post by PascLeRasc » Thu, Oct 26, 2017, 10:57 PM UTC

Shouldn't this be more accurately called Seppuku Linux?

Re: Suicide Linux

#43

Post by Retr0spectrum » Thu, Oct 26, 2017, 11:07 PM UTC

siegelzero wrote: post #3

Reminds me of bash roulette. http://www.bash.org/?96164

That also reminds me of something similar, where a random offset in /dev/mem is clobbered. What potentially makes it more amusing is that it would probably just crash your machine, rather than completely destroy it.

Re: Suicide Linux

#44

Post by Retr0spectrum » Thu, Oct 26, 2017, 11:09 PM UTC

tekstar wrote: post #6

a less destructive version of this is to install `sl` on your linux or mac.

Tip: If you ever trigger sl by mistake, and you're in a hurry, press Ctrl+Z instead of Ctrl+C (which doesn't work).

Re: Suicide Linux

#45

Post by FeepingCreature » Thu, Oct 26, 2017, 11:12 PM UTC

legohead wrote: post #32

lloeki wrote: post #30

> The reaction from the OS is actually rather underwhelming. Somehow related, a coworker at a previous place unmounted some disks on an old AIX production box. It took him a solid minute to realise he had mistakenly unmounted / due to a typo (yes it was possible) as old processes with already opened files were happily serving stuff and only new attempts at opening files were beginning to produce errors. Also, a simil…

A friend and I were working on a codebase and he did a similar typo: rm *>o Been using "make clean" ever since.

git clean -fixd

Re: Suicide Linux

#46

Post by bmiller2 » Thu, Oct 26, 2017, 11:27 PM UTC

In all seriousness, what if it's a machine that no one should ever really be running commands on? This could be an effective, albeit naive, way to discourage undesirables in the system.

Re: Suicide Linux

#47

Post by pierrec » Thu, Oct 26, 2017, 11:32 PM UTC

Bromskloss wrote: post #23

> You know how sometimes if you mistype a filename in Bash, it corrects your spelling and runs the command anyway? What? No, what's that about?

Yeah, I'm not aware of any distro that has this setting enabled by default. It's neat that it exists, though.

Re: Suicide Linux

#48

Post by warent » Thu, Oct 26, 2017, 11:33 PM UTC

sp332 wrote: post #8

This reminds me of Vigil, "the eternal morally vigilant programming language" https://github.com/munificent/vigil

First I've heard of this. Finally a keyword to beseech my needs!

Re: Suicide Linux

#49

Post by vacri » Thu, Oct 26, 2017, 11:33 PM UTC

noir_lord wrote: post #21

isostatic wrote: post #13

Earlier quoted context omitted.

I never type sl, but often type "gerp". I have an alias though.

for me it's "date" and "data" since I type both of those quite a lot (I don't have a clock on my desktop, I just use date when I need to know the time, I find a clock distracting because I get that "well it's 27 minutes til that meeting, never getting in the the zone in that time, better check HN" thing).

I frequently try to "isntall" things...

Re: Suicide Linux

#50

Post by kbenson » Thu, Oct 26, 2017, 11:40 PM UTC

Just have to mention, since I recognize the domain, that Sam Hughes has some excellent science fiction freely available in a serialized form here as well. Well worth investigating.