Live data from Hacker News

Suicide Linux (2009)

qntm.org

131–140 of 183 posts

Re: Suicide Linux (2009)

#131
post #4

So, does your Linux Roguelike have any progression? Can I get a magic item (ie. a file) to put in my home directory to protect it from a single mistake, or something?

Or the other way around, every time you avoid failure long enough it adds new failure modes?

Re: Suicide Linux (2009)

#132
post #95
post #45

Earlier quoted context omitted.

I can one up you: Coworker was trying to remove node so we could install a new version, so he ran: rm -rf /usr/bin node -rf was due to muscle memory, and unfortunately he forgot the space. That was a fun one to clean up. We were able to use nc because that was in /bin and not /usr/bin, so we used that to pipe curl over through a socket and then used curl to install dpkg + apt, then ran apt update to fix everything an…

So many questions about this one. Why would something by in /usr/bin that would be manual deletion? Wouldn't it be in /usr/local/bin? Were they manually deleting a package managed binary? For that matter, if you're manually installing a component like node with a large set of dirs and you might want a different version at some point (you're more likely to update to a newer major version of node than you are some base…

Yeah, I mean, obviously with the right precautions and best practices we could have avoided this. But this was a dev server, so it wasn't that serious if the entire thing got hosed. The only reason we recovered it using nc instead of just formatting the disk and starting over was because the server was physically in the office, and neither of us wanted to drive in (long commute), and we were mildly amused at the prospect of reviving a server over ssh.

When I meant it's still used today; it is, but it just displays a dashboard on a TV screen, it's not actually handling customer data or doing anything critical.

Re: Suicide Linux (2009)

#133

Earlier quoted context omitted.

> the operating system does its best to pretend that nothing is wrong, so it takes you as long as possible to realize that you've made a mistake. You're describing my (modest) experience with Javascript: it fails silently. I was describing it this way to a colleague: Javascript is a Japanese girlfriend, too polite to show you your mistakes so you have a hard time to know what you did wrong. I want a rigorous German g…

I am from the left-liberal side of things, including my choice of employers, and I am always flummoxed when I come into HN and see developers a) make comments that are flagrantly bigoted and misogynistic b) indicate that they make comments like these to their colleagues Do devs really say horrible things like this at the workplace? If anyone on my team made jokes about Japanese vs. Italian girlfriends, either they wo…

I wonder about cultural differences here. Ethnic/national jokes used to be very common in the workplace, but in the last few decades have become increasingly taboo. However, I don't think that change has happened to the same extent in all countries. I think in English-speaking countries (and especially so in North America) it has happened to a much greater extent than in many non-English speaking countries. To assume that all workplaces globally adopt the standards of your workplace, or workplaces in your country, is itself a failure to be aware of cultural diversity.

One thing about these kind of jokes, is they vary a lot in how much prejudice they encode. For example, there is a stereotype in Australian culture of the "whingeing pom", the person from England who always complains, and there is a tradition of jokes based on that stereotype. Does that mean the English are oppressed in Australia, or that Australians hate English people? Or is it more like when you gently tease your friends and family? (To use an Americanism, "joshing"). It is not like the English recipients of this kind of teasing don't have plenty of comebacks – jokes about Australians being all descended from criminals, etc. (See also [1].) I think there is a big difference between those kinds of gentle jokes which don't really encode any significant degree of racial/ethnic prejudice, and other sorts of jokes that do – it depends a lot on who is making the joke, which group is the target, and the nature and history of the relationship between the joke-teller's group and the target group.

Regardless of all that, I wouldn't tell those kinds of jokes in a work environment – some people are likely to be offended, and causing offence isn't worth it. (Plus I rarely tell jokes of any sort, since telling jokes has never been my strong suit). But if other workplaces, in other countries, have different cultures in which those kinds of jokes are more acceptable, I'm not going to judge those cultures negatively because of it, and try to exhibit enough cultural sensitivity to realise that cultures like that exist, and I'm not going to say that my culture is superior to theirs.

