1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/' xmlns:
atom=
"http://www.w3.org/2005/Atom">
4 <title>Petter Reinholdtsen
</title>
5 <description></description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
7 <atom:link href=
"http://people.skolelinux.org/pere/blog/index.rss" rel=
"self" type=
"application/rss+xml" />
10 <title>Opphavsretts-status for «Empty Socks» fra
1927?
</title>
11 <link>http://people.skolelinux.org/pere/blog/Opphavsretts_status_for__Empty_Socks__fra_1927_.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Opphavsretts_status_for__Empty_Socks__fra_1927_.html
</guid>
13 <pubDate>Fri,
12 Dec
2014 14:
30:
00 +
0100</pubDate>
14 <description><p
>For noen dager siden
15 <a href=
"http://www.nb.no/Hva-skjer/Aktuelt/Nyheter/Tapt-filmskatt-fra-Disney-funnet-i-Nasjonalbiblioteket
">annonserte
16 Nasjonalbiblioteket gladnyheten
</a
> om at de i sine arkiver hadde
17 funnet et nitratfilm-eksemplar av en
87 år gammel Disney-film ved navn
18 Empty Socks, en film som tidligere var antatt tapt og der det i følge
19 nyhetsmeldinger var kun ca.
25 sekunder bevart for ettertiden.
20 Nasjonalbiblioteket hadde
5 minutter og
30 sekunder av filmen i sitt
21 magasin. Dette er flott for bevaringen av verdens kulturarv.
5,
5
22 minutter mindre tapt enn vi trodde av får felles historie.
</p
>
24 <p
>Men hvordan kunne filmen gå tapt, når arkivlovene i USA krevde at
25 publiserte filmer på den tiden ble deponert i bibliotek? Forklaringen
26 har jeg fra Lawrence Lessig og boken Free Culture, som jeg holder på
27 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">å
28 oversette til norsk
</a
>:
</p
>
30 <p
><blockquote
>
31 <p
>Dette er delvis på grunn av loven. Opphavsrettseiere var tidlig i
32 amerikansk opphavsrettslov nødt til å deponere kopier av sine verk i
33 biblioteker. Disse kopiene skulle både sikre spredning av kunnskap,
34 og sikre at det fantes en kopi av verket tilgjengelig når vernetiden
35 utløp, slik at andre kunne få tilgang til og kopiere verket.
</p
>
37 <p
>Disse reglene gjaldt også for filmer. Men i
1915 gjorde
38 kongressbiblioteket et unntak for film. Filmer kunne bli
39 opphavsrettsbeskyttet så lenge det ble gjort slik deponering. Men
40 filmskaperne fikk så lov til å låne tilbake de deponerte filmene -
41 så lenge de ville uten noe kostnad. Bare i
1915 var det mer enn
5475
42 filmer deponert og “lånt tilbake”. Dermed var det ikke noe eksemplar
43 i noe bibliotek når vernetiden til filmen utløp. Eksemplaret
44 eksisterer - hvis den finnes i det hele tatt - i arkivbiblioteket
45 til filmselskapet.
</p
>
46 </blockquote
></p
>
48 <p
>Nyheten gjorde meg nysgjerrig på om filmen kunne være falt i det
49 fri. En
87 år gammel film kunne jo tenkes å ha blitt en del av
50 allemannseiet, slik at vi alle kan bruke den til å bygge videre på vår
51 felles kultur uten å måtte be om tillatelse - slik Walt Disney gjorde
52 det i starten av sin karriere. Jeg spurte nasjonalbiblioteket, og de
53 sa nei. Hvordan kan det ha seg med en så gammel film? En kan finne
54 informasjon om den norske vernetiden på
55 <a href=
"https://lovdata.no/dokument/NL/lov/
1961-
05-
12-
2">Lovdata
</a
>
56 og
</a
>Wikipedia
</A
>. Her er et relevant
<a
57 href=
"https://no.wikipedia.org/wiki/Opphavsrett#Vernetid
">utsnitt fra
58 siden om opphavsrett i den norske Wikipedia
</a
>:
</p
>
60 <p
><blockquote
>
61 Ifølge åndsverkloven §§
40-
41 utløper vernetiden for et åndsverk
70
62 år etter utløpet av opphavspersonens dødsår. [...] For filmverk
63 gjelder særlige regler: Her kommer ikke alle mulige opphavspersoner
64 i betraktning, men kun hovedregissøren, manusforfatteren,
65 dialogforfatteren og komponisten av filmmusikken. Vernetiden
66 begynner å løpe etter utgangen av dødsåret til den lengstlevende av
67 disse. [...] Der opphavspersonen er ukjent, utløper opphavsretten
70
68 år etter første kjente offentliggjørelse av verket. Det er kun de
69 økonomiske rettighetene som faller bort i det vernetiden er
70 utløpt. De ideelle rettighetene må fortsatt respekteres, noe som
71 blant annet innebærer at man plikter å navngi opphavspersonen ved
73 </blockquote
></p
>
75 <p
><a href=
"http://www.disneyshorts.org/shorts.aspx?shortID=
75">I følge
76 nettstedet X
</a
> er følgende personer gitt æren for denne
81 <dt
>Regissør
</dt
>
82 <dd
><a href=
"https://en.wikipedia.org/wiki/Walt_Disney
">Walt Disney
</a
> (
1901-
12-
05 –
1966-
12-
15) +
70 år =
2037</dd
>
85 <dd
><a href=
"https://en.wikipedia.org/wiki/Ub_Iwerks
">Ub Iwerks
</a
> (
1901-
03-
24 –
1971-
07-
07) +
70 år =
2042
86 <br
><a href=
"https://en.wikipedia.org/wiki/Rollin_Hamilton
">Rollin
"Ham
" Hamilton
</a
> (
1898-
10-
28 -
1951-
06-
03) +
70 år =
2022
87 <br
><a href=
"https://en.wikipedia.org/wiki/Harman_and_Ising
">Hugh Harman
</a
> (
1903-
08-
31 –
1982-
11-
25) +
70 år =
2053</dd
>
90 <dd
>Mike Marcus (?-?)
</dd
>
94 <p
>Alle fødsels- og dødsdatoene er fra engelske Wikipedia. Det er
95 ikke oppgitt navn på manusforfatter, dialogforfatter og komponist, men
96 jeg mistenker at tegnerne vil få opphavsrettigheter på tegnefilmer her
97 i Norge, og tar derfor med disse. Kameramannen vil ikke få noen
98 rettigheter så vidt jeg forstår, og er derfor ignorert her.
</p
>
100 <p
>Slik jeg forstår den norske opphavsretten vil dermed dette
101 filmverket bli allemannseie (også kalt å falle i det fri) i
2053,
126
102 år etter at det ble laget. Hvis kun regissørens rettigheter er
103 relevante, vil det skje i
2037,
110 år etter at det ble utgitt. Etter
104 det vil enhver kunne dele det med alle de har lyst til, fremføre det
105 offentlig eller klippe og lime i det for å lage sin egen film basert
106 på det - helt uten å måtte spørre noen om lov.
</p
>
108 <p
>Måtte så Nasjonalbiblioteket spørre om lov før de kunne kopiere
109 sitt nitrat-eksemplar over på mer varig format? Nei, heldigvis.
110 Åndsverklovens §
16 sier at arkiv, bibliotek, museer og undervisnings-
111 og forskningsinstitusjoner har rett til å fremstille eksemplar av verk
112 for konserverings- og sikringsformål og andre særskilte formål.
</p
>
117 <title>How to stay with sysvinit in Debian Jessie
</title>
118 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
119 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
120 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
121 <description><p
>By now, it is well known that Debian Jessie will not be using
122 sysvinit as its boot system by default. But how can one keep using
123 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
125 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
126 Schubert
</a
> and
127 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
130 <p
>If you already are using Wheezy and want to upgrade to Jessie and
131 keep sysvinit as your boot system, create a file
132 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
133 you upgrade:
</p
>
135 <p
><blockquote
><pre
>
136 Package: systemd-sysv
137 Pin: release o=Debian
139 </pre
></blockquote
><p
>
141 <p
>This file content will tell apt and aptitude to not consider
142 installing systemd-sysv as part of any installation and upgrade
143 solution when resolving dependencies, and thus tell it to avoid
144 systemd as a default boot system. The end result should be that the
145 upgraded system keep using sysvinit.
</p
>
147 <p
>If you are installing Jessie for the first time, there is no way to
148 get sysvinit installed by default (debootstrap used by
149 debian-installer have no option for this), but one can tell the
150 installer to switch to sysvinit before the first boot. Either by
151 using a kernel argument to the installer, or by adding a line to the
152 preseed file used. First, the kernel command line argument:
154 <p
><blockquote
><pre
>
155 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
156 </pre
></blockquote
><p
>
158 <p
>Next, the line to use in a preseed file:
</p
>
160 <p
><blockquote
><pre
>
161 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
162 </pre
></blockquote
><p
>
164 <p
>One can of course also do this after the first boot by installing
165 the sysvinit-core package.
</p
>
167 <p
>I recommend only using sysvinit if you really need it, as the
168 sysvinit boot sequence in Debian have several hardware specific bugs
169 on Linux caused by the fact that it is unpredictable when hardware
170 devices show up during boot. But on the other hand, the new default
171 boot system still have a few rough edges I hope will be fixed before
172 Jessie is released.
</p
>
174 <p
>Update
2014-
11-
26: Inspired by
175 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
176 blog post by Torsten Glaser
</a
>, added --purge to the preseed
182 <title>Hvordan vurderer regjeringen H
.264-patentutfordringen?
</title>
183 <link>http://people.skolelinux.org/pere/blog/Hvordan_vurderer_regjeringen_H_264_patentutfordringen_.html
</link>
184 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Hvordan_vurderer_regjeringen_H_264_patentutfordringen_.html
</guid>
185 <pubDate>Sun,
16 Nov
2014 10:
30:
00 +
0100</pubDate>
186 <description><p
>For en stund tilbake spurte jeg Fornyingsdepartementet om hvilke
187 juridiske vurderinger rundt patentproblemstillingen som var gjort da
188 H
.264 ble tatt inn i
<a href=
"http://standard.difi.no/
">statens
189 referansekatalog over standarder
</a
>. Stig Hornnes i FAD tipset meg
190 om følgende som står i oppsumeringen til høringen om
191 referansekatalogen versjon
2.0, som jeg siden ved hjelp av en
192 innsynsforespørsel fikk tak i
193 <a href=
"http://wiki.nuug.no/uttalelser/
200901-standardkatalog-v2?action=AttachFile
&do=get
&target=kongelig-resolusjon.pdf
">PDF-utgaven av
</a
>
194 datert
2009-
06-
03 (saksnummer
200803291, saksbehandler Henrik
195 Linnestad).
</p
>
197 <p
>Der står det følgende om problemstillingen:
</p
>
199 <p
><blockquote
>
200 <strong
>4.4 Patentproblematikk
</strong
>
202 <p
>NUUG og Opera ser det som særlig viktig at forslagene knyttet til
203 lyd og video baserer seg på de royalty-frie standardene Vorbis, Theora
206 <p
>Kommentarene relaterer seg til at enkelte standarder er åpne, men
207 inneholder tekniske prosedyrer som det i USA (og noen andre land som
208 Japan) er gitt patentrettigheter til. I vårt tilfelle berører dette
209 spesielt standardene Mp3 og H
.264, selv om Politidirektoratet peker på
210 at det muligens kan være tilsvarende problematikk også for Theora og
211 Vorbis. Dette medfører at det i USA kan kreves royalties for bruk av
212 tekniske løsninger knyttet til standardene, et krav som også
213 håndheves. Patenter kan imidlertid bare hevdes i de landene hvor
214 patentet er gitt, så amerikanske patenter gjelder ikke andre steder
217 <p
>Spesielt for utvikling av fri programvare er patenter
218 problematisk. GPL, en
"grunnleggende
" lisens for distribusjon av fri
219 programvare, avviser at programvare kan distribueres under denne
220 lisensen hvis det inneholder referanser til patenterte rutiner som
221 utløser krav om royalties. Det er imidlertid uproblematisk å
222 distribuere fri programvareløsninger under GPL som benytter de
223 aktuelle standardene innen eller mellom land som ikke anerkjenner
224 patentene. Derfor finner vi også flere implementeringer av Mp3 og
225 H
.264 som er fri programvare, lisensiert under GPL.
</p
>
227 <p
>I Norge og EU er patentlovgivningen langt mer restriktiv enn i USA,
228 men det er også her mulig å få patentert metoder for løsning av et
229 problem som relaterer seg til databehandling. Det er AIF bekjent ikke
230 relevante patenter i EU eller Norge hva gjelder H
.264 og Mp3, men
231 muligheten for at det finnes patenter uten at det er gjort krav om
232 royalties eller at det senere vil gis slike patenter kan ikke helt
235 <p
>AIF mener det er et behov for å gi offentlige virksomheter mulighet
236 til å benytte antatt royaltyfrie åpne standarder som et likeverdig
237 alternativ eller i tillegg til de markedsledende åpne standardene.
</p
>
239 </blockquote
></p
>
241 <p
>Det ser dermed ikke ut til at de har vurdert patentspørsmålet i
242 sammenheng med opphavsrettsvilkår slik de er formulert for f.eks.
243 Apple Final Cut Pro, Adobe Premiere Pro, Avid og Sorenson-verktøyene,
244 der det kreves brukstillatelse for patenter som ikke er gyldige i
245 Norge for å bruke disse verktøyene til annet en personlig og ikke
246 kommersiell aktivitet når det gjelder H
.264-video. Jeg må nok lete
247 videre etter svar på det spørsmålet.
</p
>
252 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
253 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
254 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
255 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
256 <description><p
>The right to communicate with your friends and family in private,
257 without anyone snooping, is a right every citicen have in a liberal
258 democracy. But this right is under serious attack these days.
</p
>
260 <p
>A while back it occurred to me that one way to make the dragnet
261 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
262 the whisleblower Snowden) more expensive for Internet email,
263 is to deliver all email using SMTP via Tor. Such SMTP option would be
264 a nice addition to the FreedomBox project if we could send email
265 between FreedomBox machines without leaking metadata about the emails
266 to the people peeking on the wire. I
267 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
268 this on the FreedomBox project mailing list in October
</a
> and got a
269 lot of useful feedback and suggestions. It also became obvious to me
270 that this was not a novel idea, as the same idea was tested and
271 documented by Johannes Berg as early as
2006, and both
272 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
273 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
274 propose a similar method / protocol to pass emails between users.
</p
>
276 <p
>To implement such system one need to set up a Tor hidden service
277 providing the SMTP protocol on port
25, and use email addresses
278 looking like username@hidden-service-name.onion. With such addresses
279 the connections to port
25 on hidden-service-name.onion using Tor will
280 go to the correct SMTP server. To do this, one need to configure the
281 Tor daemon to provide the hidden service and the mail server to accept
282 emails for this .onion domain. To learn more about Exim configuration
283 in Debian and test the design provided by Johannes Berg in his FAQ, I
284 set out yesterday to create a Debian package for making it trivial to
285 set up such SMTP over Tor service based on Debian. Getting it to work
286 were fairly easy, and
287 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
288 source code for the Debian package
</a
> is available from github. I
289 plan to move it into Debian if further testing prove this to be a
290 useful approach.
</p
>
292 <p
>If you want to test this, set up a blank Debian machine without any
293 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
294 get rid of exim4). Install tor, clone the git repository mentioned
295 above, build the deb and install it on the machine. Next, run
296 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
297 the instructions to get the service up and running. Restart tor and
298 exim when it is done, and test mail delivery using swaks like
301 <p
><blockquote
><pre
>
302 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
303 --to fbx@dutlqrrmjhtfa3vp.onion
304 </pre
></blockquote
></p
>
306 <p
>This will test the SMTP delivery using tor. Replace the email
307 address with your own address to test your server. :)
</p
>
309 <p
>The setup procedure is still to complex, and I hope it can be made
310 easier and more automatic. Especially the tor setup need more work.
311 Also, the package include a tor-smtp tool written in C, but its task
312 should probably be rewritten in some script language to make the deb
313 architecture independent. It would probably also make the code easier
314 to review. The tor-smtp tool currently need to listen on a socket for
315 exim to talk to it and is started using xinetd. It would be better if
316 no daemon and no socket is needed. I suspect it is possible to get
317 exim to run a command line tool for delivery instead of talking to a
318 socket, and hope to figure out how in a future version of this
321 <p
>Until I wipe my test machine, I can be reached using the
322 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
328 <title>First Jessie based Debian Edu released (alpha0)
</title>
329 <link>http://people.skolelinux.org/pere/blog/First_Jessie_based_Debian_Edu_released__alpha0_.html
</link>
330 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_Jessie_based_Debian_Edu_released__alpha0_.html
</guid>
331 <pubDate>Mon,
27 Oct
2014 20:
40:
00 +
0100</pubDate>
332 <description><p
>I am happy to report that I on behalf of the Debian Edu team just
334 <a href=
"https://lists.debian.org/debian-edu-announce/
2014/
10/msg00000.html
">this
335 announcement
</a
>:
</p
>
338 The Debian Edu Team is pleased to announce the release of Debian Edu
339 Jessie
8.0+edu0~alpha0
341 Debian Edu is a complete operating system for schools. Through its
342 various installation profiles you can install servers, workstations
343 and laptops which will work together on the school network. With
344 Debian Edu, the teachers themselves or their technical support can
345 roll out a complete multi-user multi-machine study environment within
346 hours or a few days. Debian Edu comes with hundreds of applications
347 pre-installed, but you can always add more packages from Debian.
349 For those who want to give Debian Edu Jessie a try, download and
350 installation instructions are available, including detailed
351 instructions in the manual[
1] explaining the first steps, such as
352 setting up a network or adding users. Please note that the password
353 for the user your prompted for during installation must have a length
354 of at least
5 characters!
356 [
1]
&lt;URL:
<a href=
"https://wiki.debian.org/DebianEdu/Documentation/Jessie
">https://wiki.debian.org/DebianEdu/Documentation/Jessie
</a
> &gt;
358 Would you like to give your school
's computer a longer life? Are you
359 tired of sneaker administration, running from computer to computer
360 reinstalling the operating system? Would you like to administrate all
361 the computers in your school using only a couple of hours every week?
362 Check out Debian Edu Jessie!
364 Skolelinux is used by at least two hundred schools all over the world,
365 mostly in Germany and Norway.
367 About Debian Edu and Skolelinux
368 ===============================
370 Debian Edu, also known as Skolelinux[
2], is a Linux distribution based
371 on Debian providing an out-of-the box environment of a completely
372 configured school network. Immediately after installation a school
373 server running all services needed for a school network is set up just
374 waiting for users and machines being added via GOsa², a comfortable
375 Web-UI. A netbooting environment is prepared using PXE, so after
376 initial installation of the main server from CD or USB stick all other
377 machines can be installed via the network. The provided school server
378 provides LDAP database and Kerberos authentication service,
379 centralized home directories, DHCP server, web proxy and many other
380 services. The desktop contains more than
60 educational software
381 packages[
3] and more are available from the Debian archive, and
382 schools can choose between KDE, Gnome, LXDE, Xfce and MATE desktop
385 [
2]
&lt;URL:
<a href=
"http://www.skolelinux.org/
">http://www.skolelinux.org/
</a
> &gt;
386 [
3]
&lt;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
> &gt;
388 Full release notes and manual
389 =============================
391 Below the download URLs there is a list of some of the new features
392 and bugfixes of Debian Edu
8.0+edu0~alpha0 Codename Jessie. The full
393 list is part of the manual. (See the feature list in the manual[
4] for
394 the English version.) For some languages manual translations are
395 available, see the manual translation overview[
5].
397 [
4]
&lt;URL:
<a href=
"https://wiki.debian.org/DebianEdu/Documentation/Jessie/Features
">https://wiki.debian.org/DebianEdu/Documentation/Jessie/Features
</a
> &gt;
398 [
5]
&lt;URL:
<a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">http://maintainer.skolelinux.org/debian-edu-doc/
</a
> &gt;
403 To download the multiarch netinstall CD release (
624 MiB) you can use
405 *
<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
>
406 *
<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
>
407 * rsync -avzP ftp.skolelinux.org::skolelinux-cd/debian-edu-
8.0+edu0~alpha0-CD.iso .
409 The SHA1SUM of this image is:
361188818e036ce67280a572f757de82ebfeb095
411 New features for Debian Edu
8.0+edu0~alpha0 Codename Jessie released
2014-
10-
27
412 ===============================================================================
418 * PXE installation now installs firmware automatically for the hardware present.
423 Everything which is new in Debian Jessie
8.0, eg:
425 * Linux kernel
3.16.x
426 * Desktop environments KDE
"Plasma
" 4.11.12, GNOME
3.14, Xfce
4.10,
427 LXDE
0.5.6 and MATE
1.8 (KDE
"Plasma
" is installed by default; to
428 choose one of the others see manual.)
429 * the browsers Iceweasel
31 ESR and Chromium
38
433 * CUPS print system
1.7.5
434 * new boot framework: systemd
435 * Educational toolbox GCompris
14.07
436 * Music creator Rosegarden
14.02
437 * Image editor Gimp
2.8.14
438 * Virtual stargazer Stellarium
0.13.0
441 * New version of debian-installer from Debian Jessie.
442 * Debian Jessie includes about
42000 packages available for
444 * More information about Debian Jessie
8.0 is provided in the release
445 notes[
6] and the installation manual[
7].
447 [
6]
&lt;URL:
<a href=
"http://www.debian.org/releases/jessie/releasenotes
">http://www.debian.org/releases/jessie/releasenotes
</a
> &gt;
448 [
7]
&lt;URL:
<a href=
"http://www.debian.org/releases/jessie/installmanual
">http://www.debian.org/releases/jessie/installmanual
</a
> &gt;
453 * Inserting incorrect DNS information in Gosa will no longer break
454 DNS completely, but instead stop DNS updates until the incorrect
455 information is corrected (Debian bug #
710362)
458 Documentation and translation updates
459 -------------------------------------
461 * The Debian Edu Jessie Manual is fully translated to German, French,
462 Italian, Danish and Dutch. Partly translated versions exist for
463 Norwegian Bokmal and Spanish.
468 * Due to new Squid settings, powering off or rebooting the main
469 server takes more time.
470 * To manage printers localhost:
631 has to be used, currently www:
631
473 Regressions / known problems
474 ----------------------------
476 * Installing LTSP chroot fails with a bug related to eatmydata about
477 exim4-config failing to run its postinst (see Debian bug #
765694
478 and Debian bug #
762103).
479 * Munin collection is not properly configured on clients (Debian bug
480 #
764594). The fix is available in a newer version of munin-node.
481 * PXE setup for Main Server and Thin Client Server setup does not
482 work when installing on a machine without direct Internet access.
483 Will be fixed when Debian bug #
766960 is fixed in Jessie.
485 See the status page[
8] for the complete list.
487 [
8]
&lt;URL:
<a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">https://wiki.debian.org/DebianEdu/Status/Jessie
</a
> &gt;
492 &lt;URL:
<a href=
"http://wiki.debian.org/DebianEdu/HowTo/ReportBugs
">http://wiki.debian.org/DebianEdu/HowTo/ReportBugs
</a
> &gt;
497 The Debian Project was founded in
1993 by Ian Murdock to be a truly
498 free community project. Since then the project has grown to be one of
499 the largest and most influential open source projects. Thousands of
500 volunteers from all over the world work together to create and
501 maintain Debian software. Available in
70 languages, and supporting a
502 huge range of computer types, Debian calls itself the universal
506 For further information, please visit the Debian web pages[
9] or send
507 mail to press@debian.org.
509 [
9]
&lt;URL:
<a href=
"http://www.debian.org/
">http://www.debian.org/
</a
> &gt;
515 <title>I spent last weekend recording MakerCon Nordic
</title>
516 <link>http://people.skolelinux.org/pere/blog/I_spent_last_weekend_recording_MakerCon_Nordic.html
</link>
517 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/I_spent_last_weekend_recording_MakerCon_Nordic.html
</guid>
518 <pubDate>Thu,
23 Oct
2014 23:
00:
00 +
0200</pubDate>
519 <description><p
>I spent last weekend at
<a href=
"http://www.makercon.no/
">Makercon
520 Nordic
</a
>, a great conference and workshop for makers in Norway and
521 the surrounding countries. I had volunteered on behalf of the
522 Norwegian Unix Users Group (NUUG) to video record the talks, and we
523 had a great and exhausting time recording the entire day, two days in
524 a row. There were only two of us, Hans-Petter and me, and we used the
525 regular video equipment for NUUG, with a
526 <a href=
"http://dvswitch.alioth.debian.org/wiki/
">dvswitch
</a
>, a
527 camera and a VGA to DV convert box, and mixed video and slides
530 <p
>Hans-Petter did the post-processing, consisting of uploading the
531 around
180 GiB of raw video to Youtube, and the result is
532 <a href=
"https://www.youtube.com/user/MakerConNordic/
">now becoming
533 public
</a
> on the MakerConNordic account. The videos have the license
534 NUUG always use on our recordings, which is
535 <a href=
"http://creativecommons.org/licenses/by-sa/
3.0/no/
">Creative
536 Commons Navngivelse-Del på samme vilkår
3.0 Norge
</a
>. Many great
537 talks available. Check it out! :)
</p
>
542 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
543 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
544 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
545 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
546 <description><p
>If you ever had to moderate a mailman list, like the ones on
547 alioth.debian.org, you know the web interface is fairly slow to
548 operate. First you visit one web page, enter the moderation password
549 and get a new page shown with a list of all the messages to moderate
550 and various options for each email address. This take a while for
551 every list you moderate, and you need to do it regularly to do a good
552 job as a list moderator. But there is a quick alternative,
553 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
554 listadmin program
</a
>. It allow you to check lists for new messages
555 to moderate in a fraction of a second. Here is a test run on two
556 lists I recently took over:
</p
>
558 <p
><blockquote
><pre
>
559 % time listadmin xiph
560 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
561 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
567 </pre
></blockquote
></p
>
569 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
570 there are no message in the moderation queue. Every morning I
571 currently moderate
68 mailman lists, and it normally take around two
572 minutes. When I took over the two pkg-xiph lists above a few days
573 ago, there were
400 emails waiting in the moderator queue. It took me
574 less than
15 minutes to process them all using the listadmin
577 <p
>If you install
578 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
579 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
580 with content like this, the moderation task is a breeze:
</p
>
582 <p
><blockquote
><pre
>
583 username username@example.org
586 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
589 adminurl https://{domain}/mailman/admindb/{list}
590 mailman-list@lists.example.com
593 other-list@otherserver.example.org
594 </pre
></blockquote
></p
>
596 <p
>There are other options to set as well. Check the manual page to
597 learn the details.
</p
>
599 <p
>If you are forced to moderate lists on a mailman installation where
600 the SSL certificate is self signed or not properly signed by a
601 generally accepted signing authority, you can set a environment
602 variable when calling listadmin to disable SSL verification:
</p
>
604 <p
><blockquote
><pre
>
605 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
606 </pre
></blockquote
></p
>
608 <p
>If you want to moderate a subset of the lists you take care of, you
609 can provide an argument to the listadmin script like I do in the
610 initial screen dump (the xiph argument). Using an argument, only
611 lists matching the argument string will be processed. This make it
612 quick to accept messages if you notice the moderation request in your
615 <p
>Without the listadmin program, I would never be the moderator of
68
616 mailing lists, as I simply do not have time to spend on that if the
617 process was any slower. The listadmin program have saved me hours of
618 time I could spend elsewhere over the years. It truly is nice free
621 <p
>As usual, if you use Bitcoin and want to show your support of my
622 activities, please send Bitcoin donations to my address
623 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
625 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
626 configuration example. Also, I
've been told that the
627 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
633 <title>Debian Jessie, PXE and automatic firmware installation
</title>
634 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
635 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
636 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
637 <description><p
>When PXE installing laptops with Debian, I often run into the
638 problem that the WiFi card require some firmware to work properly.
639 And it has been a pain to fix this using preseeding in Debian.
640 Normally something more is needed. But thanks to
641 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
642 package
</a
> and its recent tasksel extension, it has now become easy
643 to do this using simple preseeding.
</p
>
645 <p
>The isenkram-cli package provide tasksel tasks which will install
646 firmware for the hardware found in the machine (actually, requested by
647 the kernel modules for the hardware). (It can also install user space
648 programs supporting the hardware detected, but that is not the focus
649 of this story.)
</p
>
651 <p
>To get this working in the default installation, two preeseding
652 values are needed. First, the isenkram-cli package must be installed
653 into the target chroot (aka the hard drive) before tasksel is executed
654 in the pkgsel step of the debian-installer system. This is done by
655 preseeding the base-installer/includes debconf value to include the
656 isenkram-cli package. The package name is next passed to debootstrap
657 for installation. With the isenkram-cli package in place, tasksel
658 will automatically use the isenkram tasks to detect hardware specific
659 packages for the machine being installed and install them, because
660 isenkram-cli contain tasksel tasks.
</p
>
662 <p
>Second, one need to enable the non-free APT repository, because
663 most firmware unfortunately is non-free. This is done by preseeding
664 the apt-mirror-setup step. This is unfortunate, but for a lot of
665 hardware it is the only option in Debian.
</p
>
667 <p
>The end result is two lines needed in your preseeding file to get
668 firmware installed automatically by the installer:
</p
>
670 <p
><blockquote
><pre
>
671 base-installer base-installer/includes string isenkram-cli
672 apt-mirror-setup apt-setup/non-free boolean true
673 </pre
></blockquote
></p
>
675 <p
>The current version of isenkram-cli in testing/jessie will install
676 both firmware and user space packages when using this method. It also
677 do not work well, so use version
0.15 or later. Installing both
678 firmware and user space packages might give you a bit more than you
679 want, so I decided to split the tasksel task in two, one for firmware
680 and one for user space programs. The firmware task is enabled by
681 default, while the one for user space programs is not. This split is
682 implemented in the package currently in unstable.
</p
>
684 <p
>If you decide to give this a go, please let me know (via email) how
685 this recipe work for you. :)
</p
>
687 <p
>So, I bet you are wondering, how can this work. First and
688 foremost, it work because tasksel is modular, and driven by whatever
689 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
690 isenkram-cli package place two files for tasksel to find. First there
691 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
693 <p
><blockquote
><pre
>
694 Task: isenkram-packages
696 Description: Hardware specific packages (autodetected by isenkram)
697 Based on the detected hardware various hardware specific packages are
699 Test-new-install: show show
701 Packages: for-current-hardware
703 Task: isenkram-firmware
705 Description: Hardware specific firmware packages (autodetected by isenkram)
706 Based on the detected hardware various hardware specific firmware
707 packages are proposed.
708 Test-new-install: mark show
710 Packages: for-current-hardware-firmware
711 </pre
></blockquote
></p
>
713 <p
>The key parts are Test-new-install which indicate how the task
714 should be handled and the Packages line referencing to a script in
715 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
716 list of packages to install. The for-current-hardware-firmware script
717 look like this to list relevant firmware for the machine:
719 <p
><blockquote
><pre
>
724 isenkram-autoinstall-firmware -l
725 </pre
></blockquote
></p
>
727 <p
>With those two pieces in place, the firmware is installed by
728 tasksel during the normal d-i run. :)
</p
>
730 <p
>If you want to test what tasksel will install when isenkram-cli is
731 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
732 --new-install
</tt
> to get the list of packages that tasksel would
735 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
736 pilots in testing this feature, as isenkram is used there now to
737 install firmware, replacing the earlier scripts.
</p
>
742 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
743 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
744 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
745 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
746 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
747 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
748 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
749 on a screen normally showing the bread types and prizes:
</p
>
751 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
753 <p
>If it had booted as it was supposed to, I would never had known
754 about this hidden Linux installation. It is interesting what
755 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
760 <title>New lsdvd release version
0.17 is ready
</title>
761 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
762 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
763 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
764 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
765 got a new set of developers a few weeks ago, after the original
766 developer decided to step down and pass the project to fresh blood.
767 This project is now maintained by Petter Reinholdtsen and Steve
770 <p
>I just wrapped up
771 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
772 new lsdvd release
</a
>, available in git or from
773 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
774 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
779 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
780 <li
>Check for garbage in the program chains, which indicate that a track is
781 non-existant, to work around additional copy protection
</li
>
782 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
783 <li
>Fix pallete display of first entry
</li
>
784 <li
>Fix include orders
</li
>
785 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
786 <li
>Fix the chapter count
</li
>
787 <li
>Make sure the array size and the array limit used when initialising
788 the palette size is the same.
</li
>
789 <li
>Fix array printing.
</li
>
790 <li
>Correct subsecond calculations.
</li
>
791 <li
>Add sector information to the output format.
</li
>
792 <li
>Clean up code to be closer to ANSI C and compile without warnings
793 with more GCC compiler warnings.
</li
>
797 <p
>This change bring together patches for lsdvd in use in various
798 Linux and Unix distributions, as well as patches submitted to the
799 project the last nine years. Please check it out. :)
</p
>