<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Dugnadsnett_for_alle_stiller_p__Oslo_Maker_Faire_i_januar_2014.html">Dugnadsnett for alle stiller på Oslo Maker Faire i januar 2014</a></div>
- <div class="date">10th December 2013</div>
- <div class="body"><p>Helga 18. og 19. januar 2014 arrangeres
-<a href="http://makerfaireoslo.no/no/program/dugnadsnett">Oslo Maker
-Faire</a>, og <a href="http://www.dugnadsnett.no/">Dugnadsnett for
-alle</a> har fått plass! Planen er å ha et bord med en plakat der vi
-forteller om hva Dugnadsnett for alle er for noe, og et lite verksted
-der vi hjelper folk som er interessert i å få opp sin egen mesh-node.
-Jeg gleder meg til å se hvordan prosjektet blir mottatt der.</p>
-
-<p>Målet med dugnadsnett for alle i Oslo er å få på plass et datanett
-for kommunikasjon ved hjelp av radio-repeaterstasjoner (kalt
-mesh-noder) som gjør at en kan direkte kommunisere med slekt, venner
-og bekjente i Oslo via andre som deltar i dugnadsnettet, samt gjøre
-det mulig komme ut på internett via dugnadsnettet. Første delmål er å
-kunne sende SMS-meldinger vha. IP-telefoni løsningen
-<a href="http://www.servalproject.org/">Serval project</a> mellom
-deltagerne i Dugnadsnett for alle i Oslo. Formålet er å ta tilbake
-kontrollen over egen nett-infrastruktur og gjøre det dyrere å bedrive
-massiv innsamling av informasjon om borgernes bruk av datanett.</p>
-
-<p>Høres dette interessant ut? Bli med på prosjektet, fortell oss
-hvor du kunne tenke deg å sette opp en radio-repeater (slik at folk i
-nærheten kan finne hverandre ved hjelp av
-<a href="http://flynor.net/mesh/mesh.php">kartet over planlagte og
-eksisterende radio-repeatere</A>), bli med på epostlisten
-<a href="http://lists.nuug.no/mailman/listinfo/dugnadsnett">dugnadsnett
-(at) nuug.no</a> og stikk innom
-<a href="irc://irc.freenode.net/#dugnadsnett.no">IRC-kanalen
-#dugnadsnett.no</a>. Så langt er det planlagt over 40
-radio-repeatere, med VPN-forbindelser via Internet for å la de delene
-av nettet som ikke når hverandre via radio kunne snakke med hverandre
-likevel.</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/Opphavsretts_status_for__Empty_Socks__fra_1927_.html">Opphavsretts-status for «Empty Socks» fra 1927?</a></div>
+ <div class="date">12th December 2014</div>
+ <div class="body"><p>For noen dager siden
+<a href="http://www.nb.no/Hva-skjer/Aktuelt/Nyheter/Tapt-filmskatt-fra-Disney-funnet-i-Nasjonalbiblioteket">annonserte
+Nasjonalbiblioteket gladnyheten</a> om at de i sine arkiver hadde
+funnet et nitratfilm-eksemplar av en 87 år gammel Disney-film ved navn
+Empty Socks, en film som tidligere var antatt tapt og der det i følge
+nyhetsmeldinger var kun ca. 25 sekunder bevart for ettertiden.
+Nasjonalbiblioteket hadde 5 minutter og 30 sekunder av filmen i sitt
+magasin. Dette er flott for bevaringen av verdens kulturarv. 5,5
+minutter mindre tapt enn vi trodde av får felles historie.</p>
+
+<p>Men hvordan kunne filmen gå tapt, når arkivlovene i USA krevde at
+publiserte filmer på den tiden ble deponert i bibliotek? Forklaringen
+har jeg fra Lawrence Lessig og boken
+<a href="http://free-culture.cc/">Free Culture</a>, som jeg holder på
+<a href="https://github.com/petterreinholdtsen/free-culture-lessig">å
+oversette til norsk</a>:</p>
+
+<p><blockquote>
+<p>Dette er delvis på grunn av loven. Opphavsrettseiere var tidlig i
+ amerikansk opphavsrettslov nødt til å deponere kopier av sine verk i
+ biblioteker. Disse kopiene skulle både sikre spredning av kunnskap,
+ og sikre at det fantes en kopi av verket tilgjengelig når vernetiden
+ utløp, slik at andre kunne få tilgang til og kopiere verket.</p>
+
+<p>Disse reglene gjaldt også for filmer. Men i 1915 gjorde
+ kongressbiblioteket et unntak for film. Filmer kunne bli
+ opphavsrettsbeskyttet så lenge det ble gjort slik deponering. Men
+ filmskaperne fikk så lov til å låne tilbake de deponerte filmene -
+ så lenge de ville uten noe kostnad. Bare i 1915 var det mer enn 5475
+ filmer deponert og “lånt tilbake”. Dermed var det ikke noe eksemplar
+ i noe bibliotek når vernetiden til filmen utløp. Eksemplaret
+ eksisterer - hvis den finnes i det hele tatt - i arkivbiblioteket
+ til filmselskapet.</p>
+</blockquote></p>
+
+<p>Nyheten gjorde meg nysgjerrig på om filmen kunne være falt i det
+fri. En 87 år gammel film kunne jo tenkes å ha blitt en del av
+allemannseiet, slik at vi alle kan bruke den til å bygge videre på vår
+felles kultur uten å måtte be om tillatelse - slik Walt Disney gjorde
+det i starten av sin karriere. Jeg spurte nasjonalbiblioteket, og de
+sa nei. Hvordan kan det ha seg med en så gammel film? Jeg besteme
+meg for å undersøke nærmere. En kan finne informasjon om den norske
+vernetiden på
+<a href="https://lovdata.no/dokument/NL/lov/1961-05-12-2">Lovdata</a>
+og </a>Wikipedia</A>. Her er et relevant <a
+href="https://no.wikipedia.org/wiki/Opphavsrett#Vernetid">utsnitt fra
+siden om opphavsrett i den norske Wikipedia</a>:</p>
+
+<p><blockquote>
+ Ifølge åndsverkloven §§ 40-41 utløper vernetiden for et åndsverk 70
+ år etter utløpet av opphavspersonens dødsår. [...] For filmverk
+ gjelder særlige regler: Her kommer ikke alle mulige opphavspersoner
+ i betraktning, men kun hovedregissøren, manusforfatteren,
+ dialogforfatteren og komponisten av filmmusikken. Vernetiden
+ begynner å løpe etter utgangen av dødsåret til den lengstlevende av
+ disse. [...] Der opphavspersonen er ukjent, utløper opphavsretten 70
+ år etter første kjente offentliggjørelse av verket. Det er kun de
+ økonomiske rettighetene som faller bort i det vernetiden er
+ utløpt. De ideelle rettighetene må fortsatt respekteres, noe som
+ blant annet innebærer at man plikter å navngi opphavspersonen ved
+ tilgjengeliggjøring.
+</blockquote></p>
+
+<p>I følge nettstedet
+<a href="http://www.disneyshorts.org/shorts.aspx?shortID=75">The
+Encyclopedia of Disney Animated Shorts</a> er følgende personer gitt
+æren for denne kortfilmen:</p>
+
+<dl>
+
+<dt>Regissør</dt>
+<dd><a href="https://en.wikipedia.org/wiki/Walt_Disney">Walt Disney</a> (1901-12-05 – 1966-12-15) +70 år = 2037</dd>
+
+<dt>Animasjon
+<dd><a href="https://en.wikipedia.org/wiki/Ub_Iwerks">Ub Iwerks</a> (1901-03-24 – 1971-07-07) +70 år = 2042
+<br><a href="https://en.wikipedia.org/wiki/Rollin_Hamilton">Rollin "Ham" Hamilton</a> (1898-10-28 - 1951-06-03) +70 år = 2022
+<br><a href="https://en.wikipedia.org/wiki/Harman_and_Ising">Hugh Harman</a> (1903-08-31 – 1982-11-25) +70 år = 2053</dd>
+
+<dt>Kamera
+<dd>Mike Marcus (?-?)</dd>
+
+</dl>
+
+<p>Alle fødsels- og dødsdatoene er fra engelske Wikipedia. Det er
+ikke oppgitt navn på manusforfatter, dialogforfatter og komponist, men
+jeg mistenker at tegnerne vil få opphavsrettigheter på tegnefilmer her
+i Norge, og tar derfor med disse. Kameramannen vil ikke få noen
+rettigheter så vidt jeg forstår, og er derfor ignorert her.</p>
+
+<p>Slik jeg forstår den norske opphavsretten vil dermed dette
+filmverket bli allemannseie (også kalt å falle i det fri) i 2053, 126
+år etter at det ble utgitt. Hvis kun regissørens rettigheter er
+relevante, vil det skje i 2037, 110 år etter at det ble utgitt. Etter
+det vil enhver kunne dele det med alle de har lyst til, fremføre det
+offentlig eller klippe og lime i det for å lage sin egen film basert
+på det - helt uten å måtte spørre noen om lov.</p>
+
+<p>Måtte så Nasjonalbiblioteket spørre om lov før de kunne kopiere
+sitt nitrat-eksemplar over på mer varig format? Nei, heldigvis.
+Åndsverklovens § 16 sier at arkiv, bibliotek, museer og undervisnings-
+og forskningsinstitusjoner har rett til å fremstille eksemplar av verk
+for konserverings- og sikringsformål og andre særskilte formål.</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Klaus_Knopper.html">Debian Edu interview: Klaus Knopper</a></div>
- <div class="date"> 6th December 2013</div>
- <div class="body"><p>It has been a while since I managed to publish the last interview,
-but the <a href="http://www.skolelinux.org/">Debian Edu /
-Skolelinux</a> community is still going strong, and yesterday we even
-had a new school administrator show up on
-<a href="irc://irc.debian.org/#debian-edu">#debian-edu</a> to share
-his success story with installing Debian Edu at their school. This
-time I have been able to get some helpful comments from the creator of
-Knoppix, Klaus Knopper, who was involved in a Skolelinux project in
-Germany a few years ago.</p>
-
-<p><strong>Who are you, and how do you spend your days?</strong></p>
-
-<p>I am Klaus Knopper. I have a master degree in electrical
-engineering, and is currently professor in information management at
-the university of applied sciences Kaiserslautern / Germany and
-freelance Open Source software developer and consultant.</p>
-
-<p>All of this is pretty much of the work I spend my days with. Apart
-from teaching, I'm also conducting some more or less experimental
-projects like the <a href="http://www.knoppix.org">Knoppix GNU/Linux live
-system</a> (Debian-based like Skolelinux),
-<a href="http://www.knopper.net/knoppix-adriane/index-en.html">ADRIANE</a>
-(a blind-friendly talking desktop system) and
-<a href="http://www.knopper.net/linbo/index-en.html">LINBO</a>
-(Linux-based network boot console, a fast remote install and repair
-system supporting various operating systems).</p>
-
-<p><strong>How did you get in contact with the Skolelinux / Debian Edu
-project?</strong></p>
-
-<p>The credit for this have to go to Kurt Gramlich, who is the German
-coordinator for Skolelinux. We were looking for an all-in-one open
-source community-supported distribution for schools, and Kurt
-introduced us to Skolelinux for this purpose.</p>
-
-<p><strong>What do you see as the advantages of Skolelinux / Debian
-Edu?</strong></p>
-
-<ul>
- <li>Quick installation,</li>
- <li>works (almost) out of the box,</li>
- <li>contains many useful software packages for teaching and learning,</li>
- <li>is a purely community-based distro and not controlled by a
- single company,</li>
- <li>has a large number of supporters and teachers who share their
- experience and problem solutions.</li>
-</ul>
-
-<p><strong>What do you see as the disadvantages of Skolelinux / Debian
-Edu?</strong></p>
-
-<ul>
- <li>Skolelinux is - as we had to learn - not easily upgradable to
- the next version. Opposed to its genuine Debian base, upgrading to
- a new version means a full new installation from scratch to get it
- working again reliably.
-
- <li>Skolelinux is based on Debian/stable, and therefore always a
- little outdated in terms of program versions compared to Edubuntu or
- similar educational Linux distros, which rather use Debian/testing
- as their base.
-
- <li>Skolelinux has some very self-opinionated and stubborn default
- configuration which in my opinion adds unnecessary complexity and is
- not always suitable for a schools needs, the preset network
- configuration is actually a core definition feature of Skolelinux
- and not easy to change, so schools sometimes have to change their
- network configuration to make it "Skolelinux-compatible".
-
- <li>Some proposed extensions, which were made available as
- contribution, like secure examination mode and lecture material
- distribution and collection, were not accepted into the mainline
- Skolelinux development and are now not easy to maintain in the
- future because of Skolelinux somewhat undeterministic update
- schemes.</li>
-
- <li>Skolelinux has only a very tiny number of base developers
- compared to Debian.</li>
-
-</ul>
-
-<p>For these reasons and experience from our project, I would now
-rather consider using plain Debian for schools next time, until
-Skolelinux is more closely integrated into Debian and becomes
-upgradeable without reinstallation.</p>
-
-<p><strong>Which free software do you use daily?</strong></p>
-
-<p>GNU/Linux with LXDE desktop, bash for interactive dialog and
-programming, texlive for documentation and correspondence,
-occasionally LibreOffice for document format conversion. Various
-programming languages for teaching.</p>
-
-<p><strong>Which strategy do you believe is the right one to use to
-get schools to use free software?</strong></p>
-
-<p>Strong arguments are</p>
-
-<ul>
-
- <li>Knowledge is free, and so should be methods and tools for
- teaching and learning.</li>
-
- <li>Students can learn with and use the same software at school, at
- home, and at their working place without running into license or
- conversion problems.</li>
-
- <li>Closed source or proprietary software hides knowledge rather
- than exposing it, and proprietary software vendors try to bind
- customers to certain products. But teachers need to teach
- science, not products.</li>
-
- <li>If you have everything you for daily work as open source, what
- would you need proprietary software for?</li>
-
-</ul>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html">How to stay with sysvinit in Debian Jessie</a></div>
+ <div class="date">22nd November 2014</div>
+ <div class="body"><p>By now, it is well known that Debian Jessie will not be using
+sysvinit as its boot system by default. But how can one keep using
+sysvinit in Jessie? It is fairly easy, and here are a few recipes,
+courtesy of
+<a href="http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html">Erich
+Schubert</a> and
+<a href="http://smcv.pseudorandom.co.uk/2014/still_universal/">Simon
+McVittie</a>.
+
+<p>If you already are using Wheezy and want to upgrade to Jessie and
+keep sysvinit as your boot system, create a file
+<tt>/etc/apt/preferences.d/use-sysvinit</tt> with this content before
+you upgrade:</p>
+
+<p><blockquote><pre>
+Package: systemd-sysv
+Pin: release o=Debian
+Pin-Priority: -1
+</pre></blockquote><p>
+
+<p>This file content will tell apt and aptitude to not consider
+installing systemd-sysv as part of any installation and upgrade
+solution when resolving dependencies, and thus tell it to avoid
+systemd as a default boot system. The end result should be that the
+upgraded system keep using sysvinit.</p>
+
+<p>If you are installing Jessie for the first time, there is no way to
+get sysvinit installed by default (debootstrap used by
+debian-installer have no option for this), but one can tell the
+installer to switch to sysvinit before the first boot. Either by
+using a kernel argument to the installer, or by adding a line to the
+preseed file used. First, the kernel command line argument:
+
+<p><blockquote><pre>
+preseed/late_command="in-target apt-get install --purge -y sysvinit-core"
+</pre></blockquote><p>
+
+<p>Next, the line to use in a preseed file:</p>
+
+<p><blockquote><pre>
+d-i preseed/late_command string in-target apt-get install -y sysvinit-core
+</pre></blockquote><p>
+
+<p>One can of course also do this after the first boot by installing
+the sysvinit-core package.</p>
+
+<p>I recommend only using sysvinit if you really need it, as the
+sysvinit boot sequence in Debian have several hardware specific bugs
+on Linux caused by the fact that it is unpredictable when hardware
+devices show up during boot. But on the other hand, the new default
+boot system still have a few rough edges I hope will be fixed before
+Jessie is released.</p>
+
+<p>Update 2014-11-26: Inspired by
+<ahref="https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg">a
+blog post by Torsten Glaser</a>, added --purge to the preseed
+line.</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Dugnadsnett_for_alle__a_wireless_community_network_in_Oslo__take_shape.html">Dugnadsnett for alle, a wireless community network in Oslo, take shape</a></div>
- <div class="date">30th November 2013</div>
- <div class="body"><p>If you want the ability to electronically communicate directly with
-your neighbors and friends using a network controlled by your peers in
-stead of centrally controlled by a few corporations, or would like to
-experiment with interesting network technology, the
-<a href="http://www.dugnadsnett.no/">Dugnasnett for alle i Oslo</a>
-might be project for you. 39 mesh nodes are currently being planned,
-in the freshly started initiative from NUUG and Hackeriet to create a
-wireless community network. The work is inspired by
-<a href="http://freifunk.net/">Freifunk</a>,
-<a href="http://www.awmn.net/">Athens Wireless Metropolitan
-Network</a>, <a href="http://en.wikipedia.org/wiki/Roofnet">Roofnet</a>
-and other successful mesh networks around the globe. Two days ago we
-held a workshop to try to get people started on setting up their own
-mesh node, and there we decided to create a new mailing list
-<a href="http://lists.nuug.no/mailman/listinfo/dugnadsnett">dugnadsnett
-(at) nuug.no</a> and IRC channel
-<a href="irc://irc.freenode.net/#dugnadsnett.no">#dugnadsnett.no</a> to
-coordinate the work. See also the NUUG blog post
-<a href="http://www.nuug.no/news/E_postliste_og_IRC_kanal_for_Dugnadsnett_for_alle_i_Oslo.shtml">announcing
-the mailing list and IRC channel</a>.</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/Hvordan_vurderer_regjeringen_H_264_patentutfordringen_.html">Hvordan vurderer regjeringen H.264-patentutfordringen?</a></div>
+ <div class="date">16th November 2014</div>
+ <div class="body"><p>For en stund tilbake spurte jeg Fornyingsdepartementet om hvilke
+juridiske vurderinger rundt patentproblemstillingen som var gjort da
+H.264 ble tatt inn i <a href="http://standard.difi.no/">statens
+referansekatalog over standarder</a>. Stig Hornnes i FAD tipset meg
+om følgende som står i oppsumeringen til høringen om
+referansekatalogen versjon 2.0, som jeg siden ved hjelp av en
+innsynsforespørsel fikk tak i
+<a href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon.pdf">PDF-utgaven av</a>
+datert 2009-06-03 (saksnummer 200803291, saksbehandler Henrik
+Linnestad).</p>
+
+<p>Der står det følgende om problemstillingen:</p>
+
+<p><blockquote>
+<strong>4.4 Patentproblematikk</strong>
+
+<p>NUUG og Opera ser det som særlig viktig at forslagene knyttet til
+lyd og video baserer seg på de royalty-frie standardene Vorbis, Theora
+og FLAC.</p>
+
+<p>Kommentarene relaterer seg til at enkelte standarder er åpne, men
+inneholder tekniske prosedyrer som det i USA (og noen andre land som
+Japan) er gitt patentrettigheter til. I vårt tilfelle berører dette
+spesielt standardene Mp3 og H.264, selv om Politidirektoratet peker på
+at det muligens kan være tilsvarende problematikk også for Theora og
+Vorbis. Dette medfører at det i USA kan kreves royalties for bruk av
+tekniske løsninger knyttet til standardene, et krav som også
+håndheves. Patenter kan imidlertid bare hevdes i de landene hvor
+patentet er gitt, så amerikanske patenter gjelder ikke andre steder
+enn USA.</p>
+
+<p>Spesielt for utvikling av fri programvare er patenter
+problematisk. GPL, en "grunnleggende" lisens for distribusjon av fri
+programvare, avviser at programvare kan distribueres under denne
+lisensen hvis det inneholder referanser til patenterte rutiner som
+utløser krav om royalties. Det er imidlertid uproblematisk å
+distribuere fri programvareløsninger under GPL som benytter de
+aktuelle standardene innen eller mellom land som ikke anerkjenner
+patentene. Derfor finner vi også flere implementeringer av Mp3 og
+H.264 som er fri programvare, lisensiert under GPL.</p>
+
+<p>I Norge og EU er patentlovgivningen langt mer restriktiv enn i USA,
+men det er også her mulig å få patentert metoder for løsning av et
+problem som relaterer seg til databehandling. Det er AIF bekjent ikke
+relevante patenter i EU eller Norge hva gjelder H.264 og Mp3, men
+muligheten for at det finnes patenter uten at det er gjort krav om
+royalties eller at det senere vil gis slike patenter kan ikke helt
+avvises.</p>
+
+<p>AIF mener det er et behov for å gi offentlige virksomheter mulighet
+til å benytte antatt royaltyfrie åpne standarder som et likeverdig
+alternativ eller i tillegg til de markedsledende åpne standardene.</p>
+
+</blockquote></p>
+
+<p>Det ser dermed ikke ut til at de har vurdert patentspørsmålet i
+sammenheng med opphavsrettsvilkår slik de er formulert for f.eks.
+Apple Final Cut Pro, Adobe Premiere Pro, Avid og Sorenson-verktøyene,
+der det kreves brukstillatelse for patenter som ikke er gyldige i
+Norge for å bruke disse verktøyene til annet en personlig og ikke
+kommersiell aktivitet når det gjelder H.264-video. Jeg må nok lete
+videre etter svar på det spørsmålet.</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Hvor_godt_fungerer_Linux_klienter_mot_MS_Exchange_.html">Hvor godt fungerer Linux-klienter mot MS Exchange?</a></div>
- <div class="date">26th November 2013</div>
- <div class="body"><p>Jeg
-<a href="http://people.skolelinux.org/pere/blog/_pent_m_te_p__onsdag_om_bruken_av_Microsoft_Exchange_ved_Universitetet_i_Oslo.html">skrev
-i juni om protestene</a> på planene til min arbeidsplass,
-<a href="http://www.uio.no/">Universitetet i Oslo</a>, om å gå bort fra
-fri programvare- og åpne standardløsninger for å håndtere epost,
-vekk fra IETF-standarden SIEVE for filtrering av epost og over til
-godseide spesifikasjoner og epostsystemet Microsoft Exchange.
-Protestene har fått litt ny omtale i media de siste dagene, i tillegg
-til de oppslagene som kom i mai.</p>
-
-<ul>
-
-<li>2013-11-26 <a href="http://www.version2.dk/artikel/gigantisk-outlook-konvertering-moeder-protester-paa-universitet-55147">Gigantisk Outlook-konvertering møder protester på universitet</a> - versjon2.dk</li>
-
-<li>2013-11-25
- <a href="http://www.idg.no/computerworld/article279407.ece">Microsoft-protest
- på Universitetet</a> - Computerworld</li>
-
-<li>2013-11-25
- <a href="http://www.uniforum.uio.no/nyheter/2013/11/uio-bor-bruke-apen-programvare.html">Kjemper
- mot innføring av Microsoft Exchange på UiO</a> - Uniforum</li>
-
-<li>2013-11-25
- <a href="http://www.uniforum.uio.no/nyheter/2013/11/uio-utsetter-innforing-av-nytt-e-postsystem.html">Utsetter
- innføring av nytt e-postsystem</a> - Uniforum</li>
-
-<li>2013-05-29
- <a href="http://universitas.no/nyhet/58462/forsvarer-nytt-it-system">Forsvarer
- nytt IT-system</a> - Universitas</li>
-
-<li>2013-05-23
- <a href="http://www.uniforum.uio.no/nyheter/2013/05/uio-innforer-nytt-epost-og-kalendersystem.html">UiO
- innfører nytt epost- og kalenderverktøy</a> - Uniforum</li>
-
-<li>2013-05-22
- <a href="http://universitas.no/nyhet/58424/protestgruppe-vil-stanse-it-system">Protestgruppe
- vil stanse IT-system</a> - Universitas</li>
-
-<li>2013-05-15
- <a href="http://www.uniforum.uio.no/leserbrev/2013/uio-ma-ha-kontroll-over-sitt-eget-epostsystem.html">UiO
- må ha kontroll over sitt eget epostsystem</a> - Uniforum</li>
-
-</ul>
-
-<p>Prosjektledelsen har fortalt at dette skal fungere like godt for
-Linux-brukere som for brukere av Microsoft Windows og Apple MacOSX,
-men jeg lurer på hva slags erfaringer Linux-brukere i eksisterende
-miljøer som bruker MS Exchange har gjort. Hvis du har slik erfaring
-hadet det vært veldig fint om du kan send et leserbrev til
-<a href="http://www.uniforum.uio.no/">Uniforum</a> og fortelle om hvor
-greit det er å bruke Exchange i kryss-platform-miljøer? De jeg har
-snakket med sier en greit får lest e-posten sin hvis Exchange har
-slått på IMAP-funksjonalitet, men at kalender og møtebooking ikke
-fungerer godt for Linux-klienter. Jeg har ingen personlig erfaring å
-komme med, så jeg er nysgjerrig på hva andre kan dele av erfaringer
-med universitetet.</p>
-
-<p>Mitt ankerpunkt mot å bytte ut fri programvare som fungerer godt
-med godseid programvare er at en mister kontroll over egen
-infrastruktur, låser seg inn i en løsning det vil bli dyrt å komme ut
-av, uten at en får funksjonalitet en ikke kunne skaffet seg med fri
-programvare, eventuelt videreutviklet med de pengene som brukes på
-overgangen til MS Exchange. Personlig planlegger jeg å fortsette å
-laste ned all eposten min til lokal maskin for indeksering og lesing
-med <a href=="http://notmuchmail.org">notmuch</a>, så jeg håper jeg
-ikke blir veldig skadelidende av overgangen.</p>
-
-<p><a href="http://dinis.linguateca.pt/Diana/ImotMSUiO.html">Underskriftslista
-for oss som er mot endringen</a>, som omtales i artiklene, er fortsatt
-åpen for de som vil signere på oppropet. Akkurat nå er det 298
-personer som har signert.</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html">A Debian package for SMTP via Tor (aka SMTorP) using exim4</a></div>
+ <div class="date">10th November 2014</div>
+ <div class="body"><p>The right to communicate with your friends and family in private,
+without anyone snooping, is a right every citicen have in a liberal
+democracy. But this right is under serious attack these days.</p>
+
+<p>A while back it occurred to me that one way to make the dragnet
+surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
+the whisleblower Snowden) more expensive for Internet email,
+is to deliver all email using SMTP via Tor. Such SMTP option would be
+a nice addition to the FreedomBox project if we could send email
+between FreedomBox machines without leaking metadata about the emails
+to the people peeking on the wire. I
+<a href="http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html">proposed
+this on the FreedomBox project mailing list in October</a> and got a
+lot of useful feedback and suggestions. It also became obvious to me
+that this was not a novel idea, as the same idea was tested and
+documented by Johannes Berg as early as 2006, and both
+<a href="https://github.com/pagekite/Mailpile/wiki/SMTorP">the
+Mailpile</a> and <a href="http://dee.su/cables">the Cables</a> systems
+propose a similar method / protocol to pass emails between users.</p>
+
+<p>To implement such system one need to set up a Tor hidden service
+providing the SMTP protocol on port 25, and use email addresses
+looking like username@hidden-service-name.onion. With such addresses
+the connections to port 25 on hidden-service-name.onion using Tor will
+go to the correct SMTP server. To do this, one need to configure the
+Tor daemon to provide the hidden service and the mail server to accept
+emails for this .onion domain. To learn more about Exim configuration
+in Debian and test the design provided by Johannes Berg in his FAQ, I
+set out yesterday to create a Debian package for making it trivial to
+set up such SMTP over Tor service based on Debian. Getting it to work
+were fairly easy, and
+<a href="https://github.com/petterreinholdtsen/exim4-smtorp">the
+source code for the Debian package</a> is available from github. I
+plan to move it into Debian if further testing prove this to be a
+useful approach.</p>
+
+<p>If you want to test this, set up a blank Debian machine without any
+mail system installed (or run <tt>apt-get purge exim4-config</tt> to
+get rid of exim4). Install tor, clone the git repository mentioned
+above, build the deb and install it on the machine. Next, run
+<tt>/usr/lib/exim4-smtorp/setup-exim-hidden-service</tt> and follow
+the instructions to get the service up and running. Restart tor and
+exim when it is done, and test mail delivery using swaks like
+this:</p>
+
+<p><blockquote><pre>
+torsocks swaks --server dutlqrrmjhtfa3vp.onion \
+ --to fbx@dutlqrrmjhtfa3vp.onion
+</pre></blockquote></p>
+
+<p>This will test the SMTP delivery using tor. Replace the email
+address with your own address to test your server. :)</p>
+
+<p>The setup procedure is still to complex, and I hope it can be made
+easier and more automatic. Especially the tor setup need more work.
+Also, the package include a tor-smtp tool written in C, but its task
+should probably be rewritten in some script language to make the deb
+architecture independent. It would probably also make the code easier
+to review. The tor-smtp tool currently need to listen on a socket for
+exim to talk to it and is started using xinetd. It would be better if
+no daemon and no socket is needed. I suspect it is possible to get
+exim to run a command line tool for delivery instead of talking to a
+socket, and hope to figure out how in a future version of this
+system.</p>
+
+<p>Until I wipe my test machine, I can be reached using the
+<tt>fbx@dutlqrrmjhtfa3vp.onion</tt> mail address, deliverable over
+SMTorP. :)</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html">New chrpath release 0.15</a></div>
- <div class="date">24th November 2013</div>
- <div class="body"><p>After many years break from the package and a vain hope that
-development would be continued by someone else, I finally pulled my
-acts together this morning and wrapped up a new release of chrpath,
-the command line tool to modify the rpath and runpath of already
-compiled ELF programs. The update was triggered by the persistence of
-Isha Vishnoi at IBM, which needed a new config.guess file to get
-support for the ppc64le architecture (powerpc 64-bit Little Endian) he
-is working on. I checked the
-<a href="http://packages.qa.debian.org/chrpath">Debian</a>,
-<a href="https://launchpad.net/ubuntu/+source/chrpath">Ubuntu</a> and
-<a href="https://admin.fedoraproject.org/pkgdb/acls/name/chrpath">Fedora</a>
-packages for interesting patches (failed to find the source from
-OpenSUSE and Mandriva packages), and found quite a few nice fixes.
-These are the release notes:</p>
-
-<p>New in 0.15 released 2013-11-24:</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/First_Jessie_based_Debian_Edu_released__alpha0_.html">First Jessie based Debian Edu released (alpha0)</a></div>
+ <div class="date">27th October 2014</div>
+ <div class="body"><p>I am happy to report that I on behalf of the Debian Edu team just
+sent out
+<a href="https://lists.debian.org/debian-edu-announce/2014/10/msg00000.html">this
+announcement</a>:</p>
-<ul>
+<pre>
+The Debian Edu Team is pleased to announce the release of Debian Edu
+Jessie 8.0+edu0~alpha0
+
+Debian Edu is a complete operating system for schools. Through its
+various installation profiles you can install servers, workstations
+and laptops which will work together on the school network. With
+Debian Edu, the teachers themselves or their technical support can
+roll out a complete multi-user multi-machine study environment within
+hours or a few days. Debian Edu comes with hundreds of applications
+pre-installed, but you can always add more packages from Debian.
+
+For those who want to give Debian Edu Jessie a try, download and
+installation instructions are available, including detailed
+instructions in the manual[1] explaining the first steps, such as
+setting up a network or adding users. Please note that the password
+for the user your prompted for during installation must have a length
+of at least 5 characters!
+
+ [1] <URL: <a href="https://wiki.debian.org/DebianEdu/Documentation/Jessie">https://wiki.debian.org/DebianEdu/Documentation/Jessie</a> >
+
+Would you like to give your school's computer a longer life? Are you
+tired of sneaker administration, running from computer to computer
+reinstalling the operating system? Would you like to administrate all
+the computers in your school using only a couple of hours every week?
+Check out Debian Edu Jessie!
+
+Skolelinux is used by at least two hundred schools all over the world,
+mostly in Germany and Norway.
+
+About Debian Edu and Skolelinux
+===============================
+
+Debian Edu, also known as Skolelinux[2], is a Linux distribution based
+on Debian providing an out-of-the box environment of a completely
+configured school network. Immediately after installation a school
+server running all services needed for a school network is set up just
+waiting for users and machines being added via GOsa², a comfortable
+Web-UI. A netbooting environment is prepared using PXE, so after
+initial installation of the main server from CD or USB stick all other
+machines can be installed via the network. The provided school server
+provides LDAP database and Kerberos authentication service,
+centralized home directories, DHCP server, web proxy and many other
+services. The desktop contains more than 60 educational software
+packages[3] and more are available from the Debian archive, and
+schools can choose between KDE, Gnome, LXDE, Xfce and MATE desktop
+environment.
+
+ [2] <URL: <a href="http://www.skolelinux.org/">http://www.skolelinux.org/</a> >
+ [3] <URL: <a href="http://people.skolelinux.org/pere/blog/Educational_applications_included_in_Debian_Edu___Skolelinux__the_screenshot_collection____.html">http://people.skolelinux.org/pere/blog/Educational_applications_included_in_Debian_Edu___Skolelinux__the_screenshot_collection____.html</a> >
+
+Full release notes and manual
+=============================
+
+Below the download URLs there is a list of some of the new features
+and bugfixes of Debian Edu 8.0+edu0~alpha0 Codename Jessie. The full
+list is part of the manual. (See the feature list in the manual[4] for
+the English version.) For some languages manual translations are
+available, see the manual translation overview[5].
+
+ [4] <URL: <a href="https://wiki.debian.org/DebianEdu/Documentation/Jessie/Features">https://wiki.debian.org/DebianEdu/Documentation/Jessie/Features</a> >
+ [5] <URL: <a href="http://maintainer.skolelinux.org/debian-edu-doc/">http://maintainer.skolelinux.org/debian-edu-doc/</a> >
+
+Where to get it
+---------------
+
+To download the multiarch netinstall CD release (624 MiB) you can use
+
+ * <a href="ftp://ftp.skolelinux.org/skolelinux-cd/debian-edu-8.0+edu0~alpha0-CD.iso">ftp://ftp.skolelinux.org/skolelinux-cd/debian-edu-8.0+edu0~alpha0-CD.iso</a>
+ * <a href="http://ftp.skolelinux.org/skolelinux-cd/debian-edu-8.0+edu0~alpha0-CD.iso">http://ftp.skolelinux.org/skolelinux-cd/debian-edu-8.0+edu0~alpha0-CD.iso</a>
+ * rsync -avzP ftp.skolelinux.org::skolelinux-cd/debian-edu-8.0+edu0~alpha0-CD.iso .
+
+The SHA1SUM of this image is: 361188818e036ce67280a572f757de82ebfeb095
+
+New features for Debian Edu 8.0+edu0~alpha0 Codename Jessie released 2014-10-27
+===============================================================================
+
+
+Installation changes
+--------------------
+
+ * PXE installation now installs firmware automatically for the hardware present.
+
+Software updates
+----------------
+
+Everything which is new in Debian Jessie 8.0, eg:
+
+ * Linux kernel 3.16.x
+ * Desktop environments KDE "Plasma" 4.11.12, GNOME 3.14, Xfce 4.10,
+ LXDE 0.5.6 and MATE 1.8 (KDE "Plasma" is installed by default; to
+ choose one of the others see manual.)
+ * the browsers Iceweasel 31 ESR and Chromium 38
+ * !LibreOffice 4.3.3
+ * GOsa 2.7.4
+ * LTSP 5.5.4
+ * CUPS print system 1.7.5
+ * new boot framework: systemd
+ * Educational toolbox GCompris 14.07
+ * Music creator Rosegarden 14.02
+ * Image editor Gimp 2.8.14
+ * Virtual stargazer Stellarium 0.13.0
+ * golearn 0.9
+ * tuxpaint 0.9.22
+ * New version of debian-installer from Debian Jessie.
+ * Debian Jessie includes about 42000 packages available for
+ installation.
+ * More information about Debian Jessie 8.0 is provided in the release
+ notes[6] and the installation manual[7].
+
+ [6] <URL: <a href="http://www.debian.org/releases/jessie/releasenotes">http://www.debian.org/releases/jessie/releasenotes</a> >
+ [7] <URL: <a href="http://www.debian.org/releases/jessie/installmanual">http://www.debian.org/releases/jessie/installmanual</a> >
+
+Fixed bugs
+----------
+
+ * Inserting incorrect DNS information in Gosa will no longer break
+ DNS completely, but instead stop DNS updates until the incorrect
+ information is corrected (Debian bug #710362)
+ * and many others.
+
+Documentation and translation updates
+-------------------------------------
+
+ * The Debian Edu Jessie Manual is fully translated to German, French,
+ Italian, Danish and Dutch. Partly translated versions exist for
+ Norwegian Bokmal and Spanish.
+
+Other changes
+-------------
+
+ * Due to new Squid settings, powering off or rebooting the main
+ server takes more time.
+ * To manage printers localhost:631 has to be used, currently www:631
+ doesn't work.
+
+Regressions / known problems
+----------------------------
+
+ * Installing LTSP chroot fails with a bug related to eatmydata about
+ exim4-config failing to run its postinst (see Debian bug #765694
+ and Debian bug #762103).
+ * Munin collection is not properly configured on clients (Debian bug
+ #764594). The fix is available in a newer version of munin-node.
+ * PXE setup for Main Server and Thin Client Server setup does not
+ work when installing on a machine without direct Internet access.
+ Will be fixed when Debian bug #766960 is fixed in Jessie.
- <li>Updated config.sub and config.guess from the GNU project to work
- with newer architectures. Thanks to isha vishnoi for the heads
- up.</li>
+See the status page[8] for the complete list.
- <li>Updated README with current URLs.</li>
+ [8] <URL: <a href="https://wiki.debian.org/DebianEdu/Status/Jessie">https://wiki.debian.org/DebianEdu/Status/Jessie</a> >
- <li>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
- Matthias Klose.</li>
+How to report bugs
+------------------
- <li>Added missing help for -k|--keepgoing option, using patch by
- Petr Machata found in Fedora.</li>
+<URL: <a href="http://wiki.debian.org/DebianEdu/HowTo/ReportBugs">http://wiki.debian.org/DebianEdu/HowTo/ReportBugs</a> >
- <li>Rewrite removal of RPATH/RUNPATH to make sure the entry in
- .dynamic is a NULL terminated string. Based on patch found in
- Fedora credited Axel Thimm and Christian Krause.</li>
+About Debian
+============
-</ul>
+The Debian Project was founded in 1993 by Ian Murdock to be a truly
+free community project. Since then the project has grown to be one of
+the largest and most influential open source projects. Thousands of
+volunteers from all over the world work together to create and
+maintain Debian software. Available in 70 languages, and supporting a
+huge range of computer types, Debian calls itself the universal
+operating system.
+
+Contact Information
+For further information, please visit the Debian web pages[9] or send
+mail to press@debian.org.
-<p>You can
-<a href="https://alioth.debian.org/frs/?group_id=31052">download the
-new version 0.15 from alioth</a>. Please let us know via the Alioth
-project if something is wrong with the new release. The test suite
-did not discover any old errors, so if you find a new one, please also
-include a testsuite check.</p>
+ [9] <URL: <a href="http://www.debian.org/">http://www.debian.org/</a> >
+</pre>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian
">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian
edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/RSS_kilde_for_friteksts_k_i_offentlige_anbud_hos_Doffin.html">RSS-kilde for fritekstsøk i offentlige anbud hos Doffin</a></div>
- <div class="date">22nd November 2013</div>
- <div class="body"><p>I fjor sommer lagde jeg en
-<a href="http://people.skolelinux.org/pere/blog/SQL_database_med_anbud_publisert_p__Doffin.html">offentlig
-tilgjengelig SQL-database over offentlig anbud</a> basert på skraping
-av HTML-data fra Doffin. Den har stått og gått siden da, og har nå
-ca. 28000 oppføringer. Jeg oppdaget da jeg tittet innom at noen
-oppføringer var ikke blitt med, antagelig på grunn av at de fikk
-tildelt sekvensnummer i Doffin en godt stund før de ble publisert,
-slik at min nettsideskraper som fortsatte skrapingen der den slapp
-sist ikke fikk dem med seg. Jeg har fikset litt slik at skraperen nå
-ser litt tilbake i tid for å se om den har gått glipp av noen
-oppføringer, og har skrapet på nytt fra midten av september 2013 og
-fremover. Det bør dermed bli en mer komplett database for kommende
-måneder. Hvis jeg får tid skal jeg forsøke å skrape "glemte" data fra
-før midten av september 2013, men tør ikke garantere at det blir
-prioritert med det første. </p>
-
-<p>Men målet med denne bloggposten er å vise hvordan denne
-Doffin-databasen kan brukes og integreres med en RSS-leser, slik at en
-kan la datamaskinen holde et øye med Doffin-annonseringer etter
-nøkkelord. En kan lage sitt eget søk ved å besøke
-<ahref="https://classic.scraperwiki.com/docs/api?name=norwegian-doffin#sqlite">API-et
-hos Scraperwiki</a>, velge format rss2 og så legge inn noe ala dette i
-"query in SQL":</p>
-
-<p><pre>
-select title, scrapedurl as link, abstract as description,
- publishdate as pubDate from 'swdata'
- where abstract like '%linux%' or title like '%linux%'
- order by seq desc limit 20
-</pre></p>
-
-<p>Dette vil søke opp alle anbud med ordet linux i oppsummering eller
-tittel. En kan lage mer avanserte søk hvis en ønsker det. URL-en som
-dukker opp nederst på siden kan en så gi til sin RSS-leser (jeg bruker
-akregator selv), og så automatisk få beskjed hvis det dukker opp anbud
-med det aktuelle nøkkelordet i teksten. Merk at kapasiteten og
-ytelsen hos Scraperwiki er begrenset, så ikke be RSS-leseren hente ned
-oftere enn en gang hver dag.</p>
-
-<p>Du lurer kanskje på hva slags informasjon en kan få ut fra denne
-databasen. Her er to RSS-kilder, med søkeordet
-"<a href="https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&name=norwegian-doffin&query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20'swdata'%0A%20%20%20where%20abstract%20like%20'%25linux%25'%20or%20title%20like%20'%25linux%25'%0A%20%20%20order%20by%20seq%20desc%20limit%2020">linux</a>",
-søkeordet
-"<a href="https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&name=norwegian-doffin&query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20'swdata'%0A%20%20%20where%20abstract%20like%20'%25fri%20programvare%25'%20or%20title%20like%20'%25fri%20programvare%25'%0A%20%20%20order%20by%20seq%20desc%20limit%2020">fri
-programvare</a>"
-og søkeordet
-"<a href="https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&name=norwegian-doffin&query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20'swdata'%0A%20%20%20where%20abstract%20like%20'%25odf%25'%20or%20title%20like%20'%25odf%25'%0A%20%20%20order%20by%20seq%20desc%20limit%2020">odf</a>".
-Det er bare å søke på det en er interessert i. Kopier gjerne
-datasettet og sett opp din egen tjeneste hvis du vil gjøre mer
-avanserte søk. SQLite-filen med Doffin-oppføringer kan lastes med fra
-Scraperwiki for de som vil grave dypere.</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/I_spent_last_weekend_recording_MakerCon_Nordic.html">I spent last weekend recording MakerCon Nordic</a></div>
+ <div class="date">23rd October 2014</div>
+ <div class="body"><p>I spent last weekend at <a href="http://www.makercon.no/">Makercon
+Nordic</a>, a great conference and workshop for makers in Norway and
+the surrounding countries. I had volunteered on behalf of the
+Norwegian Unix Users Group (NUUG) to video record the talks, and we
+had a great and exhausting time recording the entire day, two days in
+a row. There were only two of us, Hans-Petter and me, and we used the
+regular video equipment for NUUG, with a
+<a href="http://dvswitch.alioth.debian.org/wiki/">dvswitch</a>, a
+camera and a VGA to DV convert box, and mixed video and slides
+live.</p>
+
+<p>Hans-Petter did the post-processing, consisting of uploading the
+around 180 GiB of raw video to Youtube, and the result is
+<a href="https://www.youtube.com/user/MakerConNordic/">now becoming
+public</a> on the MakerConNordic account. The videos have the license
+NUUG always use on our recordings, which is
+<a href="http://creativecommons.org/licenses/by-sa/3.0/no/">Creative
+Commons Navngivelse-Del på samme vilkår 3.0 Norge</a>. Many great
+talks available. Check it out! :)</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/All_drones_should_be_radio_marked_with_what_they_do_and_who_they_belong_to.html">All drones should be radio marked with what they do and who they belong to</a></div>
- <div class="date">21st November 2013</div>
- <div class="body"><p>Drones, flying robots, are getting more and more popular. The most
-know ones are the killer drones used by some government to murder
-people they do not like without giving them the chance of a fair
-trial, but the technology have many good uses too, from mapping and
-forest maintenance to photography and search and rescue. I am sure it
-is just a question of time before "bad drones" are in the hands of
-private enterprises and not only state criminals but petty criminals
-too. The drone technology is very useful and very dangerous. To have
-some control over the use of drones, I agree with Daniel Suarez in his
-TED talk
-"<a href="https://archive.org/details/DanielSuarez_2013G">The kill
-decision shouldn't belong to a robot</a>", where he suggested this
-little gem to keep the good while limiting the bad use of drones:</p>
-
-<blockquote>
-
-<p>Each robot and drone should have a cryptographically signed
-I.D. burned in at the factory that can be used to track its movement
-through public spaces. We have license plates on cars, tail numbers on
-aircraft. This is no different. And every citizen should be able to
-download an app that shows the population of drones and autonomous
-vehicles moving through public spaces around them, both right now and
-historically. And civic leaders should deploy sensors and civic drones
-to detect rogue drones, and instead of sending killer drones of their
-own up to shoot them down, they should notify humans to their
-presence. And in certain very high-security areas, perhaps civic
-drones would snare them and drag them off to a bomb disposal facility.</p>
-
-<p>But notice, this is more an immune system than a weapons system. It
-would allow us to avail ourselves of the use of autonomous vehicles
-and drones while still preserving our open, civil society.</p>
-
-</blockquote>
-
-<p>The key is that <em>every citizen</em> should be able to read the
-radio beacons sent from the drones in the area, to be able to check
-both the government and others use of drones. For such control to be
-effective, everyone must be able to do it. What should such beacon
-contain? At least formal owner, purpose, contact information and GPS
-location. Probably also the origin and target position of the current
-flight. And perhaps some registration number to be able to look up
-the drone in a central database tracking their movement. Robots
-should not have privacy. It is people who need privacy.</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html">listadmin, the quick way to moderate mailman lists - nice free software</a></div>
+ <div class="date">22nd October 2014</div>
+ <div class="body"><p>If you ever had to moderate a mailman list, like the ones on
+alioth.debian.org, you know the web interface is fairly slow to
+operate. First you visit one web page, enter the moderation password
+and get a new page shown with a list of all the messages to moderate
+and various options for each email address. This take a while for
+every list you moderate, and you need to do it regularly to do a good
+job as a list moderator. But there is a quick alternative,
+<a href="http://heim.ifi.uio.no/kjetilho/hacks/#listadmin">the
+listadmin program</a>. It allow you to check lists for new messages
+to moderate in a fraction of a second. Here is a test run on two
+lists I recently took over:</p>
+
+<p><blockquote><pre>
+% time listadmin xiph
+fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
+fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
+
+real 0m1.709s
+user 0m0.232s
+sys 0m0.012s
+%
+</pre></blockquote></p>
+
+<p>In 1.7 seconds I had checked two mailing lists and confirmed that
+there are no message in the moderation queue. Every morning I
+currently moderate 68 mailman lists, and it normally take around two
+minutes. When I took over the two pkg-xiph lists above a few days
+ago, there were 400 emails waiting in the moderator queue. It took me
+less than 15 minutes to process them all using the listadmin
+program.</p>
+
+<p>If you install
+<a href="https://tracker.debian.org/pkg/listadmin">the listadmin
+package</a> from Debian and create a file <tt>~/.listadmin.ini</tt>
+with content like this, the moderation task is a breeze:</p>
+
+<p><blockquote><pre>
+username username@example.org
+spamlevel 23
+default discard
+discard_if_reason "Posting restricted to members only. Remove us from your mail list."
+
+password secret
+adminurl https://{domain}/mailman/admindb/{list}
+mailman-list@lists.example.com
+
+password hidden
+other-list@otherserver.example.org
+</pre></blockquote></p>
+
+<p>There are other options to set as well. Check the manual page to
+learn the details.</p>
+
+<p>If you are forced to moderate lists on a mailman installation where
+the SSL certificate is self signed or not properly signed by a
+generally accepted signing authority, you can set a environment
+variable when calling listadmin to disable SSL verification:</p>
+
+<p><blockquote><pre>
+PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
+</pre></blockquote></p>
+
+<p>If you want to moderate a subset of the lists you take care of, you
+can provide an argument to the listadmin script like I do in the
+initial screen dump (the xiph argument). Using an argument, only
+lists matching the argument string will be processed. This make it
+quick to accept messages if you notice the moderation request in your
+email.</p>
+
+<p>Without the listadmin program, I would never be the moderator of 68
+mailing lists, as I simply do not have time to spend on that if the
+process was any slower. The listadmin program have saved me hours of
+time I could spend elsewhere over the years. It truly is nice free
+software.</p>
+
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
+
+<p>Update 2014-10-27: Added missing 'username' statement in
+configuration example. Also, I've been told that the
+PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
+sure why.</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/robot">robot</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Lets_make_a_wireless_community_network_in_Oslo_.html">Lets make a wireless community network in Oslo!</a></div>
- <div class="date">13th November 2013</div>
- <div class="body"><p>Today NUUG and Hackeriet announced
-<a href="http://www.nuug.no/news/Bli_med___bygge_dugnadsnett_for_alle_i_Oslo.shtml">our
-plans to join forces and create a wireless community network in
-Oslo</a>. The workshop to help people get started will take place
-Thursday 2013-11-28, but we already are collecting the geolocation of
-people joining forces to make this happen. We have
-<a href="https://github.com/petterreinholdtsen/meshfx-node/blob/master/oslo-nodes.geojson">9
-locations plotted on the map</a>, but we will need more before we have
-a connected mesh spread across Oslo. If this sound interesting to
-you, please join us at the workshop. If you are too impatient to wait
-15 days, please join us on the IRC channel
-<a href="irc://irc.freenode.net/%23nuug">#nuug on irc.freenode.net</a>
-right away. :)</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html">Debian Jessie, PXE and automatic firmware installation</a></div>
+ <div class="date">17th October 2014</div>
+ <div class="body"><p>When PXE installing laptops with Debian, I often run into the
+problem that the WiFi card require some firmware to work properly.
+And it has been a pain to fix this using preseeding in Debian.
+Normally something more is needed. But thanks to
+<a href="https://packages.qa.debian.org/i/isenkram.html">my isenkram
+package</a> and its recent tasksel extension, it has now become easy
+to do this using simple preseeding.</p>
+
+<p>The isenkram-cli package provide tasksel tasks which will install
+firmware for the hardware found in the machine (actually, requested by
+the kernel modules for the hardware). (It can also install user space
+programs supporting the hardware detected, but that is not the focus
+of this story.)</p>
+
+<p>To get this working in the default installation, two preeseding
+values are needed. First, the isenkram-cli package must be installed
+into the target chroot (aka the hard drive) before tasksel is executed
+in the pkgsel step of the debian-installer system. This is done by
+preseeding the base-installer/includes debconf value to include the
+isenkram-cli package. The package name is next passed to debootstrap
+for installation. With the isenkram-cli package in place, tasksel
+will automatically use the isenkram tasks to detect hardware specific
+packages for the machine being installed and install them, because
+isenkram-cli contain tasksel tasks.</p>
+
+<p>Second, one need to enable the non-free APT repository, because
+most firmware unfortunately is non-free. This is done by preseeding
+the apt-mirror-setup step. This is unfortunate, but for a lot of
+hardware it is the only option in Debian.</p>
+
+<p>The end result is two lines needed in your preseeding file to get
+firmware installed automatically by the installer:</p>
+
+<p><blockquote><pre>
+base-installer base-installer/includes string isenkram-cli
+apt-mirror-setup apt-setup/non-free boolean true
+</pre></blockquote></p>
+
+<p>The current version of isenkram-cli in testing/jessie will install
+both firmware and user space packages when using this method. It also
+do not work well, so use version 0.15 or later. Installing both
+firmware and user space packages might give you a bit more than you
+want, so I decided to split the tasksel task in two, one for firmware
+and one for user space programs. The firmware task is enabled by
+default, while the one for user space programs is not. This split is
+implemented in the package currently in unstable.</p>
+
+<p>If you decide to give this a go, please let me know (via email) how
+this recipe work for you. :)</p>
+
+<p>So, I bet you are wondering, how can this work. First and
+foremost, it work because tasksel is modular, and driven by whatever
+files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
+isenkram-cli package place two files for tasksel to find. First there
+is the task description file (/usr/share/tasksel/descs/isenkram.desc):</p>
+
+<p><blockquote><pre>
+Task: isenkram-packages
+Section: hardware
+Description: Hardware specific packages (autodetected by isenkram)
+ Based on the detected hardware various hardware specific packages are
+ proposed.
+Test-new-install: show show
+Relevance: 8
+Packages: for-current-hardware
+
+Task: isenkram-firmware
+Section: hardware
+Description: Hardware specific firmware packages (autodetected by isenkram)
+ Based on the detected hardware various hardware specific firmware
+ packages are proposed.
+Test-new-install: mark show
+Relevance: 8
+Packages: for-current-hardware-firmware
+</pre></blockquote></p>
+
+<p>The key parts are Test-new-install which indicate how the task
+should be handled and the Packages line referencing to a script in
+/usr/lib/tasksel/packages/. The scripts use other scripts to get a
+list of packages to install. The for-current-hardware-firmware script
+look like this to list relevant firmware for the machine:
+
+<p><blockquote><pre>
+#!/bin/sh
+#
+PATH=/usr/sbin:$PATH
+export PATH
+isenkram-autoinstall-firmware -l
+</pre></blockquote></p>
+
+<p>With those two pieces in place, the firmware is installed by
+tasksel during the normal d-i run. :)</p>
+
+<p>If you want to test what tasksel will install when isenkram-cli is
+installed, run <tt>DEBIAN_PRIORITY=critical tasksel --test
+--new-install</tt> to get the list of packages that tasksel would
+install.</p>
+
+<p><a href="https://wiki.debian.org/DebianEdu/">Debian Edu</a> will be
+pilots in testing this feature, as isenkram is used there now to
+install firmware, replacing the earlier scripts.</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Running_TP_Link_MR3040_as_a_batman_adv_mesh_node_using_openwrt.html">Running TP-Link MR3040 as a batman-adv mesh node using openwrt</a></div>
- <div class="date">10th November 2013</div>
- <div class="body"><p>Continuing my research into mesh networking, I was recommended to
-use TP-Link 3040 and 3600 access points as mesh nodes, and the pair I
-bought arrived on Friday. Here are my notes on how to set up the
-MR3040 as a mesh node using
-<a href="http://www.openwrt.org/">OpenWrt</a>.</p>
-
-<p>I started by following the instructions on the OpenWRT wiki for
-<a href="http://wiki.openwrt.org/toh/tp-link/tl-mr3040">TL-MR3040</a>,
-and downloaded
-<a href="http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin">the
-recommended firmware image</a>
-(openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin) and
-uploaded it into the original web interface. The flashing went fine,
-and the machine was available via telnet on the ethernet port. After
-logging in and setting the root password, ssh was available and I
-could start to set it up as a batman-adv mesh node.</p>
-
-<p>I started off by reading the instructions from
-<a href="http://wirelessafrica.meraka.org.za/wiki/index.php?title=Antoine's_Research">Wireless
-Africa</a>, which had quite a lot of useful information, but
-eventually I followed the recipe from the Open Mesh wiki for
-<a href="http://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config">using
-batman-adv on OpenWrt</a>. A small snag was the fact that the
-<tt>opkg install kmod-batman-adv</tt> command did not work as it
-should. The batman-adv kernel module would fail to load because its
-dependency crc16 was not already loaded. I
-<a href="https://dev.openwrt.org/ticket/14452">reported the bug</a> to
-the openwrt project and hope it will be fixed soon. But the problem
-only seem to affect initial testing of batman-adv, as configuration
-seem to work when booting from scratch.</p>
-
-<p>The setup is done using files in /etc/config/. I did not bridge
-the Ethernet and mesh interfaces this time, to be able to hook up the
-box on my local network and log into it for configuration updates.
-The following files were changed and look like this after modifying
-them:</p>
-
-<p><tt>/etc/config/network</tt></p>
-
-<pre>
-
-config interface 'loopback'
- option ifname 'lo'
- option proto 'static'
- option ipaddr '127.0.0.1'
- option netmask '255.0.0.0'
-
-config globals 'globals'
- option ula_prefix 'fdbf:4c12:3fed::/48'
-
-config interface 'lan'
- option ifname 'eth0'
- option type 'bridge'
- option proto 'dhcp'
- option ipaddr '192.168.1.1'
- option netmask '255.255.255.0'
- option hostname 'tl-mr3040'
- option ip6assign '60'
-
-config interface 'mesh'
- option ifname 'adhoc0'
- option mtu '1528'
- option proto 'batadv'
- option mesh 'bat0'
-</pre>
-
-<p><tt>/etc/config/wireless</tt></p>
-<pre>
-
-config wifi-device 'radio0'
- option type 'mac80211'
- option channel '11'
- option hwmode '11ng'
- option path 'platform/ar933x_wmac'
- option htmode 'HT20'
- list ht_capab 'SHORT-GI-20'
- list ht_capab 'SHORT-GI-40'
- list ht_capab 'RX-STBC1'
- list ht_capab 'DSSS_CCK-40'
- option disabled '0'
-
-config wifi-iface 'wmesh'
- option device 'radio0'
- option ifname 'adhoc0'
- option network 'mesh'
- option encryption 'none'
- option mode 'adhoc'
- option bssid '02:BA:00:00:00:01'
- option ssid 'meshfx@hackeriet'
-</pre>
-<p><tt>/etc/config/batman-adv</tt></p>
-<pre>
-
-config 'mesh' 'bat0'
- option interfaces 'adhoc0'
- option 'aggregated_ogms'
- option 'ap_isolation'
- option 'bonding'
- option 'fragmentation'
- option 'gw_bandwidth'
- option 'gw_mode'
- option 'gw_sel_class'
- option 'log_level'
- option 'orig_interval'
- option 'vis_mode'
- option 'bridge_loop_avoidance'
- option 'distributed_arp_table'
- option 'network_coding'
- option 'hop_penalty'
-
-# yet another batX instance
-# config 'mesh' 'bat5'
-# option 'interfaces' 'second_mesh'
-</pre>
-
-<p>The mesh node is now operational. I have yet to test its range,
-but I hope it is good. I have not yet tested the TP-Link 3600 box
-still wrapped up in plastic.</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html">Ubuntu used to show the bread prizes at ICA Storo</a></div>
+ <div class="date"> 4th October 2014</div>
+ <div class="body"><p>Today I came across an unexpected Ubuntu boot screen. Above the
+bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
+with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
+on a screen normally showing the bread types and prizes:</p>
+
+<p align="center"><img width="70%" src="http://people.skolelinux.org/pere/blog/images/2014-10-04-ubuntu-ica-storo-crop.jpeg"></p>
+
+<p>If it had booted as it was supposed to, I would never had known
+about this hidden Linux installation. It is interesting what
+<a href="http://revealingerrors.com/">errors can reveal</a>.</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html">Debian init.d boot script example for rsyslog</a></div>
- <div class="date"> 2nd November 2013</div>
- <div class="body"><p>If one of the points of switching to a new init system in Debian is
-<a href="http://thomas.goirand.fr/blog/?p=147">to get rid of huge
-init.d scripts</a>, I doubt we need to switch away from sysvinit and
-init.d scripts at all. Here is an example init.d script, ie a rewrite
-of /etc/init.d/rsyslog:</p>
-
-<p><pre>
-#!/lib/init/init-d-script
-### BEGIN INIT INFO
-# Provides: rsyslog
-# Required-Start: $remote_fs $time
-# Required-Stop: umountnfs $time
-# X-Stop-After: sendsigs
-# Default-Start: 2 3 4 5
-# Default-Stop: 0 1 6
-# Short-Description: enhanced syslogd
-# Description: Rsyslog is an enhanced multi-threaded syslogd.
-# It is quite compatible to stock sysklogd and can be
-# used as a drop-in replacement.
-### END INIT INFO
-DESC="enhanced syslogd"
-DAEMON=/usr/sbin/rsyslogd
-</pre></p>
-
-<p>Pretty minimalistic to me... For the record, the original sysv-rc
-script was 137 lines, and the above is just 15 lines, most of it meta
-info/comments.</p>
-
-<p>How to do this, you ask? Well, one create a new script
-/lib/init/init-d-script looking something like this:
-
-<p><pre>
-#!/bin/sh
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html">New lsdvd release version 0.17 is ready</a></div>
+ <div class="date"> 4th October 2014</div>
+ <div class="body"><p>The <a href="https://sourceforge.net/p/lsdvd/">lsdvd project</a>
+got a new set of developers a few weeks ago, after the original
+developer decided to step down and pass the project to fresh blood.
+This project is now maintained by Petter Reinholdtsen and Steve
+Dibb.</p>
+
+<p>I just wrapped up
+<a href="https://sourceforge.net/p/lsdvd/mailman/message/32896061/">a
+new lsdvd release</a>, available in git or from
+<a href="https://sourceforge.net/projects/lsdvd/files/lsdvd/">the
+download page</a>. This is the changelog dated 2014-10-03 for version
+0.17.</p>
-# Define LSB log_* functions.
-# Depend on lsb-base (>= 3.2-14) to ensure that this file is present
-# and status_of_proc is working.
-. /lib/lsb/init-functions
+<ul>
-#
-# Function that starts the daemon/service
+ <li>Ignore 'phantom' audio, subtitle tracks</li>
+ <li>Check for garbage in the program chains, which indicate that a track is
+ non-existant, to work around additional copy protection</li>
+ <li>Fix displaying content type for audio tracks, subtitles</li>
+ <li>Fix pallete display of first entry</li>
+ <li>Fix include orders</li>
+ <li>Ignore read errors in titles that would not be displayed anyway</li>
+ <li>Fix the chapter count</li>
+ <li>Make sure the array size and the array limit used when initialising
+ the palette size is the same.</li>
+ <li>Fix array printing.</li>
+ <li>Correct subsecond calculations.</li>
+ <li>Add sector information to the output format.</li>
+ <li>Clean up code to be closer to ANSI C and compile without warnings
+ with more GCC compiler warnings.</li>
-#
-do_start()
-{
- # Return
- # 0 if daemon has been started
- # 1 if daemon was already running
- # 2 if daemon could not be started
- start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \
- || return 1
- start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
- $DAEMON_ARGS \
- || return 2
- # Add code here, if necessary, that waits for the process to be ready
- # to handle requests from services started subsequently which depend
- # on this one. As a last resort, sleep for some time.
-}
-
-#
-# Function that stops the daemon/service
-#
-do_stop()
-{
- # Return
- # 0 if daemon has been stopped
- # 1 if daemon was already stopped
- # 2 if daemon could not be stopped
- # other if a failure occurred
- start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
- RETVAL="$?"
- [ "$RETVAL" = 2 ] && return 2
- # Wait for children to finish too if this is a daemon that forks
- # and if the daemon is only ever run from this initscript.
- # If the above conditions are not satisfied then add some other code
- # that waits for the process to drop all resources that could be
- # needed by services started subsequently. A last resort is to
- # sleep for some time.
- start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
- [ "$?" = 2 ] && return 2
- # Many daemons don't delete their pidfiles when they exit.
- rm -f $PIDFILE
- return "$RETVAL"
-}
+</ul>
-#
-# Function that sends a SIGHUP to the daemon/service
-#
-do_reload() {
- #
- # If the daemon can reload its configuration without
- # restarting (for example, when it is sent a SIGHUP),
- # then implement that here.
- #
- start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
- return 0
-}
-
-SCRIPTNAME=$1
-scriptbasename="$(basename $1)"
-echo "SN: $scriptbasename"
-if [ "$scriptbasename" != "init-d-library" ] ; then
- script="$1"
- shift
- . $script
-else
- exit 0
-fi
-
-NAME=$(basename $DAEMON)
-PIDFILE=/var/run/$NAME.pid
-
-# Exit if the package is not installed
-#[ -x "$DAEMON" ] || exit 0
-
-# Read configuration variable file if it is present
-[ -r /etc/default/$NAME ] && . /etc/default/$NAME
-
-# Load the VERBOSE setting and other rcS variables
-. /lib/init/vars.sh
-
-case "$1" in
- start)
- [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
- do_start
- case "$?" in
- 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
- 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
- esac
- ;;
- stop)
- [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
- do_stop
- case "$?" in
- 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
- 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
- esac
- ;;
- status)
- status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
- ;;
- #reload|force-reload)
- #
- # If do_reload() is not implemented then leave this commented out
- # and leave 'force-reload' as an alias for 'restart'.
- #
- #log_daemon_msg "Reloading $DESC" "$NAME"
- #do_reload
- #log_end_msg $?
- #;;
- restart|force-reload)
- #
- # If the "reload" option is implemented then remove the
- # 'force-reload' alias
- #
- log_daemon_msg "Restarting $DESC" "$NAME"
- do_stop
- case "$?" in
- 0|1)
- do_start
- case "$?" in
- 0) log_end_msg 0 ;;
- 1) log_end_msg 1 ;; # Old process is still running
- *) log_end_msg 1 ;; # Failed to start
- esac
- ;;
- *)
- # Failed to stop
- log_end_msg 1
- ;;
- esac
- ;;
- *)
- echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
- exit 3
- ;;
-esac
-
-:
-</pre></p>
-
-<p>It is based on /etc/init.d/skeleton, and could be improved quite a
-lot. I did not really polish the approach, so it might not always
-work out of the box, but you get the idea. I did not try very hard to
-optimize it nor make it more robust either.</p>
-
-<p>A better argument for switching init system in Debian than reducing
-the size of init scripts (which is a good thing to do anyway), is to
-get boot system that is able to handle the kernel events sensibly and
-robustly, and do not depend on the boot to run sequentially. The boot
-and the kernel have not behaved sequentially in years.</p>
+<p>This change bring together patches for lsdvd in use in various
+Linux and Unix distributions, as well as patches submitted to the
+project the last nine years. Please check it out. :)</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>.
</div>
<h2>Archive</h2>
<ul>
+<li>2014
+<ul>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2014/12/">December (1)</a></li>
+
+</ul></li>
+
<li>2013
<ul>
<li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
-<li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (2)</a></li>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
</ul></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (7)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (8)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (13)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (15)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (91)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (109)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (143)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (151)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (10)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (15)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (12)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (231)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (263)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (12)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (14)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (5)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (38)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (41)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (7)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (10)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (18)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (19)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (6)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (7)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (25)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (32)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (239)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (250)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (161)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (163)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (9)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (11)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (45)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (50)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (67)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (76)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
+
<li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (33)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (41)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (44)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (46)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (21)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (27)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (1)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (2)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (39)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (46)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (28)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (34)</a></li>
</ul>
projects / homepage.git / blobdiff