-<p>Jeg kjøpte nettopp to
-<a href="http://www.spykee-robot.com/">Spykee</a>-roboter, for test og
-leking. Kjøpte to da det var så billige, og gir meg mulighet til å
-eksperimentere uten å være veldig redd for å ødelegge alt ved å bytte
-ut firmware og slikt. Oppdaget at lekebutikken på Bryn senter hadde
-en liten stabel på lager som de ikke hadde klart å selge ut etter
-fjorårets juleinnkjøp, og var villig til å selge for en femtedel av
-vanlig pris. Jeg, Ronny og Jarle har skaffet oss restbeholdningen, og
-det blir morsomt å se hva vi får ut av dette.</p>
-
-<p>Roboten har belter styrt av to motorer, kamera, høytaler, mikrofon
-og wifi-tilkobling. Det hele styrt av en GPL-lisensiert databoks som
-jeg mistenker kjører linux. Firmware-kildekoden ble visst publisert i
-mai. Eneste utfordringen er at kontroller-programvaren kun finnes til
-Windows, men det må en kunne jobbe seg rundt når vi har kildekoden til
-firmwaren. :)</p>
-
-<ul>
-<li><a href="http://en.wikipedia.org/wiki/Spykee">Wikipedia-oppføring</a></li>
-<li><a href=http://www.spykeeworld.com/spykee/US/freeSoftware.html">Nedlasting av firmware-kilden</a></li>
-<li><a href="http://wiki.nuug.no/grupper/robot">prosjektwiki hos NUUG</a></li>
-</ul>
-</description>
- </item>
-
- <item>
- <title>Rob Weir: How to Crush Dissent</title>
- <link>http://people.skolelinux.org/pere/blog/Rob_Weir__How_to_Crush_Dissent.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Rob_Weir__How_to_Crush_Dissent.html</guid>
- <pubDate>Sun, 15 Aug 2010 22:20:00 +0200</pubDate>
- <description>
-<p>I found the notes from Rob Weir on
-<a href="http://feedproxy.google.com/~r/robweir/antic-atom/~3/VGb23-kta8c/how-to-crush-dissent.html">how
-to crush dissent</a> matching my own thoughts on the matter quite
-well. Highly recommended for those wondering which road our society
-should go down. In my view we have been heading the wrong way for a
-long time.</p>
-</description>
- </item>
-
- <item>
- <title>No hardcoded config on Debian Edu clients</title>
- <link>http://people.skolelinux.org/pere/blog/No_hardcoded_config_on_Debian_Edu_clients.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_hardcoded_config_on_Debian_Edu_clients.html</guid>
- <pubDate>Mon, 9 Aug 2010 20:15:00 +0200</pubDate>
- <description>
-<p>As reported earlier, the last few days I have looked at how Debian
-Edu clients are configured, and tried to get rid of all hardcoded
-configuration settings on the clients. I believe the work to be
-mostly done, and the clients seem to work just fine with dynamically
-generated configuration.</p>
-
-<p>What is the point, you might ask? The point is to allow a Debian
-Edu desktop to integrate into an existing network infrastructure
-without any manual configuration.</p>
-
-<p>This is what happens when installing a Debian Edu client here at
-the University of Oslo using PXE. With the PXE installation, I am
-asked for language (Norwegian Bokmål), locality (Norway) and keyboard
-layout (no-latin1), Debian Edu profile (Roaming Workstation), if I
-accept to reformat the hard drive (yes), if I want to submit info to
-popcon.debian.org (no) and root password (secret). After answering
-these questions, the installer goes ahead and does its thing, and
-after around 50 minutes it is done. I press enter to finish the
-installation, and the machine reboots into KDE. When the machine is
-ready and kdm asks for login information, I enter my university
-username and password, am told by kdm that a local home directory has
-been created and that I must log in again, and finally log in with the
-same username and password to the KDE 4.4 desktop. At no point during
-this process did it ask for university specific settings, and all the
-required configuration was dynamically detected using information
-fetched via DHCP and DNS. The roaming workstation is now ready for
-use.</p>
-
-<p>How was this done, you might wonder? First of all, here is the
-list of things that need to be configured on the client to get it
-working properly out of the box:</p>
-
-<ul>
-<li>IP address/netmask and DNS server.</li>
-<li>Web proxy URL.</li>
-<li>LDAP server for NSS directory information (user, group, etc).</li>
-<li>Kerberos server for PAM password checking.</li>
-<li>SMB mount point to access the network home directory. (*)</li>
-<li>Central syslog server to send syslog messages to. (*)</li>
-<li>Sitesummary collector URL to submit info to central server. (*)</li>
-</ul>
-
-<p>(Hm, did I forget anything? Let me knew if I did.)</p>
-
-<p>The points marked (*) are not required to be able to use the
-machine, but needed to provide central storage and allowing system
-administrators to track their machines. Since yesterday, everything
-but the sitesummary collector URL is dynamically discovered at boot
-and installation time in the svn version of Debian Edu.</p>
-
-<p>The IP and DNS setup is fetched during boot using DHCP as usual.
-When a DHCP update arrives, the proxy setup is updated by looking for
-http://wpat/wpad.dat and using the content of this WPAD file to
-configure the http and ftp proxy in /etc/environment and
-/etc/apt/apt.conf. I decided to update the proxy setup using a DHCP
-hook to ensure that the client stops using the Debian Edu proxy when
-it is moved outside the Debian Edu network, and instead uses any local
-proxy present on the new network when it moves around.</p>
-
-<p>The DNS names of the LDAP, Kerberos and syslog server and related
-configuration are generated using DNS information at boot. First the
-installer looks for a host named ldap in the current DNS domain. If
-not found, it looks for _ldap._tcp SRV records in DNS instead. If an
-LDAP server is found, its root DSE entry is requested and the
-attributes namingContexts and defaultNamingContext are used to
-determine which LDAP base to use for NSS. If there are several
-namingContexts attibutes and the defaultNamingContext is present, that
-LDAP subtree is used as the base. If defaultNamingContext is missing,
-the subtrees listed as namingContexts are searched in sequence for any
-object with class posixAccount or posixGroup, and the first one with
-such an object is used as the LDAP base. For Kerberos, a similar
-search is done by first looking for a host named kerberos, and then
-for the _kerberos._tcp SRV record. I've been unable to find a way to
-look up the Kerberos realm, so for this the upper case string of the
-current DNS domain is used.</p>
-
-<p>For the syslog server, the hosts syslog and loghost are searched
-for, and the _syslog._udp SRV record is consulted if no such host is
-found. This algorithm works for both Debian Edu and the University of
-Oslo. A similar strategy would work for locating the sitesummary
-server, but have not been implemented yet. I decided to fetch and
-save these settings during installation, to make sure moving to a
-different network does not change the set of users being allowed to
-log in nor the passwords required to log in. Usernames and passwords
-will be cached by sssd when the user logs in on the Debian Edu
-network, and will not change as the laptop move around. For a
-non-roaming machine, there is no caching, but given that it is
-supposed to stay in place it should not matter much. Perhaps we
-should switch those to use sssd too?</p>
-
-<p>The user's SMB mount point for the network home directory is
-located when the user logs in for the first time. The LDAP server is
-consulted to look for the user's LDAP object and the sambaHomePath
-attribute is used if found. If it isn't found, the home directory
-path fetched from NSS is used instead. Assuming the path is of the
-form /site/server/directory/username, the second part is looked up in
-DNS and used to generate a SMB URL of the form
-smb://server.domain/username. This algorithm works for both Debian
-edu and the University of Oslo. Perhaps there are better attributes
-to use or a better algorithm that works for more sites, but this will
-do for now. :)</p>
-
-<p>This work should make it easier to integrate the Debian Edu clients
-into any LDAP/Kerberos infrastructure, and make the current setup even
-more flexible than before. I suspect it will also work for thin
-client servers, allowing one to easily set up LTSP and hook it into a
-existing network infrastructure, but I have not had time to test this
-yet.</p>
-
-<p>If you want to help out with implementing these things for Debian
-Edu, please contact us on debian-edu@lists.debian.org.</p>
-
-<p>Update 2010-08-09: Simon Farnsworth gave me a heads-up on how to
-detect Kerberos realm from DNS, by looking for _kerberos TXT entries
-before falling back to the upper case DNS domain name. Will have to
-implement it for Debian Edu. :)</p>
+<p>Jeg fortsetter min intervjuserie med folk i
+<a href="http://www.skolelinux.org/">Skolelinuxprosjektet</a>. Denne
+gang er det en av folkene som har vært med lenge og som har tatt i
+bruk Skolelinux på alle skolene i Narvik kommune som skal i ilden.
+Han er styremedlem i
+<a href="http://www.friprogramvareiskolen.no/">foreningen
+FRISK</a>.</p>
+
+<p><strong>Hvem er du, og hva driver du med til daglig?</strong></p>
+
+<p>Mitt navn er Viggo Fedreheim, og jeg er pedagogisk og teknisk
+IKT-veileder for alle skoler i Narvik kommune. Jeg drifter totalt 17
+servere basert på Skolelinux og Debian. Jeg holder i tillegg noen kurs
+mellom all driftingen. For tiden arbeider jeg med en sentral
+LDAP-tjener for alle skoleservere samt våre Moodle- og
+Joomla-installasjoner.</p>
+
+<p><strong>Hvordan kom du i kontakt med Skolelinux-prosjektet?</strong></p>
+
+<p>Gjennom en eller annen nettavis i 2001 der var det skrevet om
+Skolelinux. Artikkelen ga meg lyst til å prøve ut systemet.</p>
+
+<p>Det startet i 2002 ved at jeg installerte en av de første utgavene
+av Skolelinux på en standard pc på Solneset skole i Tromsø. Denne var
+oppe fram til desember 2003 da jeg sluttet på den skolen og begynte i
+ny jobb i Narvik kommune.</p>
+
+<p> I Narvik kommune var det i 2004 kun 2 servere på da totalt 15
+skoler. Disse var Windows NT baserte. På disse to skolene var det lite
+med maskiner. Jobben med å få Narvik Kommune opp på akseptabelt nivå
+virket å være formidabel. Men med hjelp av gode kollegaer og leder
+skrev jeg en IKT plan for Narvik kommune som ble vedtatt av politikere
+i august 2004. I denne planen ble det bestemt at Narvik kommune skulle
+bruke Skolelinux. Her ble det også satt av midler til kabling av god
+infrastruktur på alle skoler samt innkjøp av nye datamaskiner. Så i
+dag har vi 17 servere hvorav 13 er på Skolelinux, med ca 1500 klienter
+basert på tynne, "halvtykke" og et stort antall bærbare pcer basert på
+Kubuntu.</p>
+
+<p><strong>Hva er fordelene med Skolelinux slik du ser det?</strong></p>
+
+<p>Lisenskostnader, driftkostnader og hardwarekrav som er mye lavere
+enn for andre systemer.</p>
+
+<p><strong>Hva er ulempene med Skolelinux slik du ser det?</strong></p>
+
+<p>Pedagogiske programvare som ikke fungerer mot Linux. En Stoooor
+flaskehals og som gjør at Linux kanskje ikke blir valgt andre
+plasser.</p>
+
+<p>Eksempler er Relemo, Lindys (lingit sine programmer), 5plus
+(matematikk). Disse er programmer som ikke lar seg kjøre i Linux.</p>
+
+<p> Men det ser ut for at mange leverandører går over til mer
+nettbaserte programmer istedet for å installere lokalt. Dette med
+enkelte leverandører som ikke kan levere programmer til Linux er et
+lite problem og over tid tror jeg at denne barrieren er borte.</p>
+
+<p><strong>Hvilken fri programvare bruker du til daglig?</strong></p>
+
+<p>Kjører Kubuntu på laptoper, Debian squeeze på stasjonær
+kontorpc. Ut over dette arbeder jeg svært mye via konsoll mot andre
+servere.</p>