X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/26591612c6f2c23c796caba813d1e7ab4746dc94..ee8e077b581437eae5b52ed81d7f8288c449c750:/blog/tags/mesh%20network/index.html diff --git a/blog/tags/mesh network/index.html b/blog/tags/mesh network/index.html index a894cd86c1..6a0b9236ad 100644 --- a/blog/tags/mesh network/index.html +++ b/blog/tags/mesh network/index.html @@ -355,7 +355,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 -Debian +Debian Jessie based mesh node images for the Raspberry Pi. First, the --foreign /path/to/binfm_handler option tell vmdebootstrap to call debootstrap with --foreign and to copy the handler into the @@ -518,7 +518,7 @@ after inserting the target SD card into the build machine:

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 -an +an earlier blog post about this mesh testing.

The mesh node was not horribly expensive either. I bought @@ -712,6 +712,46 @@ mesh system.

Archive