New Chrubuntu script + github.

The "one to rule them all" script from Jay's blog is on Google Drive and has not been updated the last time I checked. The new updates/commits to the script support a 64bit filesystem as the Dev and possibly Beta channels(through chrome://help once logged in) provide the Acer C7 with a 64bit kernel and 32bit filesystem(kernel 3.8.11 x86_64 as of writing this).

Feel free to edit my changes. I was trying to update and shrink things a bit, but I am a Wiki newbie.
I did not see any area to discuss modules / patches for a custom kernel or the C7 itself, even though it says patches are welcome in the Wiki. If someone could either provide that information to me or put on the Wiki itself, you would have my thanks.
UserError (talk) 08:11, 18 September 2013 (UTC)

So there's no real way to 'submit' patches. once you get something working post it to thread on the forums. If you need hosting, and you get someone else to confirm that it works hit me up and I'll host it for you. You can always find me in IRC or on bbs.archlinux GrayHatter (talk) 22:20, 18 September 2013 (UTC)

it might worth taking the guide out of the c7 chromebook and into a generic solution for having Arch rootfs on Chromebooks without SeaBIOS payload

I've been doing some reading today on how to flash the coreboot seabios to the C7, I'm probably going to tackle some time in the next week. If I do it successfully I'm happy to write the guide for it. This tag is certainly correct, it's poorly written with too many caveats to list; it would be better to start fresh with an ACTUAL Arch installation guide. (( as suggested by User:Dhead )) GrayHatter (talk) 02:27, 21 September 2014 (UTC)

GrayHatter, the Chromebook page now also covers the installation procedure on non SeaBIOS models as part of the general Chromebook#Installation guide so I removed duplicate content (that exist in the Chromebook page, Beginners guide or Grub) and some links that covered in the custom firmware topic. As I see it the C710 page should only cover model specific information like how to disable the hardware write protection, post installation configurations (touchpad xorg.conf.d, different tweaks) and known issues. Having a unified guide for Chromebook will help having one update guide and not countless outdated guides and also push to to collaboration between users if a patched kernel package needed to be maintained for a while. So I believe this is the way to go. Dhead (talk)