<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>
+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
<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>
+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
<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>
+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
<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>
+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
<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>
+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
<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>
+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
<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>
+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
<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>
+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
<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>
+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
<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>
+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
<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>
+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
<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>
+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
<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>
+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