objectives.txt

  # samsung chromebook, HP Chromebook 11 G1, HP Chromebook 11 G2, Samsung Chromebook 2 13", Samsung Chromebook 2 11". "Exynos, daisy board variants", use "ALARM peach"
  # Acer Chromebook R13 "elm board" "Mediatek MT8173 Cortex-A72/A53 2.1GHz/1.7GHz quad-core HMP processor", use "ALARM oak"
  # ASUS Chromebook Flip C100PA, ASUS Chromebook C201, AOpen Chromebase Mini, Asus Chromebit CS10, AOpen Chromebox Mini, Hisense Chromebook C11, "Rockchip RK3288" use "ALARM veyron"
  # Samsung Chromebook Plus, "Rockchip RK3399" uses "ALARM gru"
  # Acer Chromebase, Acer Chromebook 13 (CB5-311), HP Chromebook 14 G3, "Tegra K1 nyan" are unaccounted for so far"

  # note: r13 and chromebook plus installs are identical, yet have different kernel partiton sizes than daisy and veyron. both r13 and chromebook plus had identical partition sizes.
 
  # we need to organize the residual files left over by the install
  # if the user decides to keep the script and the tarball, lets create an appropriately named directory, rename the script to reflect the chromebook, and put tarball and script in the one directory, just in case the user is dealing with more than one chromebook.
  
  # let's also have the script be ran at boot, via root's .bashrc, then remove itself from the bash rc after completion
  # give the user the option to keep parts of the helper script (hidden ssid, create user, ect)
  
  # come up with a script to link to the README.md that will harvest chromebook info and send it to us via email, in order to have enought info to account for unconfirmed chromebooks.