Raspberry Pi and Chromebook Pixel
I haven’t had a commercially backed Linux device that I’ve been excited to use as much as my Pixel.
One of the things that brightened my day today was the realisation that Chromebooks support Linux filesystems for SDCards and other removable media.
This opens up a lot of Pi hackery possibilities.
echo -n "Passphrase:"
read -sr p
gpg -d --batch --passphrase "$p" "$0" | python
-----BEGIN PGP MESSAGE-----
Version: GnuPG v2.0.19 (GNU/Linux)
-----END PGP MESSAGE-----
Maybe I should combine this with puppet.
Apparently, the default SeaBIOS on the Chromebook Pixel only exposes 1M of RAM.
To boot a kernel and initramfs, you need a bit more than that. Here’s how I calculated how many megabytes the on board Intel graphics card removes from the main pool of RAM.
Yea, I’m one of those people now.
Chromebook Pixel: Konami Code compliant (Photo credit: Stratageme.com)
Went into the Tottenham Court Road store today. If it weren’t for the slight risk of dipping into my overdraft, I would be posting this reply from a pixel.
To maintain objectivity, I brought along a techy-minded friend from work along to review the shit specs out of it.
It has a lot of pixels, but it’s not made of chrome.
People have been asking me why I love the Chromebook Pixel so much. I’ve tried, and in most cases failed, to portray it verbally. So, lets try this…
I have been reading the GNU Make manual. I knew about some of these features already, implicit rules, special targets etc. I’ve used .PHONY for a while, without *really* knowing how it works (and thus, how to properly use it).
Today, I’ve learnt about .ONESHELL (new in gmake 3.82).
New author, introducing my brother!
Happy New Year
Firstly, an apology for not posting things here for a while. It’s not that I haven’t run out of topics to rant on about, or the lack of anything really new in the tech world in the run-up for Christmas. I could talk to you about Chromebooks success, or my exploits on EC2 (build servers for raspberry pis).