Talk:1084: Server Problem

Explain xkcd: It's 'cause you're dumb.
(Difference between revisions)
Jump to: navigation, search
()
Line 26: Line 26:
  
 
== ==
 
== ==
Cueball's last line is a reference to an error message from the 8-bit era that went something like "Device not ready" which led some people to interpret it (literally) that they should try again later, when it really meant "the drive can't read the floppy disc that's in it". [[Special:Contributions/75.103.23.206|75.103.23.206]] 20:39, 7 December 2012 (UTC)
+
Cueball's last line is a reference to an error message from the 8-bit era that went something like "Device not ready" or "device busy, try again later" which led some people to interpret it (literally) that they should try again later, when it really meant "the drive can't read the floppy disc that's in it". [[Special:Contributions/75.103.23.206|75.103.23.206]] 20:39, 7 December 2012 (UTC)

Revision as of 20:40, 7 December 2012

It reminded me of the Flashback Virus that happened on Macs --Toddr (talk) 21:41, 9 August 2012‎ (UTC)

Contents

WooWoo Science from La-La Land

I love this paragraph: "Proponents of the singularity typically state that an "intelligence explosion",where superintelligences design successive generations of increasingly powerful minds, might occur very quickly and might not stop until the agent's cognitive abilities greatly surpass that of any human."

"OK team, you can stop now, we are much more intelligent than they are" "Don't we need to keep learning" "Nah!"

Whence comes the quote (and the follow-up commentary)? Attribution requested. Posted by an IP-address contributor; if you'd like to see this retained, please follow up with sources, explanation, and signature... otherwise, I think the content is just tangential enough to be removed. -- IronyChef (talk) 14:42, 16 August 2012 (UTC)
I believe the assumption is that they will hit some sort of fundamental physical limit on intelligence (At the extreme long-term end, perhaps latency due to the finite speed of light) and stop, rather than simply grow tired of advancing and focus attention elsewhere. Thirgfloorgreg (talk) 23:02, 17 August 2012 (UTC)

I think there are two ways of interpreting it. The most likely is that Megan's "What did you do!?" is a cry of frustration and amazement that Cueball has managed to *so* break the server. First, how on earth did Cueball's $PATH get changed *at all* so that executing "ls" in the shell ran anything but the usual /bin/ls? Second, how did it end up pointing to that ls.jar? And third, what the heck did Cueball do to end up with that ls.jar being installed there anyway!? Then her "You should shut down..." comment should be interpreted as being preceded with the phrase "You are so clearly not qualified to use a computer that ...". On the other hand, she may be expressing awe and amazement at his ability to interact with his system in such a bizarre way. And then her "You should shut down ..." comment should be preceded with the phrase, "You are clearly so at one with computing machinery that ..." TK 2012-08-17

alias ls='sudo java usr/share/Adobe/doc/example/android_vm/root/sbin/ls.jar' Davidy22 (talk) 23:35, 16 September 2012 (UTC)

or you could edit $PATH and do a soft link from the first member of PATH/ls to /usr/share/Adobe/doc/example/android_vm/root/sbin/ls.jar, anyway if i was Megan i wouldn't give up just yet, i still have /bin/ls and dir in my disposal... (and always check the environment variables... never assume the user's environment is clean.. it's just most likely that $PATH got screwed up (happened a bit too often for my liking in my previous company.. some people just love to use the command "set PATH=/myprog" instead of set PATH=${PATH}:/myprog ) and all you had to do is to reset the variable and we are done :) (but ya.. Megan's reaction is also my reaction.. it's fun to see people helpless and think that they have royally screwed up their system when you swoop in like a super hero to miraculously repair their system) 118.101.220.167 09:59, 4 December 2012 (UTC)

Considering Cueball's response, which suggests he is completely unaware of the unlikeliness of the error message, we can assume that the latter is not the case. Cueball totally fails to miss the point by suggesting a simple solution while not realizing how messed up his system would need to be to not even be able to operate the ls command. --88.75.181.101 02:45, 20 September 2012 (UTC)

Cueball has somehow messed up his path so that 'ls' now points to ls.jar, which executes the command on an external device (presumably an Android device).

Cueball's last line is a reference to an error message from the 8-bit era that went something like "Device not ready" or "device busy, try again later" which led some people to interpret it (literally) that they should try again later, when it really meant "the drive can't read the floppy disc that's in it". 75.103.23.206 20:39, 7 December 2012 (UTC)

Personal tools
Namespaces

Variants
Actions
Navigation
Tools

It seems you are using noscript, which is stopping our project wonderful ads from working. Explain xkcd uses ads to pay for bandwidth, and we manually approve all our advertisers, and our ads are restricted to unobtrusive images and slow animated GIFs. If you found this site helpful, please consider whitelisting us.

Want to advertise with us, or donate to us with Paypal or Bitcoin?