X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/326b1a1c4d040d2fb4fdddef69a4a68ffbfdd75f..ebfb53b51b789a038b3157fc273aaf96559b76c4:/blog/archive/2013/10/index.html diff --git a/blog/archive/2013/10/index.html b/blog/archive/2013/10/index.html index e09e062fb3..b84631e63c 100644 --- a/blog/archive/2013/10/index.html +++ b/blog/archive/2013/10/index.html @@ -36,17 +36,19 @@ create a image file, add a partition table, mount it and run debootstrap in the mounted directory to create a Debian system on a stick. Yesterday, I decided to try to teach it how to make images for Raspberry Pi, as part -of a plan to simplify the build system for the FreedomBox project. -The FreedomBox project already uses vmdebootstrap for the virtualbox -images, but its home made multistrap based system for Dreamplug -images, and it is lacking support for Raspberry Pi.

+of a plan to simplify the build system for +the FreedomBox +project. The FreedomBox project already uses vmdebootstrap for +the virtualbox images, but its current build system made multistrap +based system for Dreamplug images, and it is lacking support for +Raspberry Pi.

Armed with the knowledge on how to build "foreign" (aka non-native architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap code and adjusted it to be able to build armel images on my amd64 Debian laptop. I ended up giving vmdebootstrap five new options, allowing me to replicate the image creation process I use to make -Debian +Debian Jessie based mesh node images for the Raspberry Pi. First, the --foreign /path/to/binfm_handler option tell vmdebootstrap to call debootstrap with --foreign and to copy the handler into the @@ -578,6 +580,50 @@ me know. :)

Archive