anchor.diff:  # Minimum configuration for masters
   --master_data_dirs=/data/kudu
   --master_wal_dir=/data/kudu
  +# Uncomment this if your system does not support hole punching.
  +#--block_manager=file
  +
   # Minimum configuration for tablet servers
   --tserver_data_dirs=/data/kudu
   --tserver_wal_dir=/data/kudu
   --tserver_master_addrs=kudu_master.example.com
  +# Uncomment this if your system does not support hole punching.
  +#--block_manager=file
   ----
   // TODO probably change this to 'review and edit' later
   
  
positive.code: 
  .Operating System
  - An operating system and version supported by Cloudera.
  - OSX is not supported, even for building from source.
  
  .Storage
  - If solid state storage is available, storing Kudu WALs on such high-performance
  media may significantly improve latency when Kudu is configured for its highest
  durability levels.
  - An EXT4 or XFS filesystem to store Kudu data and write-ahead logs (WALs).
  
  == Install Using Parcels
  
  If you use Cloudera Manager, the easiest way to install Kudu is with parcels. First,
  add the parcel repository to Cloudera Manager. Then distribute Kudu to your cluster.
  Here is the procedure in detail.
  
  //  tag::quickstart_parcels[]
  
  
negative.code:   - You cannot store WALs in a subdirectory of the data directory.
    - If any host is both a master and tablet server, configure different directories
    for master and tablet server. For instance, `/data/kudu/master` and `/data/kudu/tserver`.
    - If you choose a filesystem that does not support <<req_hole_punching,hole punching>>,
    service start-up will fail. Exit the configuration wizard by clicking the *Cloudera*
    logo at the top of the Cloudera Manager interface, and search for the
    *Kudu Service Advanced Configuration Snippet (Safety Valve) for gflagfile* configuration option.
    Add the following line to it, and save your changes: `--block_manager=file`
  
  . If you did not need to exit the wizard, click *Continue*. Kudu masters and tablet
  servers are started. Otherwise, go to the Kudu service, and click *Actions > Start*.
  
  +
  // tag::verify_install[]
  