These instructions have moved to https://github.com/emporia-vue-local/esphome
These are my notes on how to set up GPG with the private key stored on the hardware Yubikey. This will reduce the chances of your GPG private key from being stolen, and also allow you to protect other secrets such as SSH private keys.
It's just some notes and a partial worklog for now, but I may turn it into a full blog post later.
The polybar package has been updated so this is no longer needed. |
Add the following chunk to your existing ISC dhcpd.conf
file.
if exists user-class and ( option user-class = "iPXE" ) {
filename "http://boot.smidsrod.lan/boot.ipxe";
}
else {
filename "undionly.kpxe";
}
(or see https://gist.github.com/4008017 for a more elaborate setup
/** | |
* This code is licensed under the terms of the MIT license | |
* | |
* Deep diff between two object, using lodash | |
* @param {Object} object Object compared | |
* @param {Object} base Object to compare with | |
* @return {Object} Return a new object who represent the diff | |
*/ | |
function difference(object, base) { | |
function changes(object, base) { |
####Disabling SPI write protection
Put the Chromebook in developer-mode:
- With machine powered off, hold down Esc and Refresh(F3) while hitting power button
- At warning prompt, hit Control+D, then Enter at prompt about enabling developer mode
- Machine will format itself
Now remove the write-protect screw to enable flashrom
to flash new Coreboot/Libreboot.
Flip powered-off machine over and remove 8 philips-head screws. 2 are located under rubber feet.
#!/usr/bin/env python | |
from sys import argv, stdin, stdout, stderr | |
from traceback import print_exc | |
from os import path, isatty | |
from textwrap import dedent | |
from collections import Counter | |
from math import sqrt | |
import inspect | |
# Luminance threshold values |
The `Getting started`_ instructions are a good start (no surprise there!) but are somewhat incomplete and currently look a bit outdated (I plan to fix them soon): however, the outcome has been that I have struggled more than I felt necessary in building and running Mesos on a dev VM (Ubuntu 14.04 running under VirtualBox).
Some of the issue seem to arise from the unfortunate combination of Mesos Master trying to guess its own IP address, the VM being (obviously) non-DNS resolvable and, eventually, the Slave and the Framework failing to properly communicate with the Master.
In the process of solving this, I ended up automating all the dependencies installation, building and running the framework; I have then broken it down into the following modules to make it easier to run only parts of the process.
#!/bin/bash | |
set -e | |
for opt in $* ; do | |
case "$opt" in | |
--debug) hubot_debug="coffee --nodejs --debug";; | |
esac | |
done |