1 <?xml version=
"1.0" encoding=
"ISO-8859-1"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries from November
2013</title>
5 <description>Entries from November
2013</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>Hvor godt fungerer Linux-klienter mot MS Exchange?
</title>
11 <link>http://people.skolelinux.org/pere/blog/Hvor_godt_fungerer_Linux_klienter_mot_MS_Exchange_.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Hvor_godt_fungerer_Linux_klienter_mot_MS_Exchange_.html
</guid>
13 <pubDate>Tue,
26 Nov
2013 18:
50:
00 +
0100</pubDate>
14 <description><p
>Jeg
15 <a href=
"http://people.skolelinux.org/pere/blog/_pent_m_te_p__onsdag_om_bruken_av_Microsoft_Exchange_ved_Universitetet_i_Oslo.html
">skrev
16 i juni om protestene
</a
> på planene til min arbeidsplass,
17 <a href=
"http://www.uio.no/
">Universitetet i Oslo
</a
>, om å gå bort fra
18 fri programvare- og åpne standardløsninger for å håndtere epost,
19 vekk fra IETF-standarden SIEVE for filtrering av epost og over til
20 godseide spesifikasjoner og epostsystemet Microsoft Exchange.
21 Protestene har fått litt ny omtale i media de siste dagene, i tillegg
22 til de oppslagene som kom i mai.
</p
>
26 <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
>
29 <a href=
"http://www.idg.no/computerworld/article279407.ece
">Microsoft-protest
30 på Universitetet
</a
> - Computerworld
</li
>
33 <a href=
"http://www.uniforum.uio.no/nyheter/
2013/
11/uio-bor-bruke-apen-programvare.html
">Kjemper
34 mot innføring av Microsoft Exchange på UiO
</a
> - Uniforum
</li
>
37 <a href=
"http://www.uniforum.uio.no/nyheter/
2013/
11/uio-utsetter-innforing-av-nytt-e-postsystem.html
">Utsetter
38 innføring av nytt e-postsystem
</a
> - Uniforum
</li
>
41 <a href=
"http://universitas.no/nyhet/
58462/forsvarer-nytt-it-system
">Forsvarer
42 nytt IT-system
</a
> - Universitas
</li
>
45 <a href=
"http://www.uniforum.uio.no/nyheter/
2013/
05/uio-innforer-nytt-epost-og-kalendersystem.html
">UiO
46 innfører nytt epost- og kalenderverktøy
</a
> - Uniforum
</li
>
49 <a href=
"http://universitas.no/nyhet/
58424/protestgruppe-vil-stanse-it-system
">Protestgruppe
50 vil stanse IT-system
</a
> - Universitas
</li
>
53 <a href=
"http://www.uniforum.uio.no/leserbrev/
2013/uio-ma-ha-kontroll-over-sitt-eget-epostsystem.html
">UiO
54 må ha kontroll over sitt eget epostsystem
</a
> - Uniforum
</li
>
58 <p
>Prosjektledelsen har fortalt at dette skal fungere like godt for
59 Linux-brukere som for brukere av Microsoft Windows og Apple MacOSX,
60 men jeg lurer på hva slags erfaringer Linux-brukere i eksisterende
61 miljøer som bruker MS Exchange har gjort. Hvis du har slik erfaring
62 hadet det vært veldig fint om du kan send et leserbrev til
63 <a href=
"http://www.uniforum.uio.no/
">Uniforum
</a
> og fortelle om hvor
64 greit det er å bruke Exchange i kryss-platform-miljøer? De jeg har
65 snakket med sier en greit får lest e-posten sin hvis Exchange har
66 slått på IMAP-funksjonalitet, men at kalender og møtebooking ikke
67 fungerer godt for Linux-klienter. Jeg har ingen personlig erfaring å
68 komme med, så jeg er nysgjerrig på hva andre kan dele av erfaringer
69 med universitetet.
</p
>
71 <p
>Mitt ankerpunkt mot å bytte ut fri programvare som fungerer godt
72 med godseid programvare er at en mister kontroll over egen
73 infrastruktur, låser seg inn i en løsning det vil bli dyrt å komme ut
74 av, uten at en får funksjonalitet en ikke kunne skaffet seg med fri
75 programvare, eventuelt videreutviklet med de pengene som brukes på
76 overgangen til MS Exchange. Personlig planlegger jeg å fortsette å
77 laste ned all eposten min til lokal maskin for indeksering og lesing
78 med
<a href==
"http://notmuchmail.org
">notmuch
</a
>, så jeg håper jeg
79 ikke blir veldig skadelidende av overgangen.
</p
>
81 <p
><a href=
"http://dinis.linguateca.pt/Diana/ImotMSUiO.html
">Underskriftslista
82 for oss som er mot endringen
</a
>, som omtales i artiklene, er fortsatt
83 åpen for de som vil signere på oppropet. Akkurat nå er det
298
84 personer som har signert.
</p
>
89 <title>New chrpath release
0.15</title>
90 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
91 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
92 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
93 <description><p
>After many years break from the package and a vain hope that
94 development would be continued by someone else, I finally pulled my
95 acts together this morning and wrapped up a new release of chrpath,
96 the command line tool to modify the rpath and runpath of already
97 compiled ELF programs. The update was triggered by the persistence of
98 Isha Vishnoi at IBM, which needed a new config.guess file to get
99 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
100 is working on. I checked the
101 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
102 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
103 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
104 packages for interesting patches (failed to find the source from
105 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
106 These are the release notes:
</p
>
108 <p
>New in
0.15 released
2013-
11-
24:
</p
>
112 <li
>Updated config.sub and config.guess from the GNU project to work
113 with newer architectures. Thanks to isha vishnoi for the heads
116 <li
>Updated README with current URLs.
</li
>
118 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
119 Matthias Klose.
</li
>
121 <li
>Added missing help for -k|--keepgoing option, using patch by
122 Petr Machata found in Fedora.
</li
>
124 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
125 .dynamic is a NULL terminated string. Based on patch found in
126 Fedora credited Axel Thimm and Christian Krause.
</li
>
131 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
132 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
133 project if something is wrong with the new release. The test suite
134 did not discover any old errors, so if you find a new one, please also
135 include a testsuite check.
</p
>
140 <title>RSS-kilde for fritekstsøk i offentlige anbud hos Doffin
</title>
141 <link>http://people.skolelinux.org/pere/blog/RSS_kilde_for_friteksts_k_i_offentlige_anbud_hos_Doffin.html
</link>
142 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/RSS_kilde_for_friteksts_k_i_offentlige_anbud_hos_Doffin.html
</guid>
143 <pubDate>Fri,
22 Nov
2013 13:
40:
00 +
0100</pubDate>
144 <description><p
>I fjor sommer lagde jeg en
145 <a href=
"http://people.skolelinux.org/pere/blog/SQL_database_med_anbud_publisert_p__Doffin.html
">offentlig
146 tilgjengelig SQL-database over offentlig anbud
</a
> basert på skraping
147 av HTML-data fra Doffin. Den har stått og gått siden da, og har nå
148 ca.
28000 oppføringer. Jeg oppdaget da jeg tittet innom at noen
149 oppføringer var ikke blitt med, antagelig på grunn av at de fikk
150 tildelt sekvensnummer i Doffin en godt stund før de ble publisert,
151 slik at min nettsideskraper som fortsatte skrapingen der den slapp
152 sist ikke fikk dem med seg. Jeg har fikset litt slik at skraperen nå
153 ser litt tilbake i tid for å se om den har gått glipp av noen
154 oppføringer, og har skrapet på nytt fra midten av september
2013 og
155 fremover. Det bør dermed bli en mer komplett database for kommende
156 måneder. Hvis jeg får tid skal jeg forsøke å skrape
"glemte
" data fra
157 før midten av september
2013, men tør ikke garantere at det blir
158 prioritert med det første.
</p
>
160 <p
>Men målet med denne bloggposten er å vise hvordan denne
161 Doffin-databasen kan brukes og integreres med en RSS-leser, slik at en
162 kan la datamaskinen holde et øye med Doffin-annonseringer etter
163 nøkkelord. En kan lage sitt eget søk ved å besøke
164 <ahref=
"https://classic.scraperwiki.com/docs/api?name=norwegian-doffin#sqlite
">API-et
165 hos Scraperwiki
</a
>, velge format rss2 og så legge inn noe ala dette i
166 "query in SQL
":
</p
>
169 select title, scrapedurl as link, abstract as description,
170 publishdate as pubDate from
'swdata
'
171 where abstract like
'%linux%
' or title like
'%linux%
'
172 order by seq desc limit
20
173 </pre
></p
>
175 <p
>Dette vil søke opp alle anbud med ordet linux i oppsummering eller
176 tittel. En kan lage mer avanserte søk hvis en ønsker det. URL-en som
177 dukker opp nederst på siden kan en så gi til sin RSS-leser (jeg bruker
178 akregator selv), og så automatisk få beskjed hvis det dukker opp anbud
179 med det aktuelle nøkkelordet i teksten. Merk at kapasiteten og
180 ytelsen hos Scraperwiki er begrenset, så ikke be RSS-leseren hente ned
181 oftere enn en gang hver dag.
</p
>
183 <p
>Du lurer kanskje på hva slags informasjon en kan få ut fra denne
184 databasen. Her er to RSS-kilder, med søkeordet
185 "<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
>",
187 "<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
188 programvare
</a
>"
190 "<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
>".
191 Det er bare å søke på det en er interessert i. Kopier gjerne
192 datasettet og sett opp din egen tjeneste hvis du vil gjøre mer
193 avanserte søk. SQLite-filen med Doffin-oppføringer kan lastes med fra
194 Scraperwiki for de som vil grave dypere.
</p
>
199 <title>All drones should be radio marked with what they do and who they belong to
</title>
200 <link>http://people.skolelinux.org/pere/blog/All_drones_should_be_radio_marked_with_what_they_do_and_who_they_belong_to.html
</link>
201 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/All_drones_should_be_radio_marked_with_what_they_do_and_who_they_belong_to.html
</guid>
202 <pubDate>Thu,
21 Nov
2013 15:
40:
00 +
0100</pubDate>
203 <description><p
>Drones, flying robots, are getting more and more popular. The most
204 know ones are the killer drones used by some government to murder
205 people they do not like without giving them the chance of a fair
206 trial, but the technology have many good uses too, from mapping and
207 forest maintenance to photography and search and rescue. I am sure it
208 is just a question of time before
"bad drones
" are in the hands of
209 private enterprises and not only state criminals but petty criminals
210 too. The drone technology is very useful and very dangerous. To have
211 some control over the use of drones, I agree with Daniel Suarez in his
213 "<a href=
"https://archive.org/details/DanielSuarez_2013G
">The kill
214 decision shouldn
't belong to a robot
</a
>", where he suggested this
215 little gem to keep the good while limiting the bad use of drones:
</p
>
219 <p
>Each robot and drone should have a cryptographically signed
220 I.D. burned in at the factory that can be used to track its movement
221 through public spaces. We have license plates on cars, tail numbers on
222 aircraft. This is no different. And every citizen should be able to
223 download an app that shows the population of drones and autonomous
224 vehicles moving through public spaces around them, both right now and
225 historically. And civic leaders should deploy sensors and civic drones
226 to detect rogue drones, and instead of sending killer drones of their
227 own up to shoot them down, they should notify humans to their
228 presence. And in certain very high-security areas, perhaps civic
229 drones would snare them and drag them off to a bomb disposal facility.
</p
>
231 <p
>But notice, this is more an immune system than a weapons system. It
232 would allow us to avail ourselves of the use of autonomous vehicles
233 and drones while still preserving our open, civil society.
</p
>
237 <p
>The key is that
<em
>every citizen
</em
> should be able to read the
238 radio beacons sent from the drones in the area, to be able to check
239 both the government and others use of drones. For such control to be
240 effective, everyone must be able to do it. What should such beacon
241 contain? At least formal owner, purpose, contact information and GPS
242 location. Probably also the origin and target position of the current
243 flight. And perhaps some registration number to be able to look up
244 the drone in a central database tracking their movement. Robots
245 should not have privacy. It is people who need privacy.
</p
>
250 <title>Lets make a wireless community network in Oslo!
</title>
251 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_wireless_community_network_in_Oslo_.html
</link>
252 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_a_wireless_community_network_in_Oslo_.html
</guid>
253 <pubDate>Wed,
13 Nov
2013 21:
00:
00 +
0100</pubDate>
254 <description><p
>Today NUUG and Hackeriet announced
255 <a href=
"http://www.nuug.no/news/Bli_med___bygge_dugnadsnett_for_alle_i_Oslo.shtml
">our
256 plans to join forces and create a wireless community network in
257 Oslo
</a
>. The workshop to help people get started will take place
258 Thursday
2013-
11-
28, but we already are collecting the geolocation of
259 people joining forces to make this happen. We have
260 <a href=
"https://github.com/petterreinholdtsen/meshfx-node/blob/master/oslo-nodes.geojson
">9
261 locations plotted on the map
</a
>, but we will need more before we have
262 a connected mesh spread across Oslo. If this sound interesting to
263 you, please join us at the workshop. If you are too impatient to wait
264 15 days, please join us on the IRC channel
265 <a href=
"irc://irc.freenode.net/%
23nuug
">#nuug on irc.freenode.net
</a
>
266 right away. :)
</p
>
271 <title>Running TP-Link MR3040 as a batman-adv mesh node using openwrt
</title>
272 <link>http://people.skolelinux.org/pere/blog/Running_TP_Link_MR3040_as_a_batman_adv_mesh_node_using_openwrt.html
</link>
273 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Running_TP_Link_MR3040_as_a_batman_adv_mesh_node_using_openwrt.html
</guid>
274 <pubDate>Sun,
10 Nov
2013 23:
00:
00 +
0100</pubDate>
275 <description><p
>Continuing my research into mesh networking, I was recommended to
276 use TP-Link
3040 and
3600 access points as mesh nodes, and the pair I
277 bought arrived on Friday. Here are my notes on how to set up the
278 MR3040 as a mesh node using
279 <a href=
"http://www.openwrt.org/
">OpenWrt
</a
>.
</p
>
281 <p
>I started by following the instructions on the OpenWRT wiki for
282 <a href=
"http://wiki.openwrt.org/toh/tp-link/tl-mr3040
">TL-MR3040
</a
>,
284 <a href=
"http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin
">the
285 recommended firmware image
</a
>
286 (openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin) and
287 uploaded it into the original web interface. The flashing went fine,
288 and the machine was available via telnet on the ethernet port. After
289 logging in and setting the root password, ssh was available and I
290 could start to set it up as a batman-adv mesh node.
</p
>
292 <p
>I started off by reading the instructions from
293 <a href=
"http://wirelessafrica.meraka.org.za/wiki/index.php?title=Antoine
's_Research
">Wireless
294 Africa
</a
>, which had quite a lot of useful information, but
295 eventually I followed the recipe from the Open Mesh wiki for
296 <a href=
"http://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config
">using
297 batman-adv on OpenWrt
</a
>. A small snag was the fact that the
298 <tt
>opkg install kmod-batman-adv
</tt
> command did not work as it
299 should. The batman-adv kernel module would fail to load because its
300 dependency crc16 was not already loaded. I
301 <a href=
"https://dev.openwrt.org/ticket/
14452">reported the bug
</a
> to
302 the openwrt project and hope it will be fixed soon. But the problem
303 only seem to affect initial testing of batman-adv, as configuration
304 seem to work when booting from scratch.
</p
>
306 <p
>The setup is done using files in /etc/config/. I did not bridge
307 the Ethernet and mesh interfaces this time, to be able to hook up the
308 box on my local network and log into it for configuration updates.
309 The following files were changed and look like this after modifying
312 <p
><tt
>/etc/config/network
</tt
></p
>
316 config interface
'loopback
'
317 option ifname
'lo
'
318 option proto
'static
'
319 option ipaddr
'127.0.0.1'
320 option netmask
'255.0.0.0'
322 config globals
'globals
'
323 option ula_prefix
'fdbf:
4c12:
3fed::/
48'
325 config interface
'lan
'
326 option ifname
'eth0
'
327 option type
'bridge
'
328 option proto
'dhcp
'
329 option ipaddr
'192.168.1.1'
330 option netmask
'255.255.255.0'
331 option hostname
'tl-mr3040
'
332 option ip6assign
'60'
334 config interface
'mesh
'
335 option ifname
'adhoc0
'
336 option mtu
'1528'
337 option proto
'batadv
'
338 option mesh
'bat0
'
341 <p
><tt
>/etc/config/wireless
</tt
></p
>
344 config wifi-device
'radio0
'
345 option type
'mac80211
'
346 option channel
'11'
347 option hwmode
'11ng
'
348 option path
'platform/ar933x_wmac
'
349 option htmode
'HT20
'
350 list ht_capab
'SHORT-GI-
20'
351 list ht_capab
'SHORT-GI-
40'
352 list ht_capab
'RX-STBC1
'
353 list ht_capab
'DSSS_CCK-
40'
354 option disabled
'0'
356 config wifi-iface
'wmesh
'
357 option device
'radio0
'
358 option ifname
'adhoc0
'
359 option network
'mesh
'
360 option encryption
'none
'
361 option mode
'adhoc
'
362 option bssid
'02:BA:
00:
00:
00:
01'
363 option ssid
'meshfx@hackeriet
'
365 <p
><tt
>/etc/config/batman-adv
</tt
></p
>
368 config
'mesh
' 'bat0
'
369 option interfaces
'adhoc0
'
370 option
'aggregated_ogms
'
371 option
'ap_isolation
'
372 option
'bonding
'
373 option
'fragmentation
'
374 option
'gw_bandwidth
'
375 option
'gw_mode
'
376 option
'gw_sel_class
'
377 option
'log_level
'
378 option
'orig_interval
'
379 option
'vis_mode
'
380 option
'bridge_loop_avoidance
'
381 option
'distributed_arp_table
'
382 option
'network_coding
'
383 option
'hop_penalty
'
385 # yet another batX instance
386 # config
'mesh
' 'bat5
'
387 # option
'interfaces
' 'second_mesh
'
390 <p
>The mesh node is now operational. I have yet to test its range,
391 but I hope it is good. I have not yet tested the TP-Link
3600 box
392 still wrapped up in plastic.
</p
>
397 <title>Debian init.d boot script example for rsyslog
</title>
398 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
399 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
400 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
401 <description><p
>If one of the points of switching to a new init system in Debian is
402 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
403 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
404 init.d scripts at all. Here is an example init.d script, ie a rewrite
405 of /etc/init.d/rsyslog:
</p
>
408 #!/lib/init/init-d-script
411 # Required-Start: $remote_fs $time
412 # Required-Stop: umountnfs $time
413 # X-Stop-After: sendsigs
414 # Default-Start:
2 3 4 5
415 # Default-Stop:
0 1 6
416 # Short-Description: enhanced syslogd
417 # Description: Rsyslog is an enhanced multi-threaded syslogd.
418 # It is quite compatible to stock sysklogd and can be
419 # used as a drop-in replacement.
421 DESC=
"enhanced syslogd
"
422 DAEMON=/usr/sbin/rsyslogd
423 </pre
></p
>
425 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
426 script was
137 lines, and the above is just
15 lines, most of it meta
427 info/comments.
</p
>
429 <p
>How to do this, you ask? Well, one create a new script
430 /lib/init/init-d-script looking something like this:
435 # Define LSB log_* functions.
436 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
437 # and status_of_proc is working.
438 . /lib/lsb/init-functions
441 # Function that starts the daemon/service
447 #
0 if daemon has been started
448 #
1 if daemon was already running
449 #
2 if daemon could not be started
450 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
452 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
455 # Add code here, if necessary, that waits for the process to be ready
456 # to handle requests from services started subsequently which depend
457 # on this one. As a last resort, sleep for some time.
461 # Function that stops the daemon/service
466 #
0 if daemon has been stopped
467 #
1 if daemon was already stopped
468 #
2 if daemon could not be stopped
469 # other if a failure occurred
470 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
471 RETVAL=
"$?
"
472 [
"$RETVAL
" =
2 ]
&& return
2
473 # Wait for children to finish too if this is a daemon that forks
474 # and if the daemon is only ever run from this initscript.
475 # If the above conditions are not satisfied then add some other code
476 # that waits for the process to drop all resources that could be
477 # needed by services started subsequently. A last resort is to
478 # sleep for some time.
479 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
480 [
"$?
" =
2 ]
&& return
2
481 # Many daemons don
't delete their pidfiles when they exit.
483 return
"$RETVAL
"
487 # Function that sends a SIGHUP to the daemon/service
491 # If the daemon can reload its configuration without
492 # restarting (for example, when it is sent a SIGHUP),
493 # then implement that here.
495 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
500 scriptbasename=
"$(basename $
1)
"
501 echo
"SN: $scriptbasename
"
502 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
503 script=
"$
1"
510 NAME=$(basename $DAEMON)
511 PIDFILE=/var/run/$NAME.pid
513 # Exit if the package is not installed
514 #[ -x
"$DAEMON
" ] || exit
0
516 # Read configuration variable file if it is present
517 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
519 # Load the VERBOSE setting and other rcS variables
522 case
"$
1" in
524 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
526 case
"$?
" in
527 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
528 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
532 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
534 case
"$?
" in
535 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
536 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
540 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
542 #reload|force-reload)
544 # If do_reload() is not implemented then leave this commented out
545 # and leave
'force-reload
' as an alias for
'restart
'.
547 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
551 restart|force-reload)
553 # If the
"reload
" option is implemented then remove the
554 #
'force-reload
' alias
556 log_daemon_msg
"Restarting $DESC
" "$NAME
"
558 case
"$?
" in
561 case
"$?
" in
563 1) log_end_msg
1 ;; # Old process is still running
564 *) log_end_msg
1 ;; # Failed to start
574 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
580 </pre
></p
>
582 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
583 lot. I did not really polish the approach, so it might not always
584 work out of the box, but you get the idea. I did not try very hard to
585 optimize it nor make it more robust either.
</p
>
587 <p
>A better argument for switching init system in Debian than reducing
588 the size of init scripts (which is a good thing to do anyway), is to
589 get boot system that is able to handle the kernel events sensibly and
590 robustly, and do not depend on the boot to run sequentially. The boot
591 and the kernel have not behaved sequentially in years.
</p
>
596 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
597 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
598 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
599 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
600 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
601 remote display access is the preferred solution with oVirt and RedHat
602 Enterprise Virtualization, and I was sad to discover the other day
603 that the browser plugin needed to use these systems seamlessly was
604 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
605 for a package
</a
> was from
2012-
04-
10 with no progress since
606 2013-
04-
01, so I decided to wrap up a package based on the great work
607 from Cajus Pollmeier and put it in a collab-maint maintained git
608 repository to get a package I could use. I would very much like
609 others to help me maintain the package (or just take over, I do not
610 mind), but as no-one had volunteered so far, I just uploaded it to
611 NEW. I hope it will be available in Debian in a few days.
</p
>
613 <p
>The source is now available from
614 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary
">http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary
</a
>.
</p
>