5 ms·
* Enable developer mode.[1] * Drop Crouton[2] onto Chromebook to get a full dev stack and unfortunate Ubuntu/XFCE environment. * Set up chroot and start build
by neverm0re 14y ago
* Enable developer mode.[1]
* Drop Crouton[2] onto Chromebook to get a full dev stack and unfortunate Ubuntu/XFCE environment.
* Set up chroot and start building other people's crap.
* Write to SD Card/internal storage and reboot.
Which step here is hard? Tedious to roll your own I'd give you, but you don't even need to as there's stuff like ArchLinuxARM[3] which skips the middle two steps.
[1]: https://sites.google.com/a/chromium.org/dev/chromium-os/developer-information-for-chrome-os-devices/samsung-arm-chromebook https://sites.google.com/a/chromium.org/dev/chromium-os/deve...
[2]: https://github.com/keyboardsurfer/Crouton https://github.com/keyboardsurfer/Crouton
[3]: http://archlinuxarm.org/platforms/armv7/samsung-chromebook http://archlinuxarm.org/platforms/armv7/samsung-chromebook
- marban 14y agoAny words on the performance? I feel like my Samsung Chromebook is already pretty busy running five browser tabs at the same time.
- deleted 14y ago[deleted]
- neverm0re 14y agoWhoops, serves me right for not double-checking [2]: https://github.com/dnschneid/crouton https://github.com/dnschneid/crouton
- alexose 14y agoNot gonna lie, I just spent several minutes trying to figure out what context sensitive notifications for Android had to do with hacking the chromebook.