Editing 1975: Right Click

Jump to: navigation, search

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 104: Line 104:
 
Advanced> several Unix commands, all absurd (or dangerous) for some reason:
 
Advanced> several Unix commands, all absurd (or dangerous) for some reason:
 
* <code>apt-get install /dev/null</code>: <code>apt-get</code> is the standard package manager used in Debian-derived Linux distributions (including Ubuntu); it is normally used to install software; <code>/dev/null</code> is the "bit-bucket" device on any Unix system, which can be used as a dummy output file to discard output or as a dummy empty input file. This command would attempt to install <code>/dev/null</code> (which is a device, not a package!) or, more correctly, would try to install a package reading its data from <code>/dev/null</code> (if <code>apt-get</code> is given a file name it tries to interpret it as a .deb package), which is obviously impossible.
 
* <code>apt-get install /dev/null</code>: <code>apt-get</code> is the standard package manager used in Debian-derived Linux distributions (including Ubuntu); it is normally used to install software; <code>/dev/null</code> is the "bit-bucket" device on any Unix system, which can be used as a dummy output file to discard output or as a dummy empty input file. This command would attempt to install <code>/dev/null</code> (which is a device, not a package!) or, more correctly, would try to install a package reading its data from <code>/dev/null</code> (if <code>apt-get</code> is given a file name it tries to interpret it as a .deb package), which is obviously impossible.
* <code>brew install apt-get</code>: <code>brew</code> is a third-party package manager for macOS; it is generally used to install "missing" open-source utilities on a macOS system; the command is attempting to install the aforementioned <code>apt-get</code>, which is both impossible (<code>apt-get</code> doesn't run on macOS) and hilariously recursive (did you install a package manager - brew - to install another one?). Even if this were possible, the package would have been called <code>apt</code>, as apt-get is only one of the commands in the package manager.
+
* <code>brew install apt-get</code>: <code>brew</code> is a third-party package manager for macOS; it is generally used to install "missing" open-source utilities on a macOS system; the command is attempting to install the aforementioned <code>apt-get</code>, which is both impossible (<code>apt-get</code> doesn't run on macOS) and hilariously recursive (did you install a package manager - brew - to install another one?). Even if this were possible, the package would have been called "aptitude", as apt-get is only one of the commands in the package manager.
 
* <code>/usr/local/bin/wine xen-hypervisor.exe</code>: <code>wine</code> is a compatibility layer used to run Windows executables on Linux (and on macOS); the fact that it is in <code>/usr/local</code> hints that it has been manually compiled on this machine; Xen is a Linux-based hypervisor, i.e. a software used to run and manage virtual machines over a Linux host, but the .exe suffix here hints that it is a Windows executable. The command would try to launch a Windows build of a Linux-based virtual machine manager on a Unix machine through a Windows emulation layer (wine).
 
* <code>/usr/local/bin/wine xen-hypervisor.exe</code>: <code>wine</code> is a compatibility layer used to run Windows executables on Linux (and on macOS); the fact that it is in <code>/usr/local</code> hints that it has been manually compiled on this machine; Xen is a Linux-based hypervisor, i.e. a software used to run and manage virtual machines over a Linux host, but the .exe suffix here hints that it is a Windows executable. The command would try to launch a Windows build of a Linux-based virtual machine manager on a Unix machine through a Windows emulation layer (wine).
 
* <code>source .bash_history</code>: the <code>source</code> shell command reads the file that is given as argument and executes each of its rows as a command in the current shell, roughly as if you typed them in; <code>.bash_history</code> (located in the user home directory) is the file where the bash shell saves the history of the commands that have been run. This command would re-run all the commands that have been typed in the shell.
 
* <code>source .bash_history</code>: the <code>source</code> shell command reads the file that is given as argument and executes each of its rows as a command in the current shell, roughly as if you typed them in; <code>.bash_history</code> (located in the user home directory) is the file where the bash shell saves the history of the commands that have been run. This command would re-run all the commands that have been typed in the shell.

Please note that all contributions to explain xkcd may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see explain xkcd:Copyrights for details). Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel | Editing help (opens in new window)