X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/cb2bffc9f0c093d20f059990477781700cd1f6a8..b6b6575e368fa0e8d3ac34a3a09aa1e21132be0e:/blog/index.rss diff --git a/blog/index.rss b/blog/index.rss index 36e4780002..6f8847277d 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -6,6 +6,556 @@ http://people.skolelinux.org/pere/blog/ + + Some notes on fault tolerant storage systems + http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html + http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html + Wed, 1 Nov 2017 15:35:00 +0100 + <p>If you care about how fault tolerant your storage is, you might +find these articles and papers interesting. They have formed how I +think of when designing a storage system.</p> + +<ul> + +<li>USENIX :login; <a +href="https://www.usenix.org/publications/login/summer2017/ganesan">Redundancy +Does Not Imply Fault Tolerance. Analysis of Distributed Storage +Reactions to Single Errors and Corruptions</a> by Aishwarya Ganesan, +Ramnatthan Alagappan, Andrea C. Arpaci-Dusseau, and Remzi +H. Arpaci-Dusseau</li> + +<li>ZDNet +<a href="http://www.zdnet.com/article/why-raid-5-stops-working-in-2009/">Why +RAID 5 stops working in 2009</a> by Robin Harris</li> + +<li>ZDNet +<a href="http://www.zdnet.com/article/why-raid-6-stops-working-in-2019/">Why +RAID 6 stops working in 2019</a> by Robin Harris</li> + +<li>USENIX FAST'07 +<a href="http://research.google.com/archive/disk_failures.pdf">Failure +Trends in a Large Disk Drive Population</a> by Eduardo Pinheiro, +Wolf-Dietrich Weber and Luiz André Barroso</li> + +<li>USENIX ;login: <a +href="https://www.usenix.org/system/files/login/articles/hughes12-04.pdf">Data +Integrity. Finding Truth in a World of Guesses and Lies</a> by Doug +Hughes</li> + +<li>USENIX FAST'08 +<a href="https://www.usenix.org/events/fast08/tech/full_papers/bairavasundaram/bairavasundaram_html/">An +cAnalysis of Data Corruption in the Storage Stack</a> by +L. N. Bairavasundaram, G. R. Goodson, B. Schroeder, A. C. +Arpaci-Dusseau, and R. H. Arpaci-Dusseau</li> + +<li>USENIX FAST'07 <a +href="https://www.usenix.org/legacy/events/fast07/tech/schroeder/schroeder_html/">Disk +failures in the real world: what does an MTTF of 1,000,000 hours mean +to you?</a> by B. Schroeder and G. A. Gibson.</li> + +<li>USENIX ;login: <a +href="https://www.usenix.org/events/fast08/tech/full_papers/jiang/jiang_html/">Are +Disks the Dominant Contributor for Storage Failures? A Comprehensive +Study of Storage Subsystem Failure Characteristics</a> by Weihang +Jiang, Chongfeng Hu, Yuanyuan Zhou, and Arkady Kanevsky</li> + +<li>SIGMETRICS 2007 +<a href="http://research.cs.wisc.edu/adsl/Publications/latent-sigmetrics07.pdf">An +analysis of latent sector errors in disk drives</a> by +L. N. Bairavasundaram, G. R. Goodson, S. Pasupathy, and J. Schindler</li> + +</ul> + +<p>Several of these research papers are based on data collected from +hundred thousands or millions of disk, and their findings are eye +opening. The short story is simply do not implicitly trust RAID or +redundant storage systems. Details matter. And unfortunately there +are few options on Linux addressing all the identified issues. Both +ZFS and Btrfs are doing a fairly good job, but have legal and +practical issues on their own. I wonder how cluster file systems like +Ceph do in this regard. After, all the old saying, you know you have +a distributed system when the crash of a compyter you have never heard +of stops you from getting any work done. The same holds true if fault +tolerance do not work.</p> + +<p>Just remember, in the end, it do not matter how redundant, or how +fault tolerant your storage is, if you do not continuously monitor its +status to detect and replace failed disks.</p> + + + + + Web services for writing academic LaTeX papers as a team + http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html + http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html + Tue, 31 Oct 2017 21:00:00 +0100 + <p>I was surprised today to learn that a friend in academia did not +know there are easily available web services available for writing +LaTeX documents as a team. I thought it was common knowledge, but to +make sure at least my readers are aware of it, I would like to mention +these useful services for writing LaTeX documents. Some of them even +provide a WYSIWYG editor to ease writing even further.</p> + +<p>There are two commercial services available, +<a href="https://sharelatex.com">ShareLaTeX</a> and +<a href="https://overleaf.com">Overleaf</a>. They are very easy to +use. Just start a new document, select which publisher to write for +(ie which LaTeX style to use), and start writing. Note, these two +have announced their intention to join forces, so soon it will only be +one joint service. I've used both for different documents, and they +work just fine. While +<a href="https://github.com/sharelatex/sharelatex">ShareLaTeX is free +software</a>, while the latter is not. According to <a +href="https://www.overleaf.com/help/17-is-overleaf-open-source">a +announcement from Overleaf</a>, they plan to keep the ShareLaTeX code +base maintained as free software.</p> + +But these two are not the only alternatives. +<a href="https://app.fiduswriter.org/">Fidus Writer</a> is another free +software solution with <a href="https://github.com/fiduswriter">the +source available on github</a>. I have not used it myself. Several +others can be found on the nice +<a href="https://alternativeto.net/software/sharelatex/">alterntiveTo +web service</a>. + +<p>If you like Google Docs or Etherpad, but would like to write +documents in LaTeX, you should check out these services. You can even +host your own, if you want to. :)</p> + + + + + + Locating IMDB IDs of movies in the Internet Archive using Wikidata + http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html + http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html + Wed, 25 Oct 2017 12:20:00 +0200 + <p>Recently, I needed to automatically check the copyright status of a +set of <a href="http://www.imdb.com/">The Internet Movie database +(IMDB)</a> entries, to figure out which one of the movies they refer +to can be freely distributed on the Internet. This proved to be +harder than it sounds. IMDB for sure list movies without any +copyright protection, where the copyright protection has expired or +where the movie is lisenced using a permissive license like one from +Creative Commons. These are mixed with copyright protected movies, +and there seem to be no way to separate these classes of movies using +the information in IMDB.</p> + +<p>First I tried to look up entries manually in IMDB, +<a href="https://www.wikipedia.org/">Wikipedia</a> and +<a href="https://www.archive.org/">The Internet Archive</a>, to get a +feel how to do this. It is hard to know for sure using these sources, +but it should be possible to be reasonable confident a movie is "out +of copyright" with a few hours work per movie. As I needed to check +almost 20,000 entries, this approach was not sustainable. I simply +can not work around the clock for about 6 years to check this data +set.</p> + +<p>I asked the people behind The Internet Archive if they could +introduce a new metadata field in their metadata XML for IMDB ID, but +was told that they leave it completely to the uploaders to update the +metadata. Some of the metadata entries had IMDB links in the +description, but I found no way to download all metadata files in bulk +to locate those ones and put that approach aside.</p> + +<p>In the process I noticed several Wikipedia articles about movies +had links to both IMDB and The Internet Archive, and it occured to me +that I could use the Wikipedia RDF data set to locate entries with +both, to at least get a lower bound on the number of movies on The +Internet Archive with a IMDB ID. This is useful based on the +assumption that movies distributed by The Internet Archive can be +legally distributed on the Internet. With some help from the RDF +community (thank you DanC), I was able to come up with this query to +pass to <a href="https://query.wikidata.org/">the SPARQL interface on +Wikidata</a>: + +<p><pre> +SELECT ?work ?imdb ?ia ?when ?label +WHERE +{ + ?work wdt:P31/wdt:P279* wd:Q11424. + ?work wdt:P345 ?imdb. + ?work wdt:P724 ?ia. + OPTIONAL { + ?work wdt:P577 ?when. + ?work rdfs:label ?label. + FILTER(LANG(?label) = "en"). + } +} +</pre></p> + +<p>If I understand the query right, for every film entry anywhere in +Wikpedia, it will return the IMDB ID and The Internet Archive ID, and +when the movie was released and its English title, if either or both +of the latter two are available. At the moment the result set contain +2338 entries. Of course, it depend on volunteers including both +correct IMDB and The Internet Archive IDs in the wikipedia articles +for the movie. It should be noted that the result will include +duplicates if the movie have entries in several languages. There are +some bogus entries, either because The Internet Archive ID contain a +typo or because the movie is not available from The Internet Archive. +I did not verify the IMDB IDs, as I am unsure how to do that +automatically.</p> + +<p>I wrote a small python script to extract the data set from Wikidata +and check if the XML metadata for the movie is available from The +Internet Archive, and after around 1.5 hour it produced a list of 2097 +free movies and their IMDB ID. In total, 171 entries in Wikidata lack +the refered Internet Archive entry. I assume the 70 "disappearing" +entries (ie 2338-2097-171) are duplicate entries.</p> + +<p>This is not too bad, given that The Internet Archive report to +contain <a href="https://archive.org/details/feature_films">5331 +feature films</a> at the moment, but it also mean more than 3000 +movies are missing on Wikipedia or are missing the pair of references +on Wikipedia.</p> + +<p>I was curious about the distribution by release year, and made a +little graph to show how the amount of free movies is spread over the +years:<p> + +<p><img src="http://people.skolelinux.org/pere/blog/images/2017-10-25-verk-i-det-fri-filmer.png"></p> + +<p>I expect the relative distribution of the remaining 3000 movies to +be similar.</p> + +<p>If you want to help, and want to ensure Wikipedia can be used to +cross reference The Internet Archive and The Internet Movie Database, +please make sure entries like this are listed under the "External +links" heading on the Wikipedia article for the movie:</p> + +<p><pre> +* {{Internet Archive film|id=FightingLady}} +* {{IMDb title|id=0036823|title=The Fighting Lady}} +</pre></p> + +<p>Please verify the links on the final page, to make sure you did not +introduce a typo.</p> + +<p>Here is the complete list, if you want to correct the 171 +identified Wikipedia entries with broken links to The Internet +Archive: <a href="http://www.wikidata.org/entity/Q1140317">Q1140317</a>, +<a href="http://www.wikidata.org/entity/Q458656">Q458656</a>, +<a href="http://www.wikidata.org/entity/Q458656">Q458656</a>, +<a href="http://www.wikidata.org/entity/Q470560">Q470560</a>, +<a href="http://www.wikidata.org/entity/Q743340">Q743340</a>, +<a href="http://www.wikidata.org/entity/Q822580">Q822580</a>, +<a href="http://www.wikidata.org/entity/Q480696">Q480696</a>, +<a href="http://www.wikidata.org/entity/Q128761">Q128761</a>, +<a href="http://www.wikidata.org/entity/Q1307059">Q1307059</a>, +<a href="http://www.wikidata.org/entity/Q1335091">Q1335091</a>, +<a href="http://www.wikidata.org/entity/Q1537166">Q1537166</a>, +<a href="http://www.wikidata.org/entity/Q1438334">Q1438334</a>, +<a href="http://www.wikidata.org/entity/Q1479751">Q1479751</a>, +<a href="http://www.wikidata.org/entity/Q1497200">Q1497200</a>, +<a href="http://www.wikidata.org/entity/Q1498122">Q1498122</a>, +<a href="http://www.wikidata.org/entity/Q865973">Q865973</a>, +<a href="http://www.wikidata.org/entity/Q834269">Q834269</a>, +<a href="http://www.wikidata.org/entity/Q841781">Q841781</a>, +<a href="http://www.wikidata.org/entity/Q841781">Q841781</a>, +<a href="http://www.wikidata.org/entity/Q1548193">Q1548193</a>, +<a href="http://www.wikidata.org/entity/Q499031">Q499031</a>, +<a href="http://www.wikidata.org/entity/Q1564769">Q1564769</a>, +<a href="http://www.wikidata.org/entity/Q1585239">Q1585239</a>, +<a href="http://www.wikidata.org/entity/Q1585569">Q1585569</a>, +<a href="http://www.wikidata.org/entity/Q1624236">Q1624236</a>, +<a href="http://www.wikidata.org/entity/Q4796595">Q4796595</a>, +<a href="http://www.wikidata.org/entity/Q4853469">Q4853469</a>, +<a href="http://www.wikidata.org/entity/Q4873046">Q4873046</a>, +<a href="http://www.wikidata.org/entity/Q915016">Q915016</a>, +<a href="http://www.wikidata.org/entity/Q4660396">Q4660396</a>, +<a href="http://www.wikidata.org/entity/Q4677708">Q4677708</a>, +<a href="http://www.wikidata.org/entity/Q4738449">Q4738449</a>, +<a href="http://www.wikidata.org/entity/Q4756096">Q4756096</a>, +<a href="http://www.wikidata.org/entity/Q4766785">Q4766785</a>, +<a href="http://www.wikidata.org/entity/Q880357">Q880357</a>, +<a href="http://www.wikidata.org/entity/Q882066">Q882066</a>, +<a href="http://www.wikidata.org/entity/Q882066">Q882066</a>, +<a href="http://www.wikidata.org/entity/Q204191">Q204191</a>, +<a href="http://www.wikidata.org/entity/Q204191">Q204191</a>, +<a href="http://www.wikidata.org/entity/Q1194170">Q1194170</a>, +<a href="http://www.wikidata.org/entity/Q940014">Q940014</a>, +<a href="http://www.wikidata.org/entity/Q946863">Q946863</a>, +<a href="http://www.wikidata.org/entity/Q172837">Q172837</a>, +<a href="http://www.wikidata.org/entity/Q573077">Q573077</a>, +<a href="http://www.wikidata.org/entity/Q1219005">Q1219005</a>, +<a href="http://www.wikidata.org/entity/Q1219599">Q1219599</a>, +<a href="http://www.wikidata.org/entity/Q1643798">Q1643798</a>, +<a href="http://www.wikidata.org/entity/Q1656352">Q1656352</a>, +<a href="http://www.wikidata.org/entity/Q1659549">Q1659549</a>, +<a href="http://www.wikidata.org/entity/Q1660007">Q1660007</a>, +<a href="http://www.wikidata.org/entity/Q1698154">Q1698154</a>, +<a href="http://www.wikidata.org/entity/Q1737980">Q1737980</a>, +<a href="http://www.wikidata.org/entity/Q1877284">Q1877284</a>, +<a href="http://www.wikidata.org/entity/Q1199354">Q1199354</a>, +<a href="http://www.wikidata.org/entity/Q1199354">Q1199354</a>, +<a href="http://www.wikidata.org/entity/Q1199451">Q1199451</a>, +<a href="http://www.wikidata.org/entity/Q1211871">Q1211871</a>, +<a href="http://www.wikidata.org/entity/Q1212179">Q1212179</a>, +<a href="http://www.wikidata.org/entity/Q1238382">Q1238382</a>, +<a href="http://www.wikidata.org/entity/Q4906454">Q4906454</a>, +<a href="http://www.wikidata.org/entity/Q320219">Q320219</a>, +<a href="http://www.wikidata.org/entity/Q1148649">Q1148649</a>, +<a href="http://www.wikidata.org/entity/Q645094">Q645094</a>, +<a href="http://www.wikidata.org/entity/Q5050350">Q5050350</a>, +<a href="http://www.wikidata.org/entity/Q5166548">Q5166548</a>, +<a href="http://www.wikidata.org/entity/Q2677926">Q2677926</a>, +<a href="http://www.wikidata.org/entity/Q2698139">Q2698139</a>, +<a href="http://www.wikidata.org/entity/Q2707305">Q2707305</a>, +<a href="http://www.wikidata.org/entity/Q2740725">Q2740725</a>, +<a href="http://www.wikidata.org/entity/Q2024780">Q2024780</a>, +<a href="http://www.wikidata.org/entity/Q2117418">Q2117418</a>, +<a href="http://www.wikidata.org/entity/Q2138984">Q2138984</a>, +<a href="http://www.wikidata.org/entity/Q1127992">Q1127992</a>, +<a href="http://www.wikidata.org/entity/Q1058087">Q1058087</a>, +<a href="http://www.wikidata.org/entity/Q1070484">Q1070484</a>, +<a href="http://www.wikidata.org/entity/Q1080080">Q1080080</a>, +<a href="http://www.wikidata.org/entity/Q1090813">Q1090813</a>, +<a href="http://www.wikidata.org/entity/Q1251918">Q1251918</a>, +<a href="http://www.wikidata.org/entity/Q1254110">Q1254110</a>, +<a href="http://www.wikidata.org/entity/Q1257070">Q1257070</a>, +<a href="http://www.wikidata.org/entity/Q1257079">Q1257079</a>, +<a href="http://www.wikidata.org/entity/Q1197410">Q1197410</a>, +<a href="http://www.wikidata.org/entity/Q1198423">Q1198423</a>, +<a href="http://www.wikidata.org/entity/Q706951">Q706951</a>, +<a href="http://www.wikidata.org/entity/Q723239">Q723239</a>, +<a href="http://www.wikidata.org/entity/Q2079261">Q2079261</a>, +<a href="http://www.wikidata.org/entity/Q1171364">Q1171364</a>, +<a href="http://www.wikidata.org/entity/Q617858">Q617858</a>, +<a href="http://www.wikidata.org/entity/Q5166611">Q5166611</a>, +<a href="http://www.wikidata.org/entity/Q5166611">Q5166611</a>, +<a href="http://www.wikidata.org/entity/Q324513">Q324513</a>, +<a href="http://www.wikidata.org/entity/Q374172">Q374172</a>, +<a href="http://www.wikidata.org/entity/Q7533269">Q7533269</a>, +<a href="http://www.wikidata.org/entity/Q970386">Q970386</a>, +<a href="http://www.wikidata.org/entity/Q976849">Q976849</a>, +<a href="http://www.wikidata.org/entity/Q7458614">Q7458614</a>, +<a href="http://www.wikidata.org/entity/Q5347416">Q5347416</a>, +<a href="http://www.wikidata.org/entity/Q5460005">Q5460005</a>, +<a href="http://www.wikidata.org/entity/Q5463392">Q5463392</a>, +<a href="http://www.wikidata.org/entity/Q3038555">Q3038555</a>, +<a href="http://www.wikidata.org/entity/Q5288458">Q5288458</a>, +<a href="http://www.wikidata.org/entity/Q2346516">Q2346516</a>, +<a href="http://www.wikidata.org/entity/Q5183645">Q5183645</a>, +<a href="http://www.wikidata.org/entity/Q5185497">Q5185497</a>, +<a href="http://www.wikidata.org/entity/Q5216127">Q5216127</a>, +<a href="http://www.wikidata.org/entity/Q5223127">Q5223127</a>, +<a href="http://www.wikidata.org/entity/Q5261159">Q5261159</a>, +<a href="http://www.wikidata.org/entity/Q1300759">Q1300759</a>, +<a href="http://www.wikidata.org/entity/Q5521241">Q5521241</a>, +<a href="http://www.wikidata.org/entity/Q7733434">Q7733434</a>, +<a href="http://www.wikidata.org/entity/Q7736264">Q7736264</a>, +<a href="http://www.wikidata.org/entity/Q7737032">Q7737032</a>, +<a href="http://www.wikidata.org/entity/Q7882671">Q7882671</a>, +<a href="http://www.wikidata.org/entity/Q7719427">Q7719427</a>, +<a href="http://www.wikidata.org/entity/Q7719444">Q7719444</a>, +<a href="http://www.wikidata.org/entity/Q7722575">Q7722575</a>, +<a href="http://www.wikidata.org/entity/Q2629763">Q2629763</a>, +<a href="http://www.wikidata.org/entity/Q2640346">Q2640346</a>, +<a href="http://www.wikidata.org/entity/Q2649671">Q2649671</a>, +<a href="http://www.wikidata.org/entity/Q7703851">Q7703851</a>, +<a href="http://www.wikidata.org/entity/Q7747041">Q7747041</a>, +<a href="http://www.wikidata.org/entity/Q6544949">Q6544949</a>, +<a href="http://www.wikidata.org/entity/Q6672759">Q6672759</a>, +<a href="http://www.wikidata.org/entity/Q2445896">Q2445896</a>, +<a href="http://www.wikidata.org/entity/Q12124891">Q12124891</a>, +<a href="http://www.wikidata.org/entity/Q3127044">Q3127044</a>, +<a href="http://www.wikidata.org/entity/Q2511262">Q2511262</a>, +<a href="http://www.wikidata.org/entity/Q2517672">Q2517672</a>, +<a href="http://www.wikidata.org/entity/Q2543165">Q2543165</a>, +<a href="http://www.wikidata.org/entity/Q426628">Q426628</a>, +<a href="http://www.wikidata.org/entity/Q426628">Q426628</a>, +<a href="http://www.wikidata.org/entity/Q12126890">Q12126890</a>, +<a href="http://www.wikidata.org/entity/Q13359969">Q13359969</a>, +<a href="http://www.wikidata.org/entity/Q13359969">Q13359969</a>, +<a href="http://www.wikidata.org/entity/Q2294295">Q2294295</a>, +<a href="http://www.wikidata.org/entity/Q2294295">Q2294295</a>, +<a href="http://www.wikidata.org/entity/Q2559509">Q2559509</a>, +<a href="http://www.wikidata.org/entity/Q2559912">Q2559912</a>, +<a href="http://www.wikidata.org/entity/Q7760469">Q7760469</a>, +<a href="http://www.wikidata.org/entity/Q6703974">Q6703974</a>, +<a href="http://www.wikidata.org/entity/Q4744">Q4744</a>, +<a href="http://www.wikidata.org/entity/Q7766962">Q7766962</a>, +<a href="http://www.wikidata.org/entity/Q7768516">Q7768516</a>, +<a href="http://www.wikidata.org/entity/Q7769205">Q7769205</a>, +<a href="http://www.wikidata.org/entity/Q7769988">Q7769988</a>, +<a href="http://www.wikidata.org/entity/Q2946945">Q2946945</a>, +<a href="http://www.wikidata.org/entity/Q3212086">Q3212086</a>, +<a href="http://www.wikidata.org/entity/Q3212086">Q3212086</a>, +<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>, +<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>, +<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>, +<a href="http://www.wikidata.org/entity/Q6909175">Q6909175</a>, +<a href="http://www.wikidata.org/entity/Q7405709">Q7405709</a>, +<a href="http://www.wikidata.org/entity/Q7416149">Q7416149</a>, +<a href="http://www.wikidata.org/entity/Q7239952">Q7239952</a>, +<a href="http://www.wikidata.org/entity/Q7317332">Q7317332</a>, +<a href="http://www.wikidata.org/entity/Q7783674">Q7783674</a>, +<a href="http://www.wikidata.org/entity/Q7783704">Q7783704</a>, +<a href="http://www.wikidata.org/entity/Q7857590">Q7857590</a>, +<a href="http://www.wikidata.org/entity/Q3372526">Q3372526</a>, +<a href="http://www.wikidata.org/entity/Q3372642">Q3372642</a>, +<a href="http://www.wikidata.org/entity/Q3372816">Q3372816</a>, +<a href="http://www.wikidata.org/entity/Q3372909">Q3372909</a>, +<a href="http://www.wikidata.org/entity/Q7959649">Q7959649</a>, +<a href="http://www.wikidata.org/entity/Q7977485">Q7977485</a>, +<a href="http://www.wikidata.org/entity/Q7992684">Q7992684</a>, +<a href="http://www.wikidata.org/entity/Q3817966">Q3817966</a>, +<a href="http://www.wikidata.org/entity/Q3821852">Q3821852</a>, +<a href="http://www.wikidata.org/entity/Q3420907">Q3420907</a>, +<a href="http://www.wikidata.org/entity/Q3429733">Q3429733</a>, +<a href="http://www.wikidata.org/entity/Q774474">Q774474</a></p> + + + + + A one-way wall on the border? + http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html + http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html + Sat, 14 Oct 2017 22:10:00 +0200 + <p>I find it fascinating how many of the people being locked inside +the proposed border wall between USA and Mexico support the idea. The +proposal to keep Mexicans out reminds me of +<a href="http://www.history.com/news/10-things-you-may-not-know-about-the-berlin-wall">the +propaganda twist from the East Germany government</a> calling the wall +the “Antifascist Bulwark” after erecting the Berlin Wall, claiming +that the wall was erected to keep enemies from creeping into East +Germany, while it was obvious to the people locked inside it that it +was erected to keep the people from escaping.</p> + +<p>Do the people in USA supporting this wall really believe it is a +one way wall, only keeping people on the outside from getting in, +while not keeping people in the inside from getting out?</p> + + + + + Generating 3D prints in Debian using Cura and Slic3r(-prusa) + http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html + http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html + Mon, 9 Oct 2017 10:50:00 +0200 + <p>At my nearby maker space, +<a href="http://sonen.ifi.uio.no/">Sonen</a>, I heard the story that it +was easier to generate gcode files for theyr 3D printers (Ultimake 2+) +on Windows and MacOS X than Linux, because the software involved had +to be manually compiled and set up on Linux while premade packages +worked out of the box on Windows and MacOS X. I found this annoying, +as the software involved, +<a href="https://github.com/Ultimaker/Cura">Cura</a>, is free software +and should be trivial to get up and running on Linux if someone took +the time to package it for the relevant distributions. I even found +<a href="https://bugs.debian.org/706656">a request for adding into +Debian</a> from 2013, which had seem some activity over the years but +never resulted in the software showing up in Debian. So a few days +ago I offered my help to try to improve the situation.</p> + +<p>Now I am very happy to see that all the packages required by a +working Cura in Debian are uploaded into Debian and waiting in the NEW +queue for the ftpmasters to have a look. You can track the progress +on +<a href="https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org">the +status page for the 3D printer team</a>.</p> + +<p>The uploaded packages are a bit behind upstream, and was uploaded +now to get slots in <a href="https://ftp-master.debian.org/new.html">the NEW +queue</a> while we work up updating the packages to the latest +upstream version.</p> + +<p>On a related note, two competitors for Cura, which I found harder +to use and was unable to configure correctly for Ultimaker 2+ in the +short time I spent on it, are already in Debian. If you are looking +for 3D printer "slicers" and want something already available in +Debian, check out +<a href="https://tracker.debian.org/pkg/slic3r">slic3r</a> and +<a href="https://tracker.debian.org/pkg/slic3r-prusa">slic3r-prusa</a>. +The latter is a fork of the former.</p> + + + + + Mangler du en skrue, eller har du en skrue løs? + http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html + http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html + Wed, 4 Oct 2017 09:40:00 +0200 + Når jeg holder på med ulike prosjekter, så trenger jeg stadig ulike +skruer. Det siste prosjektet jeg holder på med er å lage +<a href="https://www.thingiverse.com/thing:676916">en boks til en +HDMI-touch-skjerm</a> som skal brukes med Raspberry Pi. Boksen settes +sammen med skruer og bolter, og jeg har vært i tvil om hvor jeg kan +få tak i de riktige skruene. Clas Ohlson og Jernia i nærheten har +sjelden hatt det jeg trenger. Men her om dagen fikk jeg et fantastisk +tips for oss som bor i Oslo. +<a href="http://www.zachskruer.no/">Zachariassen Jernvare AS</a> i +<a href="http://www.openstreetmap.org/?mlat=59.93421&mlon=10.76795#map=19/59.93421/10.76795">Hegermannsgate +23A på Torshov</a> har et fantastisk utvalg, og åpent mellom 09:00 og +17:00. De selger skruer, muttere, bolter, skiver etc i løs vekt, og +så langt har jeg fått alt jeg har lett etter. De har i tillegg det +meste av annen jernvare, som verktøy, lamper, ledninger, etc. Jeg +håper de har nok kunder til å holde det gående lenge, da dette er en +butikk jeg kommer til å besøke ofte. Butikken er et funn å ha i +nabolaget for oss som liker å bygge litt selv. :)</p> + + + + + Visualizing GSM radio chatter using gr-gsm and Hopglass + http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html + http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html + Fri, 29 Sep 2017 10:30:00 +0200 + <p>Every mobile phone announce its existence over radio to the nearby +mobile cell towers. And this radio chatter is available for anyone +with a radio receiver capable of receiving them. Details about the +mobile phones with very good accuracy is of course collected by the +phone companies, but this is not the topic of this blog post. The +mobile phone radio chatter make it possible to figure out when a cell +phone is nearby, as it include the SIM card ID (IMSI). By paying +attention over time, one can see when a phone arrive and when it leave +an area. I believe it would be nice to make this information more +available to the general public, to make more people aware of how +their phones are announcing their whereabouts to anyone that care to +listen.</p> + +<p>I am very happy to report that we managed to get something +visualizing this information up and running for +<a href="http://norwaymakers.org/osf17">Oslo Skaperfestival 2017</a> +(Oslo Makers Festival) taking place today and tomorrow at Deichmanske +library. The solution is based on the +<a href="http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html">simple +recipe for listening to GSM chatter</a> I posted a few days ago, and +will show up at the stand of <a href="http://sonen.ifi.uio.no/">Åpen +Sone from the Computer Science department of the University of +Oslo</a>. The presentation will show the nearby mobile phones (aka +IMSIs) as dots in a web browser graph, with lines to the dot +representing mobile base station it is talking to. It was working in +the lab yesterday, and was moved into place this morning.</p> + +<p>We set up a fairly powerful desktop machine using Debian +Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers +connected and visualize the visible cell phone towers using an +<a href="https://github.com/marlow925/hopglass">English version of +Hopglass</a>. A fairly powerfull machine is needed as the +grgsm_livemon_headless processes from +<a href="https://tracker.debian.org/pkg/gr-gsm">gr-gsm</a> converting +the radio signal to data packages is quite CPU intensive.</p> + +<p>The frequencies to listen to, are identified using a slightly +patched scan-and-livemon (to set the --args values for each receiver), +and the Hopglass data is generated using the +<a href="https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output">patches +in my meshviewer-output branch</a>. For some reason we could not get +more than four SDRs working. There is also a geographical map trying +to show the location of the base stations, but I believe their +coordinates are hardcoded to some random location in Germany, I +believe. The code should be replaced with code to look up location in +a text file, a sqlite database or one of the online databases +mentioned in +<a href="https://github.com/Oros42/IMSI-catcher/issues/14">the github +issue for the topic</a>. + +<p>If this sound interesting, visit the stand at the festival!</p> + + + Easier recipe to observe the cell phones around you http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html @@ -53,7 +603,7 @@ clone of two python scripts:</p> <p>Note, due to a bug somewhere the scan-and-livemon program (actually <a href="https://github.com/ptrkrysik/gr-gsm/issues/336">its underlying -program grgsm_scanner</a>) do not work with the HackRF radio. It do +program grgsm_scanner</a>) do not work with the HackRF radio. It does work with RTL 8232 and other similar USB radio receivers you can get very cheaply (<a href="https://www.ebay.com/sch/items/?_nkw=rtl+2832">for example @@ -224,409 +774,5 @@ one frequency?</p> - - Norwegian Bokmål edition of Debian Administrator's Handbook is now available - http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html - http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html - Tue, 25 Jul 2017 21:10:00 +0200 - <p align="center"><img align="center" src="http://people.skolelinux.org/pere/blog/images/2017-07-25-debian-handbook-nb-testprint.png"/></p> - -<p>I finally received a copy of the Norwegian Bokmål edition of -"<a href="https://debian-handbook.info/">The Debian Administrator's -Handbook</a>". This test copy arrived in the mail a few days ago, and -I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition -<a href="https://debian-handbook.info/get/#norwegian">is available -from lulu.com</a>. If you buy it quickly, you save 25% on the list -price. The book is also available for download in electronic form as -PDF, EPUB and Mobipocket, as can be -<a href="https://debian-handbook.info/browse/nb-NO/stable/">read online -as a web page</a>.</p> - -<p>This is the second book I publish (the first was the book -"<a href="http://free-culture.cc/">Free Culture</a>" by Lawrence Lessig -in -<a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">English</a>, -<a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">French</a> -and -<a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Norwegian -Bokmål</a>), and I am very excited to finally wrap up this -project. I hope -"<a href="http://www.lulu.com/shop/rapha%C3%ABl-hertzog-and-roland-mas/h%C3%A5ndbok-for-debian-administratoren/paperback/product-23262290.html">Håndbok -for Debian-administratoren</a>" will be well received.</p> - - - - - «Rapporten ser ikke på informasjonssikkerhet knyttet til personlig integritet» - http://people.skolelinux.org/pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html - http://people.skolelinux.org/pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html - Tue, 27 Jun 2017 17:50:00 +0200 - <p>Jeg kom over teksten -«<a href="https://freedom-to-tinker.com/2017/06/21/killing-car-privacy-by-federal-mandate/">Killing -car privacy by federal mandate</a>» av Leonid Reyzin på Freedom to -Tinker i dag, og det gleder meg å se en god gjennomgang om hvorfor det -er et urimelig inngrep i privatsfæren å la alle biler kringkaste sin -posisjon og bevegelse via radio. Det omtalte forslaget basert på -Dedicated Short Range Communication (DSRC) kalles Basic Safety Message -(BSM) i USA og Cooperative Awareness Message (CAM) i Europa, og det -norske Vegvesenet er en av de som ser ut til å kunne tenke seg å -pålegge alle biler å fjerne nok en bit av innbyggernes privatsfære. -Anbefaler alle å lese det som står der. - -<p>Mens jeg tittet litt på DSRC på biler i Norge kom jeg over et sitat -jeg synes er illustrativt for hvordan det offentlige Norge håndterer -problemstillinger rundt innbyggernes privatsfære i SINTEF-rapporten -«<a href="https://www.sintef.no/publikasjoner/publikasjon/Download/?pubid=SINTEF+A23933">Informasjonssikkerhet -i AutoPASS-brikker</a>» av Trond Foss:</p> - -<p><blockquote> -«Rapporten ser ikke på informasjonssikkerhet knyttet til personlig - integritet.» -</blockquote></p> - -<p>Så enkelt kan det tydeligvis gjøres når en vurderer -informasjonssikkerheten. Det holder vel at folkene på toppen kan si -at «Personvernet er ivaretatt», som jo er den populære intetsigende -frasen som gjør at mange tror enkeltindividers integritet tas vare på. -Sitatet fikk meg til å undres på hvor ofte samme tilnærming, å bare se -bort fra behovet for personlig itegritet, blir valgt når en velger å -legge til rette for nok et inngrep i privatsfæren til personer i -Norge. Det er jo sjelden det får reaksjoner. Historien om -reaksjonene på Helse Sør-Østs tjenesteutsetting er jo sørgelig nok et -unntak og toppen av isfjellet, desverre. Tror jeg fortsatt takker nei -til både AutoPASS og holder meg så langt unna det norske helsevesenet -som jeg kan, inntil de har demonstrert og dokumentert at de verdsetter -individets privatsfære og personlige integritet høyere enn kortsiktig -gevist og samfunnsnytte.</p> - - - - - Updated sales number for my Free Culture paper editions - http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html - http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html - Mon, 12 Jun 2017 11:40:00 +0200 - <p>It is pleasing to see that the work we put down in publishing new -editions of the classic <a href="http://www.free-culture.cc/">Free -Culture book</a> by the founder of the Creative Commons movement, -Lawrence Lessig, is still being appreciated. I had a look at the -latest sales numbers for the paper edition today. Not too impressive, -but happy to see some buyers still exist. All the revenue from the -books is sent to the <a href="https://creativecommons.org/">Creative -Commons Corporation</a>, and they receive the largest cut if you buy -directly from Lulu. Most books are sold via Amazon, with Ingram -second and only a small fraction directly from Lulu. The ebook -edition is available for free from -<a href="https://github.com/petterreinholdtsen/free-culture-lessig">Github</a>.</p> - -<table border="0"> -<tr><th rowspan="2" valign="bottom">Title / language</th><th colspan="3">Quantity</th></tr> -<tr><th>2016 jan-jun</th><th>2016 jul-dec</th><th>2017 jan-may</th></tr> - -<tr> - <td><a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">Culture Libre / French</a></td> - <td align="right">3</td> - <td align="right">6</td> - <td align="right">15</td> -</tr> - -<tr> - <td><a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Fri kultur / Norwegian</a></td> - <td align="right">7</td> - <td align="right">1</td> - <td align="right">0</td> -</tr> - -<tr> - <td><a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">Free Culture / English</a></td> - <td align="right">14</td> - <td align="right">27</td> - <td align="right">16</td> -</tr> - -<tr> - <td>Total</td> - <td align="right">24</td> - <td align="right">34</td> - <td align="right">31</td> -</tr> - -</table> - -<p>A bit sad to see the low sales number on the Norwegian edition, and -a bit surprising the English edition still selling so well.</p> - -<p>If you would like to translate and publish the book in your native -language, I would be happy to help make it happen. Please get in -touch.</p> - - - - - Release 0.1.1 of free software archive system Nikita announced - http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html - http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html - Sat, 10 Jun 2017 00:40:00 +0200 - <p>I am very happy to report that the -<a href="https://github.com/hiOA-ABI/nikita-noark5-core">Nikita Noark 5 -core project</a> tagged its second release today. The free software -solution is an implementation of the Norwegian archive standard Noark -5 used by government offices in Norway. These were the changes in -version 0.1.1 since version 0.1.0 (from NEWS.md): - -<ul> - - <li>Continued work on the angularjs GUI, including document upload.</li> - <li>Implemented correspondencepartPerson, correspondencepartUnit and - correspondencepartInternal</li> - <li>Applied for coverity coverage and started submitting code on - regualr basis.</li> - <li>Started fixing bugs reported by coverity</li> - <li>Corrected and completed HATEOAS links to make sure entire API is - available via URLs in _links.</li> - <li>Corrected all relation URLs to use trailing slash.</li> - <li>Add initial support for storing data in ElasticSearch.</li> - <li>Now able to receive and store uploaded files in the archive.</li> - <li>Changed JSON output for object lists to have relations in _links.</li> - <li>Improve JSON output for empty object lists.</li> - <li>Now uses correct MIME type application/vnd.noark5-v4+json.</li> - <li>Added support for docker container images.</li> - <li>Added simple API browser implemented in JavaScript/Angular.</li> - <li>Started on archive client implemented in JavaScript/Angular.</li> - <li>Started on prototype to show the public mail journal.</li> - <li>Improved performance by disabling Sprint FileWatcher.</li> - <li>Added support for 'arkivskaper', 'saksmappe' and 'journalpost'.</li> - <li>Added support for some metadata codelists.</li> - <li>Added support for Cross-origin resource sharing (CORS).</li> - <li>Changed login method from Basic Auth to JSON Web Token (RFC 7519) - style.</li> - <li>Added support for GET-ing ny-* URLs.</li> - <li>Added support for modifying entities using PUT and eTag.</li> - <li>Added support for returning XML output on request.</li> - <li>Removed support for English field and class names, limiting ourself - to the official names.</li> - <li>...</li> - -</ul> - -<p>If this sound interesting to you, please contact us on IRC (#nikita -on irc.freenode.net) or email -(<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark -mailing list).</p> - - - - - Idea for storing trusted timestamps in a Noark 5 archive - http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html - http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html - Wed, 7 Jun 2017 21:40:00 +0200 - <p><em>This is a copy of -<a href="https://lists.nuug.no/pipermail/nikita-noark/2017-June/000297.html">an -email I posted to the nikita-noark mailing list</a>. Please follow up -there if you would like to discuss this topic. The background is that -we are making a free software archive system based on the Norwegian -<a href="https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden">Noark -5 standard</a> for government archives.</em></p> - -<p>I've been wondering a bit lately how trusted timestamps could be -stored in Noark 5. -<a href="https://en.wikipedia.org/wiki/Trusted_timestamping">Trusted -timestamps</a> can be used to verify that some information -(document/file/checksum/metadata) have not been changed since a -specific time in the past. This is useful to verify the integrity of -the documents in the archive.</p> - -<p>Then it occured to me, perhaps the trusted timestamps could be -stored as dokument variants (ie dokumentobjekt referered to from -dokumentbeskrivelse) with the filename set to the hash it is -stamping?</p> - -<p>Given a "dokumentbeskrivelse" with an associated "dokumentobjekt", -a new dokumentobjekt is associated with "dokumentbeskrivelse" with the -same attributes as the stamped dokumentobjekt except these -attributes:</p> - -<ul> - -<li>format -> "RFC3161" -<li>mimeType -> "application/timestamp-reply" -<li>formatDetaljer -> "&lt;source URL for timestamp service&gt;" -<li>filenavn -> "&lt;sjekksum&gt;.tsr" - -</ul> - -<p>This assume a service following -<a href="https://tools.ietf.org/html/rfc3161">IETF RFC 3161</a> is -used, which specifiy the given MIME type for replies and the .tsr file -ending for the content of such trusted timestamp. As far as I can -tell from the Noark 5 specifications, it is OK to have several -variants/renderings of a dokument attached to a given -dokumentbeskrivelse objekt. It might be stretching it a bit to make -some of these variants represent crypto-signatures useful for -verifying the document integrity instead of representing the dokument -itself.</p> - -<p>Using the source of the service in formatDetaljer allow several -timestamping services to be used. This is useful to spread the risk -of key compromise over several organisations. It would only be a -problem to trust the timestamps if all of the organisations are -compromised.</p> - -<p>The following oneliner on Linux can be used to generate the tsr -file. $input is the path to the file to checksum, and $sha256 is the -SHA-256 checksum of the file (ie the "<sjekksum>.tsr" value mentioned -above).</p> - -<p><blockquote><pre> -openssl ts -query -data "$inputfile" -cert -sha256 -no_nonce \ - | curl -s -H "Content-Type: application/timestamp-query" \ - --data-binary "@-" http://zeitstempel.dfn.de > $sha256.tsr -</pre></blockquote></p> - -<p>To verify the timestamp, you first need to download the public key -of the trusted timestamp service, for example using this command:</p> - -<p><blockquote><pre> -wget -O ca-cert.txt \ - https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt -</pre></blockquote></p> - -<p>Note, the public key should be stored alongside the timestamps in -the archive to make sure it is also available 100 years from now. It -is probably a good idea to standardise how and were to store such -public keys, to make it easier to find for those trying to verify -documents 100 or 1000 years from now. :)</p> - -<p>The verification itself is a simple openssl command:</p> - -<p><blockquote><pre> -openssl ts -verify -data $inputfile -in $sha256.tsr \ - -CAfile ca-cert.txt -text -</pre></blockquote></p> - -<p>Is there any reason this approach would not work? Is it somehow against -the Noark 5 specification?</p> - - - - - Når nynorskoversettelsen svikter til eksamen... - http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html - http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html - Sat, 3 Jun 2017 08:20:00 +0200 - <p><a href="http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-622459b.html">Aftenposten -melder i dag</a> om feil i eksamensoppgavene for eksamen i politikk og -menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var -like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring -på om den fri oversetterløsningen -<a href="https://www.apertium.org/">Apertium</a> ville gjort en bedre -jobb enn Utdanningsdirektoratet. Det kan se slik ut.</p> - -<p>Her er bokmålsoppgaven fra eksamenen:</p> - -<blockquote> -<p>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers -rolle og muligheter til å håndtere internasjonale utfordringer, som -for eksempel flykningekrisen.</p> - -<p>Vedlegge er eksempler på tekster som kan gi relevante perspektiver -på temaet:</p> -<ol> -<li>Flykningeregnskapet 2016, UNHCR og IDMC -<li>«Grenseløst Europa for fall» A-Magasinet, 26. november 2015 -</ol> - -</blockquote> - -<p>Dette oversetter Apertium slik:</p> - -<blockquote> -<p>Drøft utfordringane knytte til nasjonalstatane sine og rolla til -andre aktørar og høve til å handtera internasjonale utfordringar, som -til dømes *flykningekrisen.</p> - -<p>Vedleggja er døme på tekster som kan gje relevante perspektiv på -temaet:</p> - -<ol> -<li>*Flykningeregnskapet 2016, *UNHCR og *IDMC</li> -<li>«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015</li> -</ol> - -</blockquote> - -<p>Ord som ikke ble forstått er markert med stjerne (*), og trenger -ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i -oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at -"andre aktørers rolle og muligheter til ..." burde vært oversatt til -"rolla til andre aktørar og deira høve til ..." eller noe slikt, men -det er kanskje flisespikking. Det understreker vel bare at det alltid -trengs korrekturlesning etter automatisk oversettelse.</p> - - - - - Epost inn som arkivformat i Riksarkivarens forskrift? - http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html - http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html - Thu, 27 Apr 2017 11:30:00 +0200 - <p>I disse dager, med frist 1. mai, har Riksarkivaren ute en høring på -sin forskrift. Som en kan se er det ikke mye tid igjen før fristen -som går ut på søndag. Denne forskriften er det som lister opp hvilke -formater det er greit å arkivere i -<a href="http://www.arkivverket.no/arkivverket/Offentleg-forvalting/Noark/Noark-5">Noark -5-løsninger</a> i Norge.</p> - -<p>Jeg fant høringsdokumentene hos -<a href="https://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing">Norsk -Arkivråd</a> etter å ha blitt tipset på epostlisten til -<a href="https://github.com/hiOA-ABI/nikita-noark5-core">fri -programvareprosjektet Nikita Noark5-Core</a>, som lager et Noark 5 -Tjenestegresesnitt. Jeg er involvert i Nikita-prosjektet og takket -være min interesse for tjenestegrensesnittsprosjektet har jeg lest en -god del Noark 5-relaterte dokumenter, og til min overraskelse oppdaget -at standard epost ikke er på listen over godkjente formater som kan -arkiveres. Høringen med frist søndag er en glimrende mulighet til å -forsøke å gjøre noe med det. Jeg holder på med -<a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/hoering-arkivforskrift.tex">egen -høringsuttalelse</a>, og lurer på om andre er interessert i å støtte -forslaget om å tillate arkivering av epost som epost i arkivet.</p> - -<p>Er du igang med å skrive egen høringsuttalelse allerede? I så fall -kan du jo vurdere å ta med en formulering om epost-lagring. Jeg tror -ikke det trengs så mye. Her et kort forslag til tekst:</p> - -<p><blockquote> - - <p>Viser til høring sendt ut 2017-02-17 (Riksarkivarens referanse - 2016/9840 HELHJO), og tillater oss å sende inn noen innspill om - revisjon av Forskrift om utfyllende tekniske og arkivfaglige - bestemmelser om behandling av offentlige arkiver (Riksarkivarens - forskrift).</p> - - <p>Svært mye av vår kommuikasjon foregår i dag på e-post.  Vi - foreslår derfor at Internett-e-post, slik det er beskrevet i IETF - RFC 5322, - <a href="https://tools.ietf.org/html/rfc5322">https://tools.ietf.org/html/rfc5322</a>. bør - inn som godkjent dokumentformat.  Vi foreslår at forskriftens - oversikt over godkjente dokumentformater ved innlevering i § 5-16 - endres til å ta med Internett-e-post.</p> - -</blockquote></p> - -<p>Som del av arbeidet med tjenestegrensesnitt har vi testet hvordan -epost kan lagres i en Noark 5-struktur, og holder på å skrive et -forslag om hvordan dette kan gjøres som vil bli sendt over til -arkivverket så snart det er ferdig. De som er interesserte kan -<a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/epostlagring.md">følge -fremdriften på web</a>.</p> - -<p>Oppdatering 2017-04-28: I dag ble høringuttalelsen jeg skrev - <a href="https://www.nuug.no/news/NUUGs_h_ringuttalelse_til_Riksarkivarens_forskrift.shtml">sendt - inn av foreningen NUUG</a>.</p> - - -