Editing 1343: Manuals

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 8: Line 8:
  
 
==Explanation==
 
==Explanation==
The chart shows the quality of tools regarding their manual:
+
{{incomplete|Created by a BOT - Please change this comment when editing this page.}}
*If you don't even need a manual to use a certain tool, that tool tends to help solve problems effectively.
 
*If you do need a manual, the tool will probably solve the problems but you have to understand that manual before you can use this tool effectively.
 
*Much less helpful are the tools where you need a manual but it doesn't exist — these tools tend to create more problems than they solve.
 
*But the worst tools are where the manuals start with a description of the manual itself — which implies both that the tool is very complex and the manual is very hard to understand, or has low expectations of its viewers.
 
 
 
The title text refers to ''sudoers'', a config file for the unix command ''{{w|sudo}}''. ''sudo'' allows users to run a program with elevated permissions, as referenced in [[149: Sandwich]]. Man pages are collections of manuals for different tools, commands, files, and functions on Unix-like systems which can be viewed with the tool ''man''. You can type <code>man man</code> in a terminal to get the manpage for the manual program. See for instance also the comic [[912: Manual Override]].
 
 
 
The sudoers file specifies which users have sudo access, and which commands they are allowed to run as other users (typically root). The syntax of the file is very complex, and the manpage uses the {{w|Extended Backus–Naur Form}} (or EBNF) to describe the syntax. The sudoers man page starts off with an explanation of EBNF's grammar, which they reference throughout the rest of the man page in describing the syntax of the sudoers file. The [http://linux.die.net/man/5/sudoers sudoers man page] is very long, clocking in at 1504 lines. In contrast, the [http://linux.die.net/man/1/man manpages man page] only has 566 lines. The number of lines may differ between some distributions and versions.
 
 
 
The title text also notes that the manual's assurance, "don't despair" because "the definitions below are annotated", fails to be reassuring, and instead merely emphasizes the length and complexity of the document to read.
 
  
 
==Transcript==
 
==Transcript==
:[A horizontal line has four points labeled on it, with the second point from the left marked with a dashed vertical line dividing the horizontal line into two parts.]
+
{{incomplete transcript}}
:[An arrow labeled "Solve problems" points left from the vertical line.]
 
:[An arrow labeled "Create problems" points right from the vertical line.]
 
:[The points are labeled, from left to right, "Tools that don't need a manual", "Tools that need a manual", "Tools that need a manual but don't have one", and "Tools whose manual starts with 'how to read this manual'".]
 
  
 
{{comic discussion}}
 
{{comic discussion}}
[[Category:Charts]]
 
[[Category:Man pages]]
 

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)