1 <?xml version=
"1.0" encoding=
"ISO-8859-1"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries from October
2013</title>
5 <description>Entries from October
2013</description>
6 <link>http://www.hungry.com/~pere/blog/
</link>
10 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
11 <link>http://www.hungry.com/~pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
12 <guid isPermaLink=
"true">http://www.hungry.com/~pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
13 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
14 <description><p
>The
15 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
16 program is a a very nice system to create virtual machine images. It
17 create a image file, add a partition table, mount it and run
18 debootstrap in the mounted directory to create a Debian system on a
19 stick. Yesterday, I decided to try to teach it how to make images for
20 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
21 of a plan to simplify the build system for
22 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
23 project
</a
>. The FreedomBox project already uses vmdebootstrap for
24 the virtualbox images, but its current build system made multistrap
25 based system for Dreamplug images, and it is lacking support for
26 Raspberry Pi.
</p
>
28 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
29 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
30 code and adjusted it to be able to build armel images on my amd64
31 Debian laptop. I ended up giving vmdebootstrap five new options,
32 allowing me to replicate the image creation process I use to make
33 <a href=
"https://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
34 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
35 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
36 call debootstrap with --foreign and to copy the handler into the
37 generated chroot before running the second stage. This allow
38 vmdebootstrap to create armel images on an amd64 host. Next I added
39 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
40 fstype
</tt
> to teach it to create a separate /boot/ partition with the
41 given file system type, allowing me to create an image with a vfat
42 partition for the /boot/ stuff. I also added a
<tt
>--variant
43 variant
</tt
> option to allow me to create smaller images without the
44 Debian base system packages installed. Finally, I added an option
45 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
46 as a boot loader. It is not needed on the Raspberry Pi and probably
47 most other non-x86 architectures. The changes were accepted by the
48 upstream author of vmdebootstrap yesterday and today, and is now
50 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
51 upstream project page
</a
>.
</p
>
53 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
54 create a small script (the customize script) to add the non-free
55 binary blob needed to boot the Raspberry Pi and the APT source
60 set -e # Exit on first error
61 rootdir=
"$
1"
62 cd
"$rootdir
"
63 cat
&lt;
&lt;EOF
> etc/apt/sources.list
64 deb http://http.debian.net/debian/ jessie main contrib non-free
66 # Install non-free binary blob needed to boot Raspberry Pi. This
67 # install a kernel somewhere too.
68 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
69 -O $rootdir/usr/bin/rpi-update
70 chmod a+x $rootdir/usr/bin/rpi-update
71 mkdir -p $rootdir/lib/modules
72 touch $rootdir/boot/start.elf
73 chroot $rootdir rpi-update
74 </pre
></p
>
76 <p
>Next, fetch the latest vmdebootstrap script and call it like this
77 to build the image:
</p
>
80 sudo ./vmdebootstrap \
83 --distribution jessie \
84 --mirror http://http.debian.net/debian \
93 --root-password raspberry \
94 --hostname raspberrypi \
95 --foreign /usr/bin/qemu-arm-static \
96 --customize `pwd`/customize \
100 --package ca-certificates \
103 </pre
></p
>
105 <p
>The list of packages being installed are the ones needed by
106 rpi-update to make the image bootable on the Raspberry Pi, with the
107 exception of netbase, which is needed by debootstrap to find
108 /etc/hosts with the minbase variant. I really wish there was a way to
109 set up an Raspberry Pi using only packages in the Debian archive, but
110 that is not possible as far as I know, because it boots from the GPU
111 using a non-free binary blob.
</p
>
113 <p
>The build host need debootstrap, kpartx and qemu-user-static and
114 probably a few others installed. I have not checked the complete
115 build dependency list.
</p
>
117 <p
>The resulting image will not use the hardware floating point unit
118 on the Raspberry PI, because the armel architecture in Debian is not
119 optimized for that use. So the images created will be a bit slower
120 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
125 <title>Det er jo makta som er mest sårbar ved massiv overvåkning av Internett
</title>
126 <link>http://www.hungry.com/~pere/blog/Det_er_jo_makta_som_er_mest_s_rbar_ved_massiv_overv_kning_av_Internett.html
</link>
127 <guid isPermaLink=
"true">http://www.hungry.com/~pere/blog/Det_er_jo_makta_som_er_mest_s_rbar_ved_massiv_overv_kning_av_Internett.html
</guid>
128 <pubDate>Sat,
26 Oct
2013 20:
30:
00 +
0200</pubDate>
129 <description><p
>De siste måneders eksponering av
130 <a href=
"http://www.aftenposten.no/nyheter/uriks/Her-er-Edvard-Snowdens-mest-omtalte-avsloringer-
7351734.html
">den
131 totale overvåkningen som foregår i den vestlige verden dokumenterer
132 hvor sårbare vi er
</a
>. Men det slår meg at de som er mest sårbare
133 for dette, myndighetspersoner på alle nivåer, neppe har innsett at de
134 selv er de mest interessante personene å lage profiler på, for å kunne
135 påvirke dem.
</p
>
137 <p
>For å ta et lite eksempel: Stortingets nettsted,
138 <a href=
"http://www.stortinget.no/
">www.stortinget.no
</a
> (og
140 <a href=
"http://data.stortinget.no/
">data.stortinget.no
</a
>),
141 inneholder informasjon om det som foregår på Stortinget, og jeg antar
142 de største brukerne av informasjonen der er representanter og
143 rådgivere på Stortinget. Intet overraskende med det. Det som derimot
144 er mer skjult er at Stortingets nettsted bruker
145 <a href=
"http://en.wikipedia.org/wiki/Google_Analytics
">Google
146 Analytics
</a
>, hvilket gjør at enhver som besøker nettsidene der også
147 rapporterer om besøket via Internett-linjer som passerer Sverige,
148 England og videre til USA. Det betyr at informasjon om ethvert besøk
149 på stortingets nettsider kan snappes opp av svensk, britisk og USAs
150 etterretningsvesen. De kan dermed holde et øye med hvilke
151 Stortingssaker stortingsrepresentantene synes er interessante å sjekke
152 ut, og hvilke sider rådgivere og andre på stortinget synes er
153 interessant å besøke, når de gjør det og hvilke andre representanter
154 som sjekker de samme sidene omtrent samtidig. Stortingets bruk av
155 Google Analytics gjør det dermed enkelt for utenlands etteretning å
156 spore representantenes aktivitet og interesse. Hvis noen av
157 representantene bruker Google Mail eller noen andre tjenestene som
158 krever innlogging, så vil det være enda enklere å finne ut nøyaktig
159 hvilke personer som bruker hvilke nettlesere og dermed knytte
160 informasjonen opp til enkeltpersoner på Stortinget.
</p
>
162 <p
>Og jo flere nettsteder som bruker Google Analytics, jo bedre
163 oversikt over stortingsrepresentantenes lesevaner og interesse blir
164 tilgjengelig for svensk, britisk og USAs etterretning. Hva de kan
165 bruke den informasjonen til overlater jeg til leseren å undres
171 <title>A Raspberry Pi based batman-adv Mesh network node
</title>
172 <link>http://www.hungry.com/~pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
</link>
173 <guid isPermaLink=
"true">http://www.hungry.com/~pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
</guid>
174 <pubDate>Mon,
21 Oct
2013 11:
40:
00 +
0200</pubDate>
175 <description><p
>The last few days I have been experimenting with
176 <a href=
"http://www.open-mesh.org/projects/batman-adv/wiki
">the
177 batman-adv mesh technology
</a
>. I want to gain some experience to see
178 if it will fit
<a href=
"https://wiki.debian.org/FreedomBox
">the
179 Freedombox project
</a
>, and together with my neighbors try to build a
180 mesh network around the park where I live. Batman-adv is a layer
2
181 mesh system (
"ethernet
" in other words), where the mesh network appear
182 as if all the mesh clients are connected to the same switch.
</p
>
184 <p
>My hardware of choice was the Linksys WRT54GL routers I had lying
185 around, but I
've been unable to get them working with batman-adv. So
186 instead, I started playing with a
187 <a href=
"http://www.raspberrypi.org/
">Raspberry Pi
</a
>, and tried to
188 get it working as a mesh node. My idea is to use it to create a mesh
189 node which function as a switch port, where everything connected to
190 the Raspberry Pi ethernet plug is connected (bridged) to the mesh
191 network. This allow me to hook a wifi base station like the Linksys
192 WRT54GL to the mesh by plugging it into a Raspberry Pi, and allow
193 non-mesh clients to hook up to the mesh. This in turn is useful for
194 Android phones using
<a href=
"http://servalproject.org/
">the Serval
195 Project
</a
> voip client, allowing every one around the playground to
196 phone and message each other for free. The reason is that Android
197 phones do not see ad-hoc wifi networks (they are filtered away from
198 the GUI view), and can not join the mesh without being rooted. But if
199 they are connected using a normal wifi base station, they can talk to
200 every client on the local network.
</p
>
202 <p
>To get this working, I
've created a debian package
203 <a href=
"https://github.com/petterreinholdtsen/meshfx-node
">meshfx-node
</a
>
205 <a href=
"https://github.com/petterreinholdtsen/meshfx-node/blob/master/build-rpi-mesh-node
">build-rpi-mesh-node
</a
>
206 to create the Raspberry Pi boot image. I
'm using Debian Jessie (and
207 not Raspbian), to get more control over the packages available.
208 Unfortunately a huge binary blob need to be inserted into the boot
209 image to get it booting, but I
'll ignore that for now. Also, as
210 Debian lack support for the CPU features available in the Raspberry
211 Pi, the system do not use the hardware floating point unit. I hope
212 the routing performance isn
't affected by the lack of hardware FPU
215 <p
>To create an image, run the following with a sudo enabled user
216 after inserting the target SD card into the build machine:
</p
>
219 % wget -O build-rpi-mesh-node \
220 https://raw.github.com/petterreinholdtsen/meshfx-node/master/build-rpi-mesh-node
221 % sudo bash -x ./build-rpi-mesh-node
> build.log
2>&1
222 % dd if=/root/rpi/rpi_basic_jessie_$(date +%Y%m%d).img of=/dev/mmcblk0 bs=
1M
224 </pre
></p
>
226 <p
>Booting with the resulting SD card on a Raspberry PI with a USB
227 wifi card inserted should give you a mesh node. At least it does for
228 me with a the wifi card I am using. The default mesh settings are the
229 ones used by the Oslo mesh project at Hackeriet, as I mentioned in
230 <a href=
"https://people.skolelinux.org/pere/blog/Oslo_community_mesh_network___with_NUUG_and_Hackeriet_at_Hausmania.html
">an
231 earlier blog post about this mesh testing
</a
>.
</p
>
233 <p
>The mesh node was not horribly expensive either. I bought
234 everything over the counter in shops nearby. If I had ordered online
235 from the lowest bidder, the price should be significantly lower:
</p
>
237 <p
><table
>
239 <tr
><th
>Supplier
</th
><th
>Model
</th
><th
>NOK
</th
></tr
>
240 <tr
><td
>Teknikkmagasinet
</td
><td
>Raspberry Pi model B
</td
><td
>349.90</td
></tr
>
241 <tr
><td
>Teknikkmagasinet
</td
><td
>Raspberry Pi type B case
</td
><td
>99.90</td
></tr
>
242 <tr
><td
>Lefdal
</td
><td
>Jensen Air:Link
25150</td
><td
>295.-
</td
></tr
>
243 <tr
><td
>Clas Ohlson
</td
><td
>Kingston
16 GB SD card
</td
><td
>199.-
</td
></tr
>
244 <tr
><td
>Total cost
</td
><td
></td
><td
>943.80</td
></tr
>
246 </table
></p
>
248 <p
>Now my mesh network at home consist of one laptop in the basement
249 connected to my production network, one Raspberry Pi node on the
1th
250 floor that can be seen by my neighbor across the park, and one
251 play-node I use to develop the image building script. And some times
252 I hook up my work horse laptop to the mesh to test it. I look forward
253 to figuring out what kind of latency the batman-adv setup will give,
254 and how much packet loss we will experience around the park. :)
</p
>
259 <title>Perl library to control the Spykee robot moved to github
</title>
260 <link>http://www.hungry.com/~pere/blog/Perl_library_to_control_the_Spykee_robot_moved_to_github.html
</link>
261 <guid isPermaLink=
"true">http://www.hungry.com/~pere/blog/Perl_library_to_control_the_Spykee_robot_moved_to_github.html
</guid>
262 <pubDate>Sat,
19 Oct
2013 10:
20:
00 +
0200</pubDate>
263 <description><p
>Back in
2010, I created a Perl library to talk to
264 <a href=
"http://en.wikipedia.org/wiki/Spykee
">the Spykee robot
</a
>
265 (with two belts, wifi, USB and Linux) and made it available from my
266 web page. Today I concluded that it should move to a site that is
267 easier to use to cooperate with others, and moved it to github. If
268 you got a Spykee robot, you might want to check out
269 <a href=
"https://github.com/petterreinholdtsen/libspykee-perl
">the
270 libspykee-perl github repository
</a
>.
</p
>
275 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
276 <link>http://www.hungry.com/~pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html
</link>
277 <guid isPermaLink=
"true">http://www.hungry.com/~pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html
</guid>
278 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
279 <description><p
>The last few days I came across a few good causes that should get
280 wider attention. I recommend signing and donating to each one of
283 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
284 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
285 Women program which is a Google Summer of Code like initiative to get
286 more women involved in free software. One debian sponsor has offered
287 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
288 earmarked
</a
> for this initiative. I donated a few minutes ago, and
289 hope you will to. :)
</p
>
291 <p
>And the Electronic Frontier Foundation just announced plans to
292 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
293 documentaries about the excessive spying
</a
> on every Internet user that
294 take place these days, and their need to fund the work. I
've already
295 donated. Are you next?
</p
>
297 <p
>For my Norwegian audience, the organisation Studentenes og
298 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
299 statement under the heading
300 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
301 Access
</a
> for those of us asking for more focus on open access in the
302 Norwegian government. So far
499 signatures. I hope you will sign it
308 <title>Oslo community mesh network - with NUUG and Hackeriet at Hausmania
</title>
309 <link>http://www.hungry.com/~pere/blog/Oslo_community_mesh_network___with_NUUG_and_Hackeriet_at_Hausmania.html
</link>
310 <guid isPermaLink=
"true">http://www.hungry.com/~pere/blog/Oslo_community_mesh_network___with_NUUG_and_Hackeriet_at_Hausmania.html
</guid>
311 <pubDate>Fri,
11 Oct
2013 14:
10:
00 +
0200</pubDate>
312 <description><p
>Wireless mesh networks are self organising and self healing
313 networks that can be used to connect computers across small and large
314 areas, depending on the radio technology used. Normal wifi equipment
315 can be used to create home made radio networks, and there are several
316 successful examples like
317 <a href=
"http://www.freifunk.net/
">Freifunk
</a
> and
318 <a href=
"http://www.awmn.net/
">Athens Wireless Metropolitan Network
</a
>
320 <a href=
"http://en.wikipedia.org/wiki/List_of_wireless_community_networks_by_region#Greece
">wikipedia
321 for a large list
</a
>) around the globe. To give you an idea how it
322 work, check out the nice overview of the Kiel Freifunk community which
323 can be seen from their
324 <a href=
"http://freifunk.in-kiel.de/ffmap/nodes.html
">dynamically
325 updated node graph and map
</a
>, where one can see how the mesh nodes
326 automatically handle routing and recover from nodes disappearing.
327 There is also a small community mesh network group in Oslo, Norway,
328 and that is the main topic of this blog post.
</p
>
330 <p
>I
've wanted to check out mesh networks for a while now, and hoped
331 to do it as part of my involvement with the
<a
332 href=
"http://www.nuug.no/
">NUUG member organisation
</a
> community, and
333 my recent involvement in
334 <a href=
"https://wiki.debian.org/FreedomBox
">the Freedombox project
</a
>
335 finally lead me to give mesh networks some priority, as I suspect a
336 Freedombox should use mesh networks to connect neighbours and family
337 when possible, given that most communication between people are
338 between those nearby (as shown for example by research on Facebook
339 communication patterns). It also allow people to communicate without
340 any central hub to tap into for those that want to listen in on the
341 private communication of citizens, which have become more and more
342 important over the years.
</p
>
344 <p
>So far I have only been able to find one group of people in Oslo
345 working on community mesh networks, over at the hack space
346 <a href=
"http://hackeriet.no/
">Hackeriet
</a
> at Husmania. They seem to
347 have started with some Freifunk based effort using OLSR, called
348 <a href=
"http://oslo.freifunk.net/index.php?title=Main_Page
">the Oslo
349 Freifunk project
</a
>, but that effort is now dead and the people
350 behind it have moved on to a batman-adv based system called
351 <a href=
"http://meshfx.org/trac
">meshfx
</a
>. Unfortunately the wiki
352 site for the Oslo Freifunk project is no longer possible to update to
353 reflect this fact, so the old project page can
't be updated to point to
354 the new project. A while back, the people at Hackeriet invited people
355 from the Freifunk community to Oslo to talk about mesh networks. I
356 came across this video where Hans Jørgen Lysglimt interview the
357 speakers about this talk (from
358 <a href=
"https://www.youtube.com/watch?v=N2Kd7CLkhSY
">youtube
</a
>):
</p
>
360 <p
><iframe width=
"420" height=
"315" src=
"https://www.youtube.com/embed/N2Kd7CLkhSY
" frameborder=
"0" allowfullscreen
></iframe
></p
>
362 <p
>I mentioned OLSR and batman-adv, which are mesh routing protocols.
363 There are heaps of different protocols, and I am still struggling to
364 figure out which one would be
"best
" for some definitions of best, but
365 given that the community mesh group in Oslo is so small, I believe it
366 is best to hook up with the existing one instead of trying to create a
367 completely different setup, and thus I have decided to focus on
368 batman-adv for now. It sure help me to know that the very cool
369 <a href=
"http://www.servalproject.org/
">Serval project in Australia
</a
>
370 is using batman-adv as their meshing technology when it create a self
371 organizing and self healing telephony system for disaster areas and
372 less industrialized communities. Check out this cool video presenting
374 <a href=
"https://www.youtube.com/watch?v=
30qNfzJCQOA
">youtube
</a
>):
</p
>
376 <p
><iframe width=
"560" height=
"315" src=
"https://www.youtube.com/embed/
30qNfzJCQOA
" frameborder=
"0" allowfullscreen
></iframe
></p
>
378 <p
>According to the wikipedia page on
379 <a href=
"http://en.wikipedia.org/wiki/Wireless_mesh_network
">Wireless
380 mesh network
</a
> there are around
70 competing schemes for routing
381 packets across mesh networks, and OLSR, B.A.T.M.A.N. and
382 B.A.T.M.A.N. advanced are protocols used by several free software
383 based community mesh networks.
</p
>
385 <p
>The batman-adv protocol is a bit special, as it provide layer
2
386 (as in ethernet ) routing, allowing ipv4 and ipv6 to work on the same
387 network. One way to think about it is that it provide a mesh based
388 vlan you can bridge to or handle like any other vlan connected to your
389 computer. The required drivers are already in the Linux kernel at
390 least since Debian Wheezy, and it is fairly easy to set up. A
391 <a href=
"http://www.open-mesh.org/projects/batman-adv/wiki/Quick-start-guide
">good
392 introduction
</a
> is available from the Open Mesh project. These are
393 the key settings needed to join the Oslo meshfx network:
</p
>
395 <p
><table
>
396 <tr
><th
>Setting
</th
><th
>Value
</th
></tr
>
397 <tr
><td
>Protocol / kernel module
</td
><td
>batman-adv
</td
></tr
>
398 <tr
><td
>ESSID
</td
><td
>meshfx@hackeriet
</td
></tr
>
399 <td
>Channel / Frequency
</td
><td
>11 /
2462</td
></tr
>
400 <td
>Cell ID
</td
><td
>02:BA:
00:
00:
00:
01</td
>
401 </table
></p
>
403 <p
>The reason for setting ad-hoc wifi Cell ID is to work around bugs
404 in firmware used in wifi card and wifi drivers. (See a nice post from
406 "<a href=
"http://tiebing.blogspot.no/
2009/
12/ad-hoc-cell-splitting-re-post-original.html
">Information
407 about cell-id splitting, stuck beacons, and failed IBSS merges!
</a
>
408 for details.) When these settings are activated and you have some
409 other mesh node nearby, your computer will be connected to the mesh
410 network and can communicate with any mesh node that is connected to
411 any of the nodes in your network of nodes. :)
</p
>
413 <p
>My initial plan was to reuse my old Linksys WRT54GL as a mesh node,
414 but that seem to be very hard, as I have not been able to locate a
415 firmware supporting batman-adv. If anyone know how to use that old
416 wifi access point with batman-adv these days, please let me know.
</p
>
418 <p
>If you find this project interesting and want to join, please join
419 us on IRC, either channel
420 <a href=
"irc://irc.freenode.net/#oslohackerspace
">#oslohackerspace
</a
>
421 or
<a href=
"irc://irc.freenode.net/#nuug
">#nuug
</a
> on
422 irc.freenode.net.
</p
>
424 <p
>While investigating mesh networks in Oslo, I came across an old
425 research paper from the university of Stavanger and Telenor Research
426 and Innovation called
427 <a href=
"http://folk.uio.no/paalee/publications/netrel-egeland-iswcs-
2008.pdf
">The
428 reliability of wireless backhaul mesh networks
</a
> and elsewhere
429 learned that Telenor have been experimenting with mesh networks at
430 Grünerløkka in Oslo. So mesh networks are also interesting for
431 commercial companies, even though Telenor discovered that it was hard
432 to figure out a good business plan for mesh networking and as far as I
433 know have closed down the experiment. Perhaps Telenor or others would
434 be interested in a cooperation?
</p
>
436 <p
><strong
>Update
2013-
10-
12</strong
>: I was just
437 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2013-October/
005900.html
">told
438 by the Serval project developers
</a
> that they no longer use
439 batman-adv (but are compatible with it), but their own crypto based
440 mesh system.
</p
>
445 <title>Skolelinux / Debian Edu
7.1 install and overview video from Marcelo Salvador
</title>
446 <link>http://www.hungry.com/~pere/blog/Skolelinux___Debian_Edu_7_1_install_and_overview_video_from_Marcelo_Salvador.html
</link>
447 <guid isPermaLink=
"true">http://www.hungry.com/~pere/blog/Skolelinux___Debian_Edu_7_1_install_and_overview_video_from_Marcelo_Salvador.html
</guid>
448 <pubDate>Tue,
8 Oct
2013 17:
10:
00 +
0200</pubDate>
449 <description><p
>The other day I was pleased and surprised to discover that Marcelo
450 Salvador had published a
451 <a href=
"https://www.youtube.com/watch?v=w-GgpdqgLFc
">video on
452 Youtube
</a
> showing how to install the standalone Debian Edu /
453 Skolelinux profile. This is the profile intended for use at home or
454 on laptops that should not be integrated into the provided network
455 services (no central home directory, no Kerberos / LDAP directory etc,
456 in other word a single user machine). The result is
11 minutes long,
457 and show some user applications (seem to be rather randomly picked).
458 Missed a few of my favorites like celestia, planets and chromium
459 showing the
<a href=
"http://www.zygotebody.com/
">Zygote Body
3D model
460 of the human body
</a
>, but I guess he did not know about those or find
461 other programs more interesting. :) And the video do not show the
462 advantages I believe is one of the most valuable featuers in Debian
463 Edu, its central school server making it possible to run hundreds of
464 computers without hard drives by installing one central
465 <a href=
"http://www.ltsp.org/
">LTSP server
</a
>.
</p
>
467 <p
>Anyway, check out the video, embedded below and linked to above:
</p
>
469 <iframe width=
"420" height=
"315" src=
"http://www.youtube.com/embed/w-GgpdqgLFc
" frameborder=
"0" allowfullscreen
></iframe
>
471 <p
>Are there other nice videos demonstrating Skolelinux? Please let
472 me know. :)
</p
>