]> pere.pagekite.me Git - homepage.git/blob - blog/archive/2012/12/12.rss
Generated.
[homepage.git] / blog / archive / 2012 / 12 / 12.rss
1 <?xml version="1.0" encoding="ISO-8859-1"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
3 <channel>
4 <title>Petter Reinholdtsen - Entries from December 2012</title>
5 <description>Entries from December 2012</description>
6 <link>https://people.skolelinux.org/pere/blog/</link>
7
8
9 <item>
10 <title>A Christmas present for Skolelinux / Debian Edu</title>
11 <link>https://people.skolelinux.org/pere/blog/A_Christmas_present_for_Skolelinux___Debian_Edu.html</link>
12 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_Christmas_present_for_Skolelinux___Debian_Edu.html</guid>
13 <pubDate>Fri, 28 Dec 2012 09:20:00 +0100</pubDate>
14 <description>&lt;p&gt;I was happy to discover a few days ago that the
15 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt;
16 project also this year received a Christmas present from Another
17 Agency in Trondheim. NOK 1000,- showed up on our donation account
18 December 24th. I want to express our thanks for this very welcome
19 present. As the Debian Edu / Skolelinux project is very short on
20 funding these days, and thus lack the money to do regular developer
21 gatherings, this donation was most welcome. One developer gathering
22 cost around NOK 15&amp;nbsp;000,-, so we need quite a lot more to keep the
23 development pace we want. Thus, I hope their example this year is
24 followed by many others. :)&lt;/p&gt;
25
26 &lt;p&gt;The public list of donors can be found on
27 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;the
28 donation page&lt;/a&gt; for the project, which also contain instructions if
29 you want to donate to the project.&lt;/p&gt;
30 </description>
31 </item>
32
33 <item>
34 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
35 <link>https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
36 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
37 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
38 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
39 year! I hope next year will prove to be a good year.&lt;/p&gt;
40
41 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
42 decentralised &quot;currency&quot; that allow people to transfer bitcoins
43 between each other with minimal overhead, is a very interesting
44 experiment. And as I wrote a few days ago, the bitcoin situation in
45 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
46 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
47 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
48 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
49 for one of the ftpmasters to approve the new bitcoin-qt package
50 name.&lt;/p&gt;
51
52 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
53 team in Debian, you can easily test the package in Debian Squeeze
54 using the following steps to get a set of working packages:&lt;/p&gt;
55
56 &lt;blockquote&gt;&lt;pre&gt;
57 git clone git://git.debian.org/git/collab-maint/bitcoin
58 cd bitcoin
59 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
60 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
61 &lt;/pre&gt;&lt;/blockquote&gt;
62
63 &lt;p&gt;You might have to install some build dependencies as well. The
64 list of commands should give you two packages, bitcoind and
65 bitcoin-qt, ready for use in a Squeeze environment. Note that the
66 client will download the complete set of bitcoin &quot;blocks&quot;, which need
67 around 5.6 GiB of data on my machine at the moment. Make sure your
68 ~/.bitcoin/ directory have lots of spare room if you want to download
69 all the blocks. The client will warn if the disk is getting full, so
70 there is not really a problem if you got too little room, but you will
71 not be able to get all the features out of the client.&lt;/p&gt;
72
73 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
74 activities, please send Bitcoin donations to my address
75 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
76 </description>
77 </item>
78
79 <item>
80 <title>A word on bitcoin support in Debian</title>
81 <link>https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
82 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
83 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
84 <description>&lt;p&gt;It has been a while since I wrote about
85 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
86 peer-to-peer based crypto-currency, and the reason is simply that I
87 have been busy elsewhere. But two days ago, I started looking at the
88 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
89 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
90 is now maintained by a
91 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
92 people&lt;/a&gt;, and the grunt work had already been done by this team. We
93 owe a huge thank you to all these team members. :)
94 But I was sad to discover that the bitcoin client is missing in
95 Wheezy. It is only available in Sid (and an outdated client from
96 backports). The client had several RC bugs registered in BTS blocking
97 it from entering testing. To try to help the team and improve the
98 situation, I spent some time providing patches and triaging the bug
99 reports. I also had a look at the bitcoin package available from Matt
100 Corallo in a
101 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
102 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
103 Debian package.&lt;/p&gt;
104
105 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
106 IRC, I pushed several patches into the collab-maint git repository to
107 improve the package. It now contains fixes for the RC issues (not from
108 me, but fixed by Scott Howard), build rules for a Qt GUI client
109 package, konqueror support for the bitcoin: URI and bash completion
110 setup. As I work on Debian Squeeze, I also created
111 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
112 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
113 it and try to integrate it into the git repository before uploading a
114 new version to unstable.
115
116 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
117 centralized control currently exercised in the monetary system. I
118 find it completely unacceptable that the USA government is collecting
119 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
120 that the major credit card companies can block legal money
121 transactions to Wikileaks. But for bitcoin to succeed, more people
122 need to use bitcoins, and more people need to accept bitcoins when
123 they sell products and services. Improving the bitcoin support in
124 Debian is a small step in the right direction, but not enough.
125 Unfortunately the user experience when browsing the web and wanting to
126 pay with bitcoin is still not very good. The bitcoin: URI is a step
127 in the right direction, but need to work in most or every browser in
128 use. Also the bitcoin-qt client is too heavy to fire up to do a
129 quick transaction. I believe there are other clients available, but
130 have not tested them.&lt;/p&gt;
131
132 &lt;p&gt;My
133 &lt;a href=&quot;https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
134 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
135 I received 20.15 BTC so far on the address I provided in my blog two
136 years ago, as can be
137 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
138 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
139 donation. The blockexplorer service demonstrates quite well that
140 bitcoin is not quite anonymous and untracked. :) I wonder if the
141 number of users have gone up since then. If you use bitcoin and want
142 to show your support of my activity, please send Bitcoin donations to
143 the same address as last time,
144 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
145 </description>
146 </item>
147
148 <item>
149 <title>Piratpartiet på opphavs-retrett?</title>
150 <link>https://people.skolelinux.org/pere/blog/Piratpartiet_p__opphavs_retrett_.html</link>
151 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Piratpartiet_p__opphavs_retrett_.html</guid>
152 <pubDate>Wed, 19 Dec 2012 13:10:00 +0100</pubDate>
153 <description>&lt;p&gt;Jeg ble overrasket over å se at Piratpartiet i
154 &lt;a href=&quot;http://www.aftenposten.no/kultur/Piratpartiet-stiller-til-Stortingsvalget-7073298.html&quot;&gt;Aftenposten&lt;/a&gt;
155 er referert på følgende:&lt;/p&gt;
156
157 &lt;blockquote&gt;
158 Når det gjelder retten til opphavsrett for kulturproduktene, mener
159 Piratpartiet av levetid + 14 år er tilfredsstillende.
160 &lt;/blockquote&gt;
161
162 &lt;p&gt;Det betyr en vernetid langt ut over det kommersielle livet til de
163 aller fleste opphavsrettsbeskyttede verker, og er i strid med slik i
164 hvert fall jeg har tolket punkt 5 i
165 &lt;a href=&quot;http://people.opera.com/howcome/2012/piratpartiet/kjerneprogram.html&quot;&gt;kjerneprogrammet
166 til Piratpartiet&lt;/a&gt;:&lt;/p&gt;
167
168 &lt;blockquote&gt;
169 &lt;p&gt;&lt;strong&gt;5: Åndsverk og patenter: tilbake til start&lt;/strong&gt;&lt;/p&gt;
170
171 &lt;table border=&quot;1&quot;&gt;
172 &lt;tr&gt;&lt;th&gt;forslag:&lt;/th&gt;&lt;td&gt;14 års opphavsrett og ingen
173 programvarepatenter&lt;/td&gt;&lt;/tr&gt;
174
175 &lt;tr&gt;&lt;th&gt;grunn:&lt;/th&gt;&lt;td&gt;Den første loven om opphavsrett spesifiserte 14
176 års vernetid. Senere har mediabransjens lobbyister stadig presset
177 loven mot lengre vern, nå er det 70 år etter forfatters død. Dette
178 gjør at mange verk glemmes og går tapt, noe som er skadelig for norsk
179 språk og kultur. Vi til tilbake til start: 14 års
180 vernetid. Patentloven sier klart at dataprogrammer ikke kan
181 patenteres. Likevel klarer patentadvokater å lure gjennom
182 programvarepatenter. Slike patenter gjør dingsene våre dyrere og kan i
183 enkelte tilfelle stoppe dem helt.&lt;/th&gt;&lt;/tr&gt;
184 &lt;/table&gt;
185 &lt;/blockquote&gt;
186
187 &lt;p&gt;Den opprinnelige opphavsretten var på 14 år totalt, ikke 14 år
188 etter opphavspersonens død. Jeg tenkte først dette kanskje var
189 feilsitering fra Aftenposten, men jeg finner samme påstand i en &lt;a
190 href=&quot;http://piratpartietnorge.org/om-gramo-og-piratpolitikken/&quot;&gt;bloggpost
191 fra Geir Aaslid&lt;/a&gt; på Piratpartietes offisielle nettsider. Der
192 skriver han følgende:&lt;/p&gt;
193
194 &lt;blockquote&gt;
195 Hva vi gjør med opphavsretten er mer komplisert fordi den omfavner så
196 mange bransjer, med ulike behov. Enhver reform er en forbedring men
197 det er nærliggende å anta at en opphavsrett på levetid + 14 år er
198 fullt ut tilfredstillende for musikk, film, litteratur og spill.
199 &lt;/blockquote&gt;
200
201 &lt;p&gt;Det virker dermed på meg som om Piratpartiet allerede har gjort
202 retrett fra sin beundringsverdige holdning om at det holdt med 14 års
203 total vernetid, til sin nye som tar utgangspunkt i levetiden til
204 opphavspersonen. Jeg håper det baserer seg på en misforståelse hos
205 piratlederen som blir korrigert tilbake til 14 års total vernetid før
206 partiet stiller til valg.&lt;/p&gt;
207
208 &lt;p&gt;Hvis du lurer på hvilke problemer lang vernetid bringer med seg,
209 anbefaler jeg å lese boken &lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free
210 Culture&lt;/a&gt; av Lawrence Lessig. Jeg og en liten gruppe andre er igang
211 med å
212 &lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;oversette
213 boken til bokmål&lt;/a&gt; og tar gjerne imot hjelp med oversettelse og
214 korrekturlesing.&lt;/p&gt;
215
216 &lt;p&gt;&lt;strong&gt;Oppdatering 2012-12-20&lt;/strong&gt;: Oppdaget at
217 &lt;a href=&quot;http://piratpartietnorge.org/om-gramo-og-piratpolitikken/&quot;&gt;bloggposten
218 til Geir Aaslid&lt;/a&gt; er endret siden i går, og nå inneholder følgende
219 avsnitt i stedet for det jeg siterte over:&lt;/p&gt;
220
221 &lt;blockquote&gt;
222 Hva vi gjør med opphavsretten er mer komplisert fordi den omfavner så
223 mange bransjer, med ulike behov. Enhver reform er en forbedring men
224 det er nærliggende å anta at en opphavsrett lik levetiden, evt + 14 år
225 er fullt ut tilfredstillende for mange skapere av musikk, film,
226 litteratur og spill. Det er for det meste de store forlagene som er
227 imot enhver reform.
228 &lt;/blockquote&gt;
229
230 &lt;p&gt;I tillegg har det dukket opp en setning nederst &quot;Dette dokumentet
231 er et utkast til svar på et angrep på Piratpartiet fra Gramo. Det
232 endrer seg derfor over tid og den endelige versjonen er det som blir
233 publisert på Hardware.no&quot;, som tyder på at originalformuleringen ikke
234 var veloverveid og sitatet i Aftenposten kanskje var basert på en
235 misforståelse.&lt;/p&gt;
236 </description>
237 </item>
238
239 <item>
240 <title>Ledger - double-entry accounting using text based storage format</title>
241 <link>https://people.skolelinux.org/pere/blog/Ledger___double_entry_accounting_using_text_based_storage_format.html</link>
242 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Ledger___double_entry_accounting_using_text_based_storage_format.html</guid>
243 <pubDate>Tue, 18 Dec 2012 23:30:00 +0100</pubDate>
244 <description>&lt;p&gt;A few days ago I came across
245 &lt;a href=&quot;http://joeyh.name/blog/entry/hledger/&quot;&gt;a blog post from Joey
246 Hess&lt;/a&gt; describing &lt;a href=&quot;http://ledger-cli.org/&quot;&gt;ledger&lt;/a&gt; and
247 hledger, a text based system for double-entry accounting. I found it
248 interesting, as I am involved with several organizations where
249 accounting is an issue, and I have not really become too friendly with
250 the different web based systems we use. I find it hard to find what I
251 look for in the menus and even harder try to get sensible data out of
252 the systems. Ledger seem different. The accounting data is kept in
253 text files that can be stored in a version control system, and there
254
255 are at least &lt;a href=&quot;https://github.com/ledger/ledger/wiki/Ports&quot;&gt;five
256 different implementations&lt;/a&gt; able to read the format. An example
257 entry look like this, and is simple enough that it will be trivial to
258 generate entries based on CVS files fetched from the bank:&lt;/p&gt;
259
260 &lt;blockquote&gt;&lt;pre&gt;
261 2004-05-27 Book Store
262 Expenses:Books $20.00
263 Liabilities:Visa
264 &lt;/pre&gt;&lt;/blockquote&gt;
265
266 &lt;p&gt;The concept seemed interesting enough for me to check it out and
267 look for others using it. I found blog posts from
268 &lt;a href=&quot;http://blog.spang.cc/posts/hledger_rocks_my_world/&quot;&gt;Christine
269 Spang&lt;/a&gt;,
270 &lt;a href=&quot;http://bugsplat.info/2010-05-23-keeping-finances-with-ledger.html&quot;&gt;Pete
271 Keen&lt;/a&gt;,
272 &lt;a href=&quot;http://blog.andrewcantino.com/blog/2010/11/06/command-line-accounting-with-ledger-and-reckon/&quot;&gt;Andrew
273 Cantino&lt;/a&gt; and
274 &lt;a href=&quot;http://blog.iphoting.com/blog/2012/11/29/command-line-double-entry-accounting/&quot;&gt;Ronald
275 Ip&lt;/a&gt; describing how they use it, as well as a post from
276 &lt;a href=&quot;https://groups.google.com/forum/?fromgroups=#!topic/ledger-cli/r0oWjwbQ9Bo&quot;&gt;Bradley
277 M. Kuhn&lt;/a&gt; at the Software Freedom Conservancy. All seemed like good
278 recommendations fitting my need.&lt;/p&gt;
279
280 &lt;p&gt;The &lt;a href=&quot;http://packages.qa.debian.org/l/ledger.html&quot;&gt;ledger&lt;/a&gt;
281 package is available in Debian Squeeze, while the
282 &lt;a href=&quot;http://packages.qa.debian.org/h/haskell-hledger.html&quot;&gt;hledger&lt;/a&gt;
283 package only is available in Debian Sid. As I use Squeeze, ledger
284 seemed the best choice to get started.&lt;/p&gt;
285
286 &lt;p&gt;To get some real data to test on, I wrote a
287 &lt;a href=&quot;http://www.nuug.no/tools/lodo2ledger&quot;&gt;web scraper&lt;/a&gt; for
288 &lt;a href=&quot;http://www.lodo.no/&quot;&gt;LODO&lt;/a&gt;, the accounting system used by
289 the &lt;a href=&quot;http://www.nuug.no/&quot;&gt;NUUG&lt;/a&gt; association, and started to
290 play with the data set. I&#39;m not really deeply into accounting, but I
291 am able to get a simple balance and accounting status for example
292 using the &quot;&lt;tt&gt;ledger balance&lt;/tt&gt;&quot; command. But I will have to
293 gather more experience before I know if the ledger way is a good fit
294 for the organisations I am involved in.&lt;/p&gt;
295 </description>
296 </item>
297
298 <item>
299 <title>61 kommuner lenker nå til FiksGataMi fra sine nettsider</title>
300 <link>https://people.skolelinux.org/pere/blog/61_kommuner_lenker_n__til_FiksGataMi_fra_sine_nettsider.html</link>
301 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/61_kommuner_lenker_n__til_FiksGataMi_fra_sine_nettsider.html</guid>
302 <pubDate>Tue, 11 Dec 2012 23:55:00 +0100</pubDate>
303 <description>&lt;p&gt;For noen dager siden omfavnet nok en kommune NUUGs
304 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt;. Med 61 kommuner
305 som lenker til FiksGataMi fra sine hjemmesider er «markedsandelen» 14%
306 (av 429 kommuner). Siden
307 &lt;a href=&quot;https://people.skolelinux.org/pere/blog/59_kommuner_omfavner_n__FiksGataMi.html&quot;&gt;siste
308 oppdatering i november&lt;/a&gt; har kommunene Re og Vågsøy kommet til og
309 slår følge med kommunene Askim, Askøy, Audnedal, Aure, Balestrand,
310 Bærum, Eide, Farsund, Flekkefjord, Folldal, Gran, Grue, Hadsel,
311 Halden, Halsa, Hamar, Hobøl, Holtålen, Hægebostad, Høyanger,
312 Kongsberg, Kristiansund, Kvinesdal, Kviteseid, Levanger, Lindesnes,
313 Luster, Lyngdal, Løten, Mandal, Marnardal, Moss, Namsos, Nissedal,
314 Nordreisa, Randaberg, Rindal, Sel, Sirdal, Skiptvet, Sortland,
315 Spydeberg, Stange, Stjørdal, Stord, Søgne, Sør-Odal, Tolga, Trysil,
316 Tynset, Tysvær, Ullensvang Herad, Utsira, Vennesla, Verdal, Vågan,
317 Vågå, Våler og Åseral. Oppdatert liste er tilgjengelig fra
318 &lt;a href=&quot;http://wiki.nuug.no/grupper/fiksgatami/positivemottakere&quot;&gt;NUUGs
319 wiki&lt;/a&gt;. Kartet er dog ikke oppdatert med de siste kommunene.&lt;/p&gt;
320
321 &lt;p&gt;Kanskje du bør høre med din kommune om de vil bli mer aktive
322 brukere av FiksGataMi? Se
323 &lt;a href=&quot;https://people.skolelinux.org/pere/blog/40_kommuner_lenker_n__til_FiksGataMi_fra_sine_nettsider___gj_r_din_.html&quot;&gt;en
324 tidligere bloggpost&lt;/a&gt; med tips om hvordan det kan gjøres.&lt;/p&gt;
325
326 &lt;p&gt;I snitt rapporteres det nå via FiksGataMi ca. 60 meldinger fra
327 innbyggerne i uka om feil på offentlig infrastruktur.&lt;/p&gt;
328 </description>
329 </item>
330
331 <item>
332 <title>Scripting the Cerebrum/bofhd user administration system using XML-RPC</title>
333 <link>https://people.skolelinux.org/pere/blog/Scripting_the_Cerebrum_bofhd_user_administration_system_using_XML_RPC.html</link>
334 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Scripting_the_Cerebrum_bofhd_user_administration_system_using_XML_RPC.html</guid>
335 <pubDate>Thu, 6 Dec 2012 10:30:00 +0100</pubDate>
336 <description>&lt;p&gt;Where I work at the &lt;a href=&quot;http://www.uio.no/&quot;&gt;University of
337 Oslo&lt;/a&gt;, we use the
338 &lt;a href=&quot;http://sourceforge.net/projects/cerebrum/&quot;&gt;Cerebrum user
339 administration system&lt;/a&gt; to maintain users, groups, DNS, DHCP, etc.
340 I&#39;ve known since the system was written that the server is providing
341 an &lt;a href=&quot;http://en.wikipedia.org/wiki/XML-RPC&quot;&gt;XML-RPC&lt;/a&gt; API, but
342 I have never spent time to try to figure out how to use it, as we
343 always use the bofh command line client at work. Until today. I want
344 to script the updating of DNS and DHCP to make it easier to set up
345 virtual machines. Here are a few notes on how to use it with
346 Python.&lt;/p&gt;
347
348 &lt;p&gt;I started by looking at the source of the Java
349 &lt;a href=&quot;http://cerebrum.svn.sourceforge.net/viewvc/cerebrum/trunk/cerebrum/clients/jbofh/&quot;&gt;bofh
350 client&lt;/a&gt;, to figure out how it connected to the API server. I also
351 googled for python examples on how to use XML-RPC, and found
352 &lt;a href=&quot;http://tldp.org/HOWTO/XML-RPC-HOWTO/xmlrpc-howto-python.html&quot;&gt;a
353 simple example in&lt;/a&gt; the XML-RPC howto.&lt;/p&gt;
354
355 &lt;p&gt;This simple example code show how to connect, get the list of
356 commands (as a JSON dump), and how to get the information about the
357 user currently logged in:&lt;/p&gt;
358
359 &lt;blockquote&gt;&lt;pre&gt;
360 #!/usr/bin/env python
361 import getpass
362 import xmlrpclib
363 server_url = &#39;https://cerebrum-uio.uio.no:8000&#39;;
364 username = getpass.getuser()
365 password = getpass.getpass()
366 server = xmlrpclib.Server(server_url);
367 #print server.get_commands(sessionid)
368 sessionid = server.login(username, password)
369 print server.run_command(sessionid, &quot;user_info&quot;, username)
370 result = server.logout(sessionid)
371 print result
372 &lt;/pre&gt;&lt;/blockquote&gt;
373
374 &lt;p&gt;Armed with this knowledge I can now move forward and script the DNS
375 and DHCP updates I wanted to do.&lt;/p&gt;
376 </description>
377 </item>
378
379 </channel>
380 </rss>