Skip to content
View env is too small
[0.000000 0.000000]
[0.000040 0.000040] U-Boot SPL 2015.10-00006-g24da68e-dirty (Jan 11 2016 - 12:05:52)
[0.008944 0.008904] Reducing CPU from 800 MHz to 600 MHz.
[0.352041 0.343097] initcall: 8083676d
[0.353635 0.001594]
[0.353649 0.000014]
[0.353657 0.000008] U-Boot 2015.10-00006-g24da68e-dirty (Jan 11 2016 - 13:30:10 -0500)
[0.359584 0.005927]
[0.359596 0.000012] initcall: 80802985
[0.361681 0.002085] U-Boot code: 80800000 -> 80855338 BSS: -> 8088EC90
View etc ppp peers wvdial
name wvdial
View wget-list

Grab both the "orig" tarball and one of the matching "debian" tarballs from

I've used the "precise" one, as that's reasonably old and should work on Debian.

Untar the orig tarball, cd into the resulting directory, then untar the "debian" tarball. This will result in a nice debian/ directory. You can change the changelog if you want with dch.

Then just build it dpkg-buildpackage -uc -us -sa

When the build is complete, you'll find your nice debian package one level up, just like usual.


Eagle on Jessie

I use Eagle 7.4 in a Jessie chroot (on a Wheezy system).

In your Jessie, install the following things:

sudo apt-get install libx11-6 libxrender1 libxrandr2 libxcursor1 libfreetype6 \
  libfontconfig1 libxext6 libxi6 libssl1.0.0 libcups2 libx11-xcb1

Some Notes on Using AWS as a "Fast" Computer


I'm cheap. My personal computer is a Dell Latitude D620 with a Core2Duo processor and a few years old consumer grade SSD. It cannot do much very quickly and I would like to be able to have a machine which can build software much faster.

I've written about using AWS as a workstation computer before on my blog, so I figured I mind as well actually try and do that.

View gist:5cf21ac53b784f28809a
andrew@lati:~/git/kicad-libs$ git commit -a -s
[readmemore 18f97d9] readme: initial sensible rules for sch and pwr symbols
1 file changed, 86 insertions(+)
andrew@lati:~/git/kicad-libs$ git push kinali-bradfa readmemore -u
ssh: connect to host port 22: Network is unreachable
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
View flashrom.patch
--- dediprog.c.orig 2015-05-01 16:17:47.000000000 -0400
+++ dediprog.c 2015-05-07 07:52:43.000000000 -0400
@@ -110,8 +110,13 @@
target_leds = leds;
- ret = usb_control_msg(dediprog_handle, 0x42, 0x07, 0x09, target_leds,
+ if (dediprog_firmwareversion >= FIRMWARE_VERSION(5,5,1))
+ ret = usb_control_msg(dediprog_handle, 0x42, 0x07, (target_leds << 8) | 0x09, 0x0,

I want to have a tool like Google's repo but which is specific (or generic, but specific at first sounds easier) to managing OpenEmbedded development for product development. Basically, I want to have a two step process where you write a set of metadata that describes how to layout a directory structure of OE layers/bitbake/etc given a set of git repos and directories which exist alongside the metadata (and maybe perforce, ew, depot directories, via git-p4), and then a second step where those directories/repos are setup for you and everything gets checked out to the right state so that you can simply source oe-init-build-env and then run your bitbake.

View lvs--all-output.txt
andrew@rhino:~$ sudo lvs --all
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
lvhome vg0 Cwi-aoC--- 325.96g lvhomecache [lvhome_corig]
[lvhome_corig] vg0 owi-aoC--- 325.96g
lvhomecache vg0 Cwi---C--- 64.00g
[lvhomecache_cdata] vg0 Cwi-ao---- 64.00g
[lvhomecache_cmeta] vg0 ewi-ao---- 1.00g
[lvol0_pmspare] vg0 ewi------- 1.00g
lvroot vg0 Cwi-aoC--- 93.13g lvrootcache [lvroot_corig]
[lvroot_corig] vg0 owi-aoC--- 93.13g
Something went wrong with that request. Please try again.