Generated.

[homepage.git] / blog / Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html

diff --git a/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html b/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
index fb9ace2b637cf59db6f5a4db4d59cb67cfa0532f..b5b2833a0a95d69f45bf1b781c63d10d48051930 100644 (file)
--- a/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
+++ b/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
@@ -41,7 +41,7 @@ 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="https://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html">Debian
+<a href="http://www.hungry.com/~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