(You also mentioned the gendered aspect of the jokes; I would expect that attitudes towards gendered jokes and how they are experienced also vary from culture to culture – and that women experience them differently in different cultures, and even individual women may experience them differently in the same culture – but I don't feel like I know enough about that whole issue to say more than that.)

[1] https://www.theguardian.com/commentisfree/2013/jul/08/what-b...

Re: Suicide Linux (2009)

#134

Earlier quoted context omitted.

I've actually wished for something that takes it the other direction: Technically, everything it does is allowed, but it's designed to stress-test your assumptions. So, a distro that replaces half of coreutils with busybox, the other half with toybox or BSD ports or something, the system libc is musl, build tools are patched to randomly switch between using gcc or clang (both of which have `-Werror` enabled by defaul…

Strange Linux

[deleted]

Re: Suicide Linux (2009)

#135
post #27

> Perhaps rm -rf / should be replaced with something with more verbose flags set. That way, when you run a bad command, you are told immediately that things are being deleted This gives me an idea: Hell Linux. In Hell Linux, the operating system does its best to pretend that nothing is wrong, so it takes you as long as possible to realize that you've made a mistake. Commands ignore all unrecognized flags. In shell sc…

I've actually wished for something that takes it the other direction: Technically, everything it does is allowed, but it's designed to stress-test your assumptions. So, a distro that replaces half of coreutils with busybox, the other half with toybox or BSD ports or something, the system libc is musl, build tools are patched to randomly switch between using gcc or clang (both of which have `-Werror` enabled by defaul…

Nix with --pure does most of what you want here.

Re: Suicide Linux (2009)

#136

Earlier quoted context omitted.

I am from the left-liberal side of things, including my choice of employers, and I am always flummoxed when I come into HN and see developers a) make comments that are flagrantly bigoted and misogynistic b) indicate that they make comments like these to their colleagues Do devs really say horrible things like this at the workplace? If anyone on my team made jokes about Japanese vs. Italian girlfriends, either they wo…

Gosh I didn't expect to start anything more than a few smiles with this comment. I'm French, this is absolutely normal to say that where I'm from, and I can tell you that no German or Italian woman / man would take offense for what I said (angry Twitter mobs don't count ;) I can't speak for Japanese people since I never met any. I don't know if your reaction is representative of US culture, but having to tip toe arou…

> having to tip toe around words and not say what you think doesn't scream free country to me

Being from the US, and not being part of the vocal minority that reacts like this, I will agree with you that the last few years have increased the sense that we aren't really free to say things that deviate from the 'approved opinion'.

Re: Suicide Linux (2009)

#137
post #45

Earlier quoted context omitted.

I can one up you: Coworker was trying to remove node so we could install a new version, so he ran: rm -rf /usr/bin node -rf was due to muscle memory, and unfortunately he forgot the space. That was a fun one to clean up. We were able to use nc because that was in /bin and not /usr/bin, so we used that to pipe curl over through a socket and then used curl to install dpkg + apt, then ran apt update to fix everything an…

My teammate a couple years ago was writing a script that needed to clear a working directory, so `rm -rf $path/*`. He ran it during debugging and found one mistake - at some point the $path variable came in empty......

This is why set -u goes at the top of all my scripts ;)

Re: Suicide Linux (2009)

#138

Earlier quoted context omitted.

That's a bit extreme. You should at least allow some error messages. Though those ones should just say "Oops, something went wrong :)"

Seriously speaking, it took me many years to realize that nearly all Windows BSoD messages are non-specific and useless - looking them up is a total waste of time. The only correct way to identify the actual error is analyzing the crashdump in WinDbg. I recently fixed a family computer that crashes randomly after a RAM upgrade. Removing the RAM didn't help, and it was totally a wild goose chase. The BSoD stop codes i…

That's quite the debugging! I can see how you acquired your username.

Re: Suicide Linux (2009)

#139
post #27

> Perhaps rm -rf / should be replaced with something with more verbose flags set. That way, when you run a bad command, you are told immediately that things are being deleted This gives me an idea: Hell Linux. In Hell Linux, the operating system does its best to pretend that nothing is wrong, so it takes you as long as possible to realize that you've made a mistake. Commands ignore all unrecognized flags. In shell sc…

Actually worked on something similar about 16 years ago. The idea was an attacker could be led astray and then drop various behavioral clues to disclose their identity past a legally arguable threshold based on challenges and confusions selectively presented. The guy I was working on it with dropped out of academics for a career of spirituality. He went off to a monastery so I also abandoned the project as well. We n…

ok, just talked to my friend. He was evasive and politely changed the topic so yeah, I still have zero information. I guess that's the right approach.

If I has asked him if he knew the name of the monastery as opposed to whether the entire story was a canard, I probably could have gotten further. By foolishly asking if it was a story, I think he fell back on the "zero information" strategy - as in, even if it's real and he's living a solemn life of meditation, don't say anything. Me effectively going "Hey man, I gotta question about spies" was in retrospect, pretty dumb.

Re: Suicide Linux (2009)

#140
post #72

Earlier quoted context omitted.

There's a more elegant solution: rm -rf /* Just an extra asterisk is enough. The shell expands it to all subdirectories under /, and it's compatible with all Unix systems.

Wildcard expansion skips filenames beginning with a dot, though.

There's no useful ones at the root level however.
Post reply on HN