I suppose it could, but my intent was just to use the developer tools to burn a card with dd. I returned the CB back to a normal setup when I was done.
That was kind of me just wondering "what if a user/student's only exposure to computing was their chromebook, and wanted to burn a card to run on a pi?"
Normally most of us have come through the ranks of older hardware, but this situation could potentially come up with younger users, so I wanted to be prepared.
Without repeating too much, the gist though of running TC / Picore on a CB is this:
1) Sole os only: not all models have the bios support to have TC be the sole os. Better have your hardware support down pretty nicely.
2) Hybrid - ChromeOs running TC in a chroot environment (crouton makes this easy. I suppose one could write their own crouton script for TC to do this - details on the github crouton project.)
Problems for me: I'm done battling with bios issues. Had enough with supposedly "open firmware" getting Crux-PPC to run on my G5 iMac. Fan control was always a problem on my model.
Chromeos hybrid - I haven't found any *guarantee* that the ability to run a chroot underneath in developer mode (and all that pertains to security wise) won't be taken away by a managerial decision upon the next os update that is pushed out to all users. Unlikely, but I'm not going to take that chance.
With the Pi, (or TC with already established hardware) *I'm* in sole control of my hardware and operational environment.
I think it might be a fun experiment / project for some, but for me, TC/Picore is more about learning and improving my skills closer to the metal, rather than just setting up or trying to emulate a turn-key environment. But that's me. Not to mention the keyboard's escape-key probably won't stand up to my pounding away in vi.