1084: Server Problem - Revision history

FaviFake at 13:17, 29 July 2025

2025-07-29T13:17:03Z

172.64.238.57: /* Explanation */ Expand definition of adobe

2023-12-29T12:49:57Z

‎Explanation: Expand definition of adobe

AmossGuy: adjust code formatting

2023-12-15T16:58:20Z

adjust code formatting

172.71.242.137: /* Explanation */

2023-12-08T07:17:48Z

‎Explanation

162.158.34.8: Undo revision 329199 by 172.70.91.230 (talk) Introduces several typological errors/confusions. Maybe two actual corrections in there, but they can be redone by someone with the time.

2023-11-17T22:08:54Z

Undo revision 329199 by 172.70.91.230 (talk) Introduces several typological errors/confusions. Maybe two *actual* corrections in there, but they can be redone by someone with the time.

172.70.91.230: /* Explanation */

2023-11-17T18:08:09Z

‎Explanation

162.158.179.69: /* Explanation */

2023-07-06T07:26:34Z

‎Explanation

Birdsinthewindow: /* Explanation */ changed a line to be more screenreader-friendly; added additional explanation

2023-04-18T18:47:03Z

‎Explanation: changed a line to be more screenreader-friendly; added additional explanation

172.71.223.4: /* Explanation */

2023-03-08T00:27:39Z

‎Explanation

KirbyDude25 at 18:28, 6 June 2022

2022-06-06T18:28:53Z

@@ Line 46: / Line 46: @@
 [[Category:Protip]]
 [[Category:Singularity]]
