X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/1dba9534f0537cdd58650b2a2d4672e5df41d966..17ddfe379836481b829ea2070f16b2a928806eb8:/blog/archive/2013/10/10.rss

diff --git a/blog/archive/2013/10/10.rss b/blog/archive/2013/10/10.rss
index cd9cbba473..5bbd7adec3 100644
--- a/blog/archive/2013/10/10.rss
+++ b/blog/archive/2013/10/10.rss
@@ -30,7 +30,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
@@ -227,7 +227,7 @@ after inserting the target SD card into the build machine:</p>
 wifi card inserted should give you a mesh node.  At least it does for
 me with a the wifi card I am using. The default mesh settings are the
 ones used by the Oslo mesh project at Hackeriet, as I mentioned in
-<a href="https://people.skolelinux.org/pere/blog/Oslo_community_mesh_network___with_NUUG_and_Hackeriet_at_Hausmania.html">an
+<a href="http://www.hungry.com/~pere/blog/Oslo_community_mesh_network___with_NUUG_and_Hackeriet_at_Hausmania.html">an
 earlier blog post about this mesh testing</a>.</p>
 
 <p>The mesh node was not horribly expensive either.  I bought