Generated.

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 4e5f96616d379d3752b0f0c4409b5d17f7824608..bf5d561a8a5c216ea7481db44cdf91e56af4c733 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=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

diff --git a/blog/archive/2013/10/10.rss b/blog/archive/2013/10/10.rss
index fe46ba8b0cfa2b52c9b0503cd7fe142241dfbcfc..472d8c7ce73fcc553213a9661c1c3fb93982ab77 100644 (file)
--- 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=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

diff --git a/blog/archive/2013/10/index.html b/blog/archive/2013/10/index.html
index 5ebb6448e8636984a846e97d67a8dd69d3123e54..e6e7bf2fa551bd0c26b159b4ee8290c752697551 100644 (file)
--- a/blog/archive/2013/10/index.html
+++ b/blog/archive/2013/10/index.html
@@ -48,7 +48,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=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

diff --git a/blog/index.html b/blog/index.html
index eef48f259c98c9e3af686f403ed737e467e5c57f..c2f56f05b033498ee6c25756ca4058dd069d78d4 100644 (file)
--- a/blog/index.html
+++ b/blog/index.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=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

diff --git a/blog/index.rss b/blog/index.rss
index c917b0e6177bde08e12b5deb7bcc1a4b1a3cb5fe..82c7ef73eda1e63d74e0ce63d24d041d92fd6aeb 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.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=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

diff --git a/blog/tags/debian/debian.rss b/blog/tags/debian/debian.rss
index c7f209474da498509203eb6c92937636e3dfbad4..89fb447cf45543c02a85fefa352545d643cb9b9b 100644 (file)
--- a/blog/tags/debian/debian.rss
+++ b/blog/tags/debian/debian.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=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

diff --git a/blog/tags/debian/index.html b/blog/tags/debian/index.html
index cbfaded86d88a139f0c7f59ccabf71d66c8d2299..3522e490850a03ba0563eb0ddf3047ea21506ad9 100644 (file)
--- a/blog/tags/debian/index.html
+++ b/blog/tags/debian/index.html
@@ -47,7 +47,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=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

diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss
index 75e37ffe8dadad10da204df23ccb92e50b48e0e1..4f0ee070a9a65698744cca13462bc087a89d3af4 100644 (file)
--- a/blog/tags/english/english.rss
+++ b/blog/tags/english/english.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=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

diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html
index 24b1c973f62b635ef355a105ebd1bd1df053e636..f831324637e9451f1c40b998b6820cb2d50673a1 100644 (file)
--- a/blog/tags/english/index.html
+++ b/blog/tags/english/index.html
@@ -47,7 +47,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=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

diff --git a/blog/tags/freedombox/freedombox.rss b/blog/tags/freedombox/freedombox.rss
index 7a13063be58809385db9143c3745b5e587da5077..62946554be391e17615ba60ee7914223190cba5b 100644 (file)
--- a/blog/tags/freedombox/freedombox.rss
+++ b/blog/tags/freedombox/freedombox.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=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

diff --git a/blog/tags/freedombox/index.html b/blog/tags/freedombox/index.html
index 7999c685b2ec0ed5d1bc4913a5df07f2b0d04cc0..949c4ed0216c1caf2465cbc44d75843637fa3efa 100644 (file)
--- a/blog/tags/freedombox/index.html
+++ b/blog/tags/freedombox/index.html
@@ -47,7 +47,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=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

diff --git a/blog/tags/mesh network/index.html b/blog/tags/mesh network/index.html
index 964adfc460b8b62ac2ba0357eea055a19e354d72..f7d0c69803c4fc049dc1b2aa762d4f7589c08eee 100644 (file)
--- a/blog/tags/mesh network/index.html
+++ b/blog/tags/mesh network/index.html
@@ -47,7 +47,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=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

diff --git a/blog/tags/mesh network/mesh network.rss b/blog/tags/mesh network/mesh network.rss
index 85dd8454175059cb21fa8d86abf95ee901397aa4..54453590d38f9b3605447a66ed492ef9f4a2a492 100644 (file)
--- a/blog/tags/mesh network/mesh network.rss
+++ b/blog/tags/mesh network/mesh network.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=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