Editing 1084: Server Problem
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 8: | Line 8: | ||
==Explanation== | ==Explanation== | ||
− | [[Cueball]] has messed up his {{w|Linux server}} | + | [[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, 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. | 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. |