-[[Category:Cueball Computer Problems]]
+[[Category:Cueball's computer problems]]
 [[Category:Comics featuring real people]]

@@ Line 10: / Line 10: @@
 [[Cueball]] has messed up his {{w|Linux server}} (which can have the prompt ~# or ~$), {{tvtropes|WalkingTechbane|apparently not for the first time}}. [[Megan]] offers to take a look at the PC and types in "ls" — a basic command that lists the files in the current directory. The computer returns a bizarre error message — it trips over one of the simplest commands, indicating that Cueball's system is messed up. ''Really'' messed up.
-On Linux, most commands are executables usually found in either /bin or /usr/bin. The /usr/share folder, on the other hand, is where "architecture-independent shared data" is stored. Adobe is a software company that produces Acrobat and Photoshop. "android_vm" would likely be a virtual machine for Android. The .jar extension suggests a Java-language program. None of the above items are related to the command "ls", nor do they have anything to do with each other, with the semi-exception that Android is based on Java. Executables should also never be found within /usr/share or within directories named "example" or "doc" - indeed, by default Linux does not even look in the /usr/share directory for items that can be run unless the user {{w|PATH (variable)|tells it to do so by changing the $PATH variable}}. The presence of "ls.jar" within a folder called "android_vm" suggests Cueball was attempting to boot up a virtual Android device, but somehow wound up directing the Linux server to use the executable files meant for the virtual system instead of the correct ones in /bin or /usr/bin.
+On Linux, most commands are executables usually found in either /bin or /usr/bin. The /usr/share folder, on the other hand, is where "architecture-independent shared data" is stored. Adobe is a software company that produces Acrobat, Photoshop, and a wide range of other software for manipulating work revolving around a 2D canvas. "android_vm" would likely be a virtual machine for Android. The .jar extension suggests a Java-language program. None of the above items are related to the command "ls", nor do they have anything to do with each other, with the semi-exception that Android is based on Java. Executables should also never be found within /usr/share or within directories named "example" or "doc" - indeed, by default Linux does not even look in the /usr/share directory for items that can be run unless the user {{w|PATH (variable)|tells it to do so by changing the $PATH variable}}. The presence of "ls.jar" within a folder called "android_vm" suggests Cueball was attempting to boot up a virtual Android device, but somehow wound up directing the Linux server to use the executable files meant for the virtual system instead of the correct ones in /bin or /usr/bin.
 In the last frame Megan is bewildered by this result and asks ''"What did you do!?"''. Cueball suggest a course of action which mimics a common error message: "[X] is busy, please try again later." Obviously he has seen this type of message frequently enough to try it as a general cure in all similar cases (even scarier, there is a good possibility that his tech issues are so bizarre that it often works for him).

@@ Line 27: / Line 27: @@
 :[Megan stands next to the computer, Cueball sits behind her on his chair. The computer returns the following:]
-:<code>/usr/share/Adobe/doc/example/android_vm/root/sbin/ls.jar:
+:<code>/usr/share/Adobe/doc/example/android_vm/root/sbin/ls.jar:</code>
-:Error: Device is not responding.</code>
+:<code>Error: Device is not responding.</code>
 :[Megan turns towards Cueball who lifts his hands with palm up.]

@@ Line 8: / Line 8: @@
 ==Explanation==
-[[Cueball]] has messed up his {{w|Linux server}}, {{tvtropes|WalkingTechbane|apparently not for the first time}}. [[Megan]] offers to take a look at the PC and types in "ls" — a basic command that lists the files in the current directory. The computer returns a bizarre error message — it trips over one of the simplest commands, indicating that Cueball's system is messed up. ''Really'' messed up.
+[[Cueball]] has messed up his {{w|Linux server}} (which can have the prompt ~# or ~$), {{tvtropes|WalkingTechbane|apparently not for the first time}}. [[Megan]] offers to take a look at the PC and types in "ls" — a basic command that lists the files in the current directory. The computer returns a bizarre error message — it trips over one of the simplest commands, indicating that Cueball's system is messed up. ''Really'' messed up.
 On Linux, most commands are executables usually found in either /bin or /usr/bin. The /usr/share folder, on the other hand, is where "architecture-independent shared data" is stored. Adobe is a software company that produces Acrobat and Photoshop. "android_vm" would likely be a virtual machine for Android. The .jar extension suggests a Java-language program. None of the above items are related to the command "ls", nor do they have anything to do with each other, with the semi-exception that Android is based on Java. Executables should also never be found within /usr/share or within directories named "example" or "doc" - indeed, by default Linux does not even look in the /usr/share directory for items that can be run unless the user {{w|PATH (variable)|tells it to do so by changing the $PATH variable}}. The presence of "ls.jar" within a folder called "android_vm" suggests Cueball was attempting to boot up a virtual Android device, but somehow wound up directing the Linux server to use the executable files meant for the virtual system instead of the correct ones in /bin or /usr/bin.

@@ Line 8: / Line 8: @@
 ==Explanation==
-[[Cueball]] has messed up his {{w|Linux server}}, {{tvtropes|WalkingTechbane|apparently not for the first time}} (but mine uses ¬$). [[Megan]] offers to take a look at the PC and types in "ls" — a basic command that lists the files in the current directory. The computer returns a bizarre error message — it trips over one of the simplest commands, indicating that Cueball's system is messed up. ''Really'' messed up.
+[[Cueball]] has messed up his {{w|Linux server}}, {{tvtropes|WalkingTechbane|apparently not for the first time}}. [[Megan]] offers to take a look at the PC and types in "ls" — a basic command that lists the files in the current directory. The computer returns a bizarre error message — it trips over one of the simplest commands, indicating that Cueball's system is messed up. ''Really'' messed up.
-On Linux, most commands are executables usually found in either /bin or /usr/bin. The /usr/share folder, on the other hand, is where "architecture-independent shared data" is stored. Adobe is a software company that produces Acrobat and Photoshop. "android_vm" would likely be a virtual machine for Android. The .jar extension suggests a Java-language program. None of the above items are related to the command "ls", nor do they have anything to do with each other, with the semi-exception that Android is based on Java. Executables should also never be found within /usr/share or within directories named "example" or "doc" - indeed, by default, Linux does not even look in the /usr/share directory for items that can be run unless the user {{w|PATH (variable)|tells it to do so by changing the $PATH variable}}. The presence of "ls.jar" within a folder called "android_vm" suggests Cueball was attempting to boot up a virtual Android device, but somehow wound up directing the Linux server to use the executable files meant for the virtual system instead of the correct ones in /bin or /usr/bin.
+On Linux, most commands are executables usually found in either /bin or /usr/bin. The /usr/share folder, on the other hand, is where "architecture-independent shared data" is stored. Adobe is a software company that produces Acrobat and Photoshop. "android_vm" would likely be a virtual machine for Android. The .jar extension suggests a Java-language program. None of the above items are related to the command "ls", nor do they have anything to do with each other, with the semi-exception that Android is based on Java. Executables should also never be found within /usr/share or within directories named "example" or "doc" - indeed, by default Linux does not even look in the /usr/share directory for items that can be run unless the user {{w|PATH (variable)|tells it to do so by changing the $PATH variable}}. The presence of "ls.jar" within a folder called "android_vm" suggests Cueball was attempting to boot up a virtual Android device, but somehow wound up directing the Linux server to use the executable files meant for the virtual system instead of the correct ones in /bin or /usr/bin.
-In the last frame, Megan is bewildered by this result and asks ''"What did you do!?"''. Cueball suggests a course of action which mimics a common error message: "[X] is busy, please try again later." He has seen this type of message frequently enough to try it as a general cure in all similar cases (even scarier, there is a good possibility that his tech issues are so bizarre that it often works for him).
+In the last frame Megan is bewildered by this result and asks ''"What did you do!?"''. Cueball suggest a course of action which mimics a common error message: "[X] is busy, please try again later." Obviously he has seen this type of message frequently enough to try it as a general cure in all similar cases (even scarier, there is a good possibility that his tech issues are so bizarre that it often works for him).
-Megan then tells Cueball to "shut down the system and wait for the {{w|technological singularity|singularity}}," referring to a hypothetical future event when superintelligence can be artificially created. Since future superintelligent humans/computers transcend our comprehension, we can't predict or even understand what will happen after the singularity. One interpretation is that Megan is telling Cueball that his system is such a mess that it will take a post-singularity superintelligence to fix it (or run it in its current state, as only an intelligence beyond present comprehension would be capable of doing). It also indicates that either [[1782: Team Chat]] or [[1668: Singularity]] could be the sequel to this comic. Since the singularity is a hypothetical event that may never happen or may happen at a date unimaginably far in the future, Megan is essentially telling Cueball to give up completely on fixing his server. This is her way of declaring that no human can fix or understand his server.
+Megan then tells Cueball to "shut down the system and wait for the {{w|technological singularity|singularity}}," referring to a hypothetical future event when superintelligence can be artificially created. Since future superintelligent humans/computers transcend our comprehension, we can't predict or even understand what will happen after the singularity. One interpretation is that Megan is telling Cueball that his system is such a mess that it will take a post-singularity superintelligence to fix it (or run it in its current state, as only an intelligence beyond present comprehension would be capable of doing). It also indicates that either [[1782: Team Chat]] or [[1668: Singularity]] could be the sequel to this comic. Since the singularity is a hypothetical event that may never happen, or may happen at a date unimaginably far in the future, Megan is essentially telling Cueball to give up completely on fixing his server. This is her way of declaring that no human can fix or understand his server.
-The title text is yet another [[: Category:P rotip|protip]] from [[Randall]]. {{w|Ray Kurzweil}} is an author and futurist who has {{w|Singularity Summit|talked}} and {{w|The Singularity Is Near|written}} much about a ''{{w|technological singularity}}''. Presumably, mangling the jargon (by confusing the concept of "singularity" with the science fiction term "{{w|cyberspace}}") is something Kurzweil (as an expert) would find annoying. Also, as Randall later pointed out in [[1573: Cyberintelligence]], the prefix "cyber" has not been used for a decade...
+The title text is yet another [[:Category:Protip|protip]] from [[Randall]]. {{w|Ray Kurzweil}} is an author and futurist who has {{w|Singularity Summit|talked}} and {{w|The Singularity Is Near|written}} much about a ''{{w|technological singularity}}''. Presumably, mangling the jargon (by confusing the concept of the "singularity" with the science fiction term "{{w|cyberspace}}") is something Kurzweil (as an expert) would find annoying. Also, as Randall later pointed out in [[1573: Cyberintelligence]], the prefix "cyber" has not really been used for a decade...
 ==Transcript==

@@ Line 12: / Line 12: @@
 The {{w|Filesystem Hierarchy Standard#Directory structure|/usr/share}} path should indicate "architecture-independent shared data". Adobe is the software company that produces Acrobat and Photoshop. Android VM would be a virtual machine for Android. The .jar extension suggests a Java-language program. None of Adobe software, Android, or Java are needed to run "ls". All of the above have nothing to do with each other, with the exception that Android applications (but not core command line utilities, like ls) are written in Java. Also, basic system executables like "ls" would never be placed within /usr/share or within some "example" or "doc" directory. On Linux, executables don't have filename extensions like ".exe" or ".jar". Core executables such as "ls" are often shipped with the operating system as binaries, so the presence of "ls.jar" suggests Cueball was attempting to unorthodoxly replace the existing executable with his own Java implementation. Additionally, it would require the folder to be within {{w|PATH (variable)|$PATH}}. In other words, the error message implies that the server is in a very bad state.
-In the last frame Megan is bewildered by this result and asks ''"what did you do?"''. Cueball suggest a course of action which mimics a common error message: "______ is busy, please try again later." Obviously he has seen this type of message frequently enough to try it as a general cure in all similar cases (even scarier, there is a good possibility that his tech issues are so bizarre that it often works for him).
+In the last frame Megan is bewildered by this result and asks ''"what did you do?"''. Cueball suggest a course of action which mimics a common error message: "[X] is busy, please try again later." Obviously he has seen this type of message frequently enough to try it as a general cure in all similar cases (even scarier, there is a good possibility that his tech issues are so bizarre that it often works for him).
-Megan then tells Cueball to "shut down the system and wait for the {{w|technological singularity|singularity}}," referring to a hypothetical future event when superintelligence can be artificially created. Since future superintelligent humans/computers transcend our comprehension, we can't predict or even understand what will happen after the singularity. One interpretation is that Megan is telling Cueball that his system is such a mess that it will take a post-singularity superintelligence to fix it (or run it in its current state, as only an intelligence beyond present comprehension would be capable of doing). It also indicates that either [[1782: Team Chat]] or [[1668: Singularity]] could be the sequel to this comic.
+Megan then tells Cueball to "shut down the system and wait for the {{w|technological singularity|singularity}}," referring to a hypothetical future event when superintelligence can be artificially created. Since future superintelligent humans/computers transcend our comprehension, we can't predict or even understand what will happen after the singularity. One interpretation is that Megan is telling Cueball that his system is such a mess that it will take a post-singularity superintelligence to fix it (or run it in its current state, as only an intelligence beyond present comprehension would be capable of doing). It also indicates that either [[1782: Team Chat]] or [[1668: Singularity]] could be the sequel to this comic. Since the singularity is a hypothetical event that may never happen, or may happen at a date unimaginably far in the future, Megan is essentially telling Cueball to give up completely on fixing his server. This is her way of declaring that no human can fix or understand his server.
 The title text is yet another [[:Category:Protip|protip]] from [[Randall]]. {{w|Ray Kurzweil}} is an author and futurist who has {{w|Singularity Summit|talked}} and {{w|The Singularity Is Near|written}} much about a ''{{w|technological singularity}}''. Presumably, mangling the jargon (by confusing the concept of the "singularity" with the science fiction term "{{w|cyberspace}}") is something Kurzweil (as an expert) would find annoying. Also, as Randall later pointed out in [[1573: Cyberintelligence]], the prefix "cyber" has not really been used for a decade...

1084: Server Problem - Revision history

FaviFake at 13:17, 29 July 2025

172.64.238.57: /* Explanation */ Expand definition of adobe

AmossGuy: adjust code formatting

172.71.242.137: /* Explanation */

162.158.34.8: Undo revision 329199 by 172.70.91.230 (talk) Introduces several typological errors/confusions. Maybe two *actual* corrections in there, but they can be redone by someone with the time.

172.70.91.230: /* Explanation */

162.158.179.69: /* Explanation */

Birdsinthewindow: /* Explanation */ changed a line to be more screenreader-friendly; added additional explanation

172.71.223.4: /* Explanation */

KirbyDude25 at 18:28, 6 June 2022

162.158.34.8: Undo revision 329199 by 172.70.91.230 (talk) Introduces several typological errors/confusions. Maybe two actual corrections in there, but they can be redone by someone with the time.