anchor.diff:  This <<flow,_flow_>> is running on a client because a user initiated it. To do
   so, he probably used the web-based Graphical User Interface (GUI), which allows
   a GRR user to start flows for clients and review the results. Or he could also
  -have used the text-based <<_the_console,_console_>> to do the same.
  +have used the text-based <<the-console,_console_>> to do the same.
   
   Any flow that can be run on a single machine can also be run as a Hunt. A hunt
   allows running a flow on all, or any subset of machines talking to the GRR
  
positive.code: Glossary
  --------
  
  [[aff4]] AFF4::
  AFF4 is the data model used for storage in GRR, with some minor extensions. You
  can read about the usage in the GRR paper linked above and there is additional
  detail linked at http://www.forensicswiki.org/wiki/AFF4
  
  [[agent]] Agent::
  A platform-specific program that is installed on machines that one might want to
  investigate. It communicates with the GRR server and can perform client actions
  at the server's request.
  
  [[client]] Client::
  A system that has an agent installed. Also used to refer to the specific
  instance of an agent running in that system.
  
  [[client_action]] Client Action::
  A client action is an action that a client can perform on behalf of the server.
  It is the base unit of work on the client. Client actions are initiated by the
  server through Flows.  Example client actions are ListDirectory,
  EnumerateFilesystems, Uninstall.
  
  [[collection]] Collection::
  A Collection is a logical set of objects stored in the AFF4 database. Generally
  these are a list of URNs containing a grouping of data such as Artifacts or
  Events from a client.
  
  [[datastore]] DataStore::
  The backend is where all AFF4 and Scheduler data is stored. It is provided as an
  abstraction to allow for replacement of the datastore without significant
  rewrite. The datastore supports read, write, querying and filtering.
  
  [[flow]] Flow::
  A logical collection of server or client actions which achieve a given
  objective. A flow is the core unit of work in the GRR server. For example a
  BrowserHistory flow contains all the logic to download, extract and display
  
negative.code: otherwise execute the binary. If you are not an administrator it will prompt
  you for credentials.
  It should then install silently in the background, unless you enabled the
   link:user_manual.doc#debugging-the-agent-install[verbose build]
  
  
  Deployment methods
  