Generated.

[homepage.git] / blog / archive / 2013 / 10 / 10.rss

diff --git a/blog/archive/2013/10/10.rss b/blog/archive/2013/10/10.rss
index 1418001907bcc605c9c674c312ea123f410b1309..472d8c7ce73fcc553213a9661c1c3fb93982ab77 100644 (file)
--- a/blog/archive/2013/10/10.rss
+++ b/blog/archive/2013/10/10.rss
@@ -18,17 +18,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
 <a href="https://wiki.debian.org/RaspberryPi">Raspberry Pi</a>, 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.</p>
+of a plan to simplify the build system for
+<a href="https://wiki.debian.org/FreedomBox">the FreedomBox
+project</a>.  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.</p>
 
 <p>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
-<a href=http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html"">Debian
+<a href="http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html">Debian
 Jessie based mesh node images for the Raspberry Pi</a>.  First, the
 <tt>--foreign /path/to/binfm_handler</tt> option tell vmdebootstrap to
 call debootstrap with --foreign and to copy the handler into the