1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/' xmlns:
atom=
"http://www.w3.org/2005/Atom">
4 <title>Petter Reinholdtsen
</title>
5 <description></description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
7 <atom:link href=
"http://people.skolelinux.org/pere/blog/index.rss" rel=
"self" type=
"application/rss+xml" />
10 <title>Metadata proposal for movies on the Internet Archive
</title>
11 <link>http://people.skolelinux.org/pere/blog/Metadata_proposal_for_movies_on_the_Internet_Archive.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Metadata_proposal_for_movies_on_the_Internet_Archive.html
</guid>
13 <pubDate>Tue,
28 Nov
2017 12:
00:
00 +
0100</pubDate>
14 <description><p
>It would be easier to locate the movie you want to watch in
15 <a href=
"https://www.archive.org/
">the Internet Archive
</a
>, if the
16 metadata about each movie was more complete and accurate. In the
17 archiving community, a well known saying state that good metadata is a
18 love letter to the future. The metadata in the Internet Archive could
19 use a face lift for the future to love us back. Here is a proposal
20 for a small improvement that would make the metadata more useful
21 today. I
've been unable to find any document describing the various
22 standard fields available when uploading videos to the archive, so
23 this proposal is based on my best quess and searching through several
24 of the existing movies.
</p
>
26 <p
>I have a few use cases in mind. First of all, I would like to be
27 able to count the number of distinct movies in the Internet Archive,
28 without duplicates. I would further like to identify the IMDB title
29 ID of the movies in the Internet Archive, to be able to look up a IMDB
30 title ID and know if I can fetch the video from there and share it
31 with my friends.
</p
>
33 <p
>Second, I would like the Butter data provider for The Internet
35 (
<a href=
"https://github.com/butterproviders/butter-provider-archive
">available
36 from github
</a
>), to list as many of the good movies as possible. The
37 plugin currently do a search in the archive with the following
41 collection:moviesandfilms
42 AND NOT collection:movie_trailers
43 AND -mediatype:collection
44 AND format:
"Archive BitTorrent
"
46 </pre
></p
>
48 <p
>Most of the cool movies that fail to show up in Butter do so
49 because the
'year
' field is missing. The
'year
' field is populated by
50 the year part from the
'date
' field, and should be when the movie was
51 released (date or year). Two such examples are
52 <a href=
"https://archive.org/details/SidneyOlcottsBen-hur1905
">Ben Hur
53 from
1905</a
> and
54 <a href=
"https://archive.org/details/Caminandes2GranDillama
">Caminandes
55 2: Gran Dillama from
2013</a
>, where the year metadata field is
58 So, my proposal is simply, for every movie in The Internet Archive
59 where an IMDB title ID exist, please fill in these metadata fields
60 (note, they can be updated also long after the video was uploaded, but
61 as far as I can tell, only by the uploader):
65 <dt
>mediatype
</dt
>
66 <dd
>Should be
'movie
' for movies.
</dd
>
68 <dt
>collection
</dt
>
69 <dd
>Should contain
'moviesandfilms
'.
</dd
>
71 <dt
>title
</dt
>
72 <dd
>The title of the movie, without the publication year.
</dd
>
74 <dt
>date
</dt
>
75 <dd
>The data or year the movie was released. This make the movie show
76 up in Butter, as well as make it possible to know the age of the
77 movie and is useful to figure out copyright status.
</dd
>
79 <dt
>director
</dt
>
80 <dd
>The director of the movie. This make it easier to know if the
81 correct movie is found in movie databases.
</dd
>
83 <dt
>publisher
</dt
>
84 <dd
>The production company making the movie. Also useful for
85 identifying the correct movie.
</dd
>
87 <dt
>links
</dt
>
89 <dd
>Add a link to the IMDB title page, for example like this:
&lt;a
90 href=
"http://www.imdb.com/title/tt0028496/
"&gt;Movie in
91 IMDB
&lt;/a
&gt;. This make it easier to find duplicates and allow for
92 counting of number of unique movies in the Archive. Other external
93 references, like to TMDB, could be added like this too.
</dd
>
97 <p
>I did consider proposing a Custom field for the IMDB title ID (for
98 example
'imdb_title_url
',
'imdb_code
' or simply
'imdb
', but suspect it
99 will be easier to simply place it in the links free text field.
</p
>
102 <a href=
"https://github.com/petterreinholdtsen/public-domain-free-imdb
">a
103 list of IMDB title IDs for several thousand movies in the Internet
104 Archive
</a
>, but I also got a list of several thousand movies without
105 such IMDB title ID (and quite a few duplicates). It would be great if
106 this data set could be integrated into the Internet Archive metadata
107 to be available for everyone in the future, but with the current
108 policy of leaving metadata editing to the uploaders, it will take a
109 while before this happen. If you have uploaded movies into the
110 Internet Archive, you can help. Please consider following my proposal
111 above for your movies, to ensure that movie is properly
112 counted. :)
</p
>
114 <p
>The list is mostly generated using wikidata, which based on
115 Wikipedia articles make it possible to link between IMDB and movies in
116 the Internet Archive. But there are lots of movies without a
117 Wikipedia article, and some movies where only a collection page exist
118 (like for
<a href=
"https://en.wikipedia.org/wiki/Caminandes
">the
119 Caminandes example above
</a
>, where there are three movies but only
120 one Wikidata entry).
</p
>
122 <p
>As usual, if you use Bitcoin and want to show your support of my
123 activities, please send Bitcoin donations to my address
124 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
129 <title>Legal to share more than
3000 movies listed on IMDB?
</title>
130 <link>http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_3000_movies_listed_on_IMDB_.html
</link>
131 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Legal_to_share_more_than_3000_movies_listed_on_IMDB_.html
</guid>
132 <pubDate>Sat,
18 Nov
2017 21:
20:
00 +
0100</pubDate>
133 <description><p
>A month ago, I blogged about my work to
134 <a href=
"http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html
">automatically
135 check the copyright status of IMDB entries
</a
>, and try to count the
136 number of movies listed in IMDB that is legal to distribute on the
137 Internet. I have continued to look for good data sources, and
138 identified a few more. The code used to extract information from
139 various data sources is available in
140 <a href=
"https://github.com/petterreinholdtsen/public-domain-free-imdb
">a
141 git repository
</a
>, currently available from github.
</p
>
143 <p
>So far I have identified
3186 unique IMDB title IDs. To gain
144 better understanding of the structure of the data set, I created a
145 histogram of the year associated with each movie (typically release
146 year). It is interesting to notice where the peaks and dips in the
147 graph are located. I wonder why they are placed there. I suspect
148 World War II caused the dip around
1940, but what caused the peak
149 around
2010?
</p
>
151 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2017-
11-
18-verk-i-det-fri-filmer.png
" /
></p
>
153 <p
>I
've so far identified ten sources for IMDB title IDs for movies in
154 the public domain or with a free license. This is the statistics
155 reported when running
'make stats
' in the git repository:
</p
>
158 249 entries (
6 unique) with and
288 without IMDB title ID in free-movies-archive-org-butter.json
159 2301 entries (
540 unique) with and
0 without IMDB title ID in free-movies-archive-org-wikidata.json
160 830 entries (
29 unique) with and
0 without IMDB title ID in free-movies-icheckmovies-archive-mochard.json
161 2109 entries (
377 unique) with and
0 without IMDB title ID in free-movies-imdb-pd.json
162 291 entries (
122 unique) with and
0 without IMDB title ID in free-movies-letterboxd-pd.json
163 144 entries (
135 unique) with and
0 without IMDB title ID in free-movies-manual.json
164 350 entries (
1 unique) with and
801 without IMDB title ID in free-movies-publicdomainmovies.json
165 4 entries (
0 unique) with and
124 without IMDB title ID in free-movies-publicdomainreview.json
166 698 entries (
119 unique) with and
118 without IMDB title ID in free-movies-publicdomaintorrents.json
167 8 entries (
8 unique) with and
196 without IMDB title ID in free-movies-vodo.json
168 3186 unique IMDB title IDs in total
171 <p
>The entries without IMDB title ID are candidates to increase the
172 data set, but might equally well be duplicates of entries already
173 listed with IMDB title ID in one of the other sources, or represent
174 movies that lack a IMDB title ID. I
've seen examples of all these
175 situations when peeking at the entries without IMDB title ID. Based
176 on these data sources, the lower bound for movies listed in IMDB that
177 are legal to distribute on the Internet is between
3186 and
4713.
179 <p
>It would be great for improving the accuracy of this measurement,
180 if the various sources added IMDB title ID to their metadata. I have
181 tried to reach the people behind the various sources to ask if they
182 are interested in doing this, without any replies so far. Perhaps you
183 can help me get in touch with the people behind VODO, Public Domain
184 Torrents, Public Domain Movies and Public Domain Review to try to
185 convince them to add more metadata to their movie entries?
</p
>
187 <p
>Another way you could help is by adding pages to Wikipedia about
188 movies that are legal to distribute on the Internet. If such page
189 exist and include a link to both IMDB and The Internet Archive, the
190 script used to generate free-movies-archive-org-wikidata.json should
191 pick up the mapping as soon as wikidata is updates.
</p
>
193 <p
>As usual, if you use Bitcoin and want to show your support of my
194 activities, please send Bitcoin donations to my address
195 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
200 <title>Some notes on fault tolerant storage systems
</title>
201 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html
</link>
202 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html
</guid>
203 <pubDate>Wed,
1 Nov
2017 15:
35:
00 +
0100</pubDate>
204 <description><p
>If you care about how fault tolerant your storage is, you might
205 find these articles and papers interesting. They have formed how I
206 think of when designing a storage system.
</p
>
210 <li
>USENIX :login;
<a
211 href=
"https://www.usenix.org/publications/login/summer2017/ganesan
">Redundancy
212 Does Not Imply Fault Tolerance. Analysis of Distributed Storage
213 Reactions to Single Errors and Corruptions
</a
> by Aishwarya Ganesan,
214 Ramnatthan Alagappan, Andrea C. Arpaci-Dusseau, and Remzi
215 H. Arpaci-Dusseau
</li
>
218 <a href=
"http://www.zdnet.com/article/why-raid-
5-stops-working-in-
2009/
">Why
219 RAID
5 stops working in
2009</a
> by Robin Harris
</li
>
222 <a href=
"http://www.zdnet.com/article/why-raid-
6-stops-working-in-
2019/
">Why
223 RAID
6 stops working in
2019</a
> by Robin Harris
</li
>
225 <li
>USENIX FAST
'07
226 <a href=
"http://research.google.com/archive/disk_failures.pdf
">Failure
227 Trends in a Large Disk Drive Population
</a
> by Eduardo Pinheiro,
228 Wolf-Dietrich Weber and Luiz André Barroso
</li
>
230 <li
>USENIX ;login:
<a
231 href=
"https://www.usenix.org/system/files/login/articles/hughes12-
04.pdf
">Data
232 Integrity. Finding Truth in a World of Guesses and Lies
</a
> by Doug
235 <li
>USENIX FAST
'08
236 <a href=
"https://www.usenix.org/events/fast08/tech/full_papers/bairavasundaram/bairavasundaram_html/
">An
237 Analysis of Data Corruption in the Storage Stack
</a
> by
238 L. N. Bairavasundaram, G. R. Goodson, B. Schroeder, A. C.
239 Arpaci-Dusseau, and R. H. Arpaci-Dusseau
</li
>
241 <li
>USENIX FAST
'07 <a
242 href=
"https://www.usenix.org/legacy/events/fast07/tech/schroeder/schroeder_html/
">Disk
243 failures in the real world: what does an MTTF of
1,
000,
000 hours mean
244 to you?
</a
> by B. Schroeder and G. A. Gibson.
</li
>
246 <li
>USENIX ;login:
<a
247 href=
"https://www.usenix.org/events/fast08/tech/full_papers/jiang/jiang_html/
">Are
248 Disks the Dominant Contributor for Storage Failures? A Comprehensive
249 Study of Storage Subsystem Failure Characteristics
</a
> by Weihang
250 Jiang, Chongfeng Hu, Yuanyuan Zhou, and Arkady Kanevsky
</li
>
252 <li
>SIGMETRICS
2007
253 <a href=
"http://research.cs.wisc.edu/adsl/Publications/latent-sigmetrics07.pdf
">An
254 analysis of latent sector errors in disk drives
</a
> by
255 L. N. Bairavasundaram, G. R. Goodson, S. Pasupathy, and J. Schindler
</li
>
259 <p
>Several of these research papers are based on data collected from
260 hundred thousands or millions of disk, and their findings are eye
261 opening. The short story is simply do not implicitly trust RAID or
262 redundant storage systems. Details matter. And unfortunately there
263 are few options on Linux addressing all the identified issues. Both
264 ZFS and Btrfs are doing a fairly good job, but have legal and
265 practical issues on their own. I wonder how cluster file systems like
266 Ceph do in this regard. After all, there is an old saying, you know
267 you have a distributed system when the crash of a computer you have
268 never heard of stops you from getting any work done. The same holds
269 true if fault tolerance do not work.
</p
>
271 <p
>Just remember, in the end, it do not matter how redundant, or how
272 fault tolerant your storage is, if you do not continuously monitor its
273 status to detect and replace failed disks.
</p
>
275 <p
>As usual, if you use Bitcoin and want to show your support of my
276 activities, please send Bitcoin donations to my address
277 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
282 <title>Web services for writing academic LaTeX papers as a team
</title>
283 <link>http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html
</link>
284 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html
</guid>
285 <pubDate>Tue,
31 Oct
2017 21:
00:
00 +
0100</pubDate>
286 <description><p
>I was surprised today to learn that a friend in academia did not
287 know there are easily available web services available for writing
288 LaTeX documents as a team. I thought it was common knowledge, but to
289 make sure at least my readers are aware of it, I would like to mention
290 these useful services for writing LaTeX documents. Some of them even
291 provide a WYSIWYG editor to ease writing even further.
</p
>
293 <p
>There are two commercial services available,
294 <a href=
"https://sharelatex.com
">ShareLaTeX
</a
> and
295 <a href=
"https://overleaf.com
">Overleaf
</a
>. They are very easy to
296 use. Just start a new document, select which publisher to write for
297 (ie which LaTeX style to use), and start writing. Note, these two
298 have announced their intention to join forces, so soon it will only be
299 one joint service. I
've used both for different documents, and they
300 work just fine. While
301 <a href=
"https://github.com/sharelatex/sharelatex
">ShareLaTeX is free
302 software
</a
>, while the latter is not. According to
<a
303 href=
"https://www.overleaf.com/help/
17-is-overleaf-open-source
">a
304 announcement from Overleaf
</a
>, they plan to keep the ShareLaTeX code
305 base maintained as free software.
</p
>
307 But these two are not the only alternatives.
308 <a href=
"https://app.fiduswriter.org/
">Fidus Writer
</a
> is another free
309 software solution with
<a href=
"https://github.com/fiduswriter
">the
310 source available on github
</a
>. I have not used it myself. Several
311 others can be found on the nice
312 <a href=
"https://alternativeto.net/software/sharelatex/
">alterntiveTo
313 web service
</a
>.
315 <p
>If you like Google Docs or Etherpad, but would like to write
316 documents in LaTeX, you should check out these services. You can even
317 host your own, if you want to. :)
</p
>
319 <p
>As usual, if you use Bitcoin and want to show your support of my
320 activities, please send Bitcoin donations to my address
321 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
326 <title>Locating IMDB IDs of movies in the Internet Archive using Wikidata
</title>
327 <link>http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html
</link>
328 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html
</guid>
329 <pubDate>Wed,
25 Oct
2017 12:
20:
00 +
0200</pubDate>
330 <description><p
>Recently, I needed to automatically check the copyright status of a
331 set of
<a href=
"http://www.imdb.com/
">The Internet Movie database
332 (IMDB)
</a
> entries, to figure out which one of the movies they refer
333 to can be freely distributed on the Internet. This proved to be
334 harder than it sounds. IMDB for sure list movies without any
335 copyright protection, where the copyright protection has expired or
336 where the movie is lisenced using a permissive license like one from
337 Creative Commons. These are mixed with copyright protected movies,
338 and there seem to be no way to separate these classes of movies using
339 the information in IMDB.
</p
>
341 <p
>First I tried to look up entries manually in IMDB,
342 <a href=
"https://www.wikipedia.org/
">Wikipedia
</a
> and
343 <a href=
"https://www.archive.org/
">The Internet Archive
</a
>, to get a
344 feel how to do this. It is hard to know for sure using these sources,
345 but it should be possible to be reasonable confident a movie is
"out
346 of copyright
" with a few hours work per movie. As I needed to check
347 almost
20,
000 entries, this approach was not sustainable. I simply
348 can not work around the clock for about
6 years to check this data
351 <p
>I asked the people behind The Internet Archive if they could
352 introduce a new metadata field in their metadata XML for IMDB ID, but
353 was told that they leave it completely to the uploaders to update the
354 metadata. Some of the metadata entries had IMDB links in the
355 description, but I found no way to download all metadata files in bulk
356 to locate those ones and put that approach aside.
</p
>
358 <p
>In the process I noticed several Wikipedia articles about movies
359 had links to both IMDB and The Internet Archive, and it occured to me
360 that I could use the Wikipedia RDF data set to locate entries with
361 both, to at least get a lower bound on the number of movies on The
362 Internet Archive with a IMDB ID. This is useful based on the
363 assumption that movies distributed by The Internet Archive can be
364 legally distributed on the Internet. With some help from the RDF
365 community (thank you DanC), I was able to come up with this query to
366 pass to
<a href=
"https://query.wikidata.org/
">the SPARQL interface on
370 SELECT ?work ?imdb ?ia ?when ?label
373 ?work wdt:P31/wdt:P279* wd:Q11424.
374 ?work wdt:P345 ?imdb.
377 ?work wdt:P577 ?when.
378 ?work rdfs:label ?label.
379 FILTER(LANG(?label) =
"en
").
382 </pre
></p
>
384 <p
>If I understand the query right, for every film entry anywhere in
385 Wikpedia, it will return the IMDB ID and The Internet Archive ID, and
386 when the movie was released and its English title, if either or both
387 of the latter two are available. At the moment the result set contain
388 2338 entries. Of course, it depend on volunteers including both
389 correct IMDB and The Internet Archive IDs in the wikipedia articles
390 for the movie. It should be noted that the result will include
391 duplicates if the movie have entries in several languages. There are
392 some bogus entries, either because The Internet Archive ID contain a
393 typo or because the movie is not available from The Internet Archive.
394 I did not verify the IMDB IDs, as I am unsure how to do that
395 automatically.
</p
>
397 <p
>I wrote a small python script to extract the data set from Wikidata
398 and check if the XML metadata for the movie is available from The
399 Internet Archive, and after around
1.5 hour it produced a list of
2097
400 free movies and their IMDB ID. In total,
171 entries in Wikidata lack
401 the refered Internet Archive entry. I assume the
70 "disappearing
"
402 entries (ie
2338-
2097-
171) are duplicate entries.
</p
>
404 <p
>This is not too bad, given that The Internet Archive report to
405 contain
<a href=
"https://archive.org/details/feature_films
">5331
406 feature films
</a
> at the moment, but it also mean more than
3000
407 movies are missing on Wikipedia or are missing the pair of references
408 on Wikipedia.
</p
>
410 <p
>I was curious about the distribution by release year, and made a
411 little graph to show how the amount of free movies is spread over the
414 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2017-
10-
25-verk-i-det-fri-filmer.png
"></p
>
416 <p
>I expect the relative distribution of the remaining
3000 movies to
417 be similar.
</p
>
419 <p
>If you want to help, and want to ensure Wikipedia can be used to
420 cross reference The Internet Archive and The Internet Movie Database,
421 please make sure entries like this are listed under the
"External
422 links
" heading on the Wikipedia article for the movie:
</p
>
425 * {{Internet Archive film|id=FightingLady}}
426 * {{IMDb title|id=
0036823|title=The Fighting Lady}}
427 </pre
></p
>
429 <p
>Please verify the links on the final page, to make sure you did not
430 introduce a typo.
</p
>
432 <p
>Here is the complete list, if you want to correct the
171
433 identified Wikipedia entries with broken links to The Internet
434 Archive:
<a href=
"http://www.wikidata.org/entity/Q1140317
">Q1140317
</a
>,
435 <a href=
"http://www.wikidata.org/entity/Q458656
">Q458656
</a
>,
436 <a href=
"http://www.wikidata.org/entity/Q458656
">Q458656
</a
>,
437 <a href=
"http://www.wikidata.org/entity/Q470560
">Q470560
</a
>,
438 <a href=
"http://www.wikidata.org/entity/Q743340
">Q743340
</a
>,
439 <a href=
"http://www.wikidata.org/entity/Q822580
">Q822580
</a
>,
440 <a href=
"http://www.wikidata.org/entity/Q480696
">Q480696
</a
>,
441 <a href=
"http://www.wikidata.org/entity/Q128761
">Q128761
</a
>,
442 <a href=
"http://www.wikidata.org/entity/Q1307059
">Q1307059
</a
>,
443 <a href=
"http://www.wikidata.org/entity/Q1335091
">Q1335091
</a
>,
444 <a href=
"http://www.wikidata.org/entity/Q1537166
">Q1537166
</a
>,
445 <a href=
"http://www.wikidata.org/entity/Q1438334
">Q1438334
</a
>,
446 <a href=
"http://www.wikidata.org/entity/Q1479751
">Q1479751
</a
>,
447 <a href=
"http://www.wikidata.org/entity/Q1497200
">Q1497200
</a
>,
448 <a href=
"http://www.wikidata.org/entity/Q1498122
">Q1498122
</a
>,
449 <a href=
"http://www.wikidata.org/entity/Q865973
">Q865973
</a
>,
450 <a href=
"http://www.wikidata.org/entity/Q834269
">Q834269
</a
>,
451 <a href=
"http://www.wikidata.org/entity/Q841781
">Q841781
</a
>,
452 <a href=
"http://www.wikidata.org/entity/Q841781
">Q841781
</a
>,
453 <a href=
"http://www.wikidata.org/entity/Q1548193
">Q1548193
</a
>,
454 <a href=
"http://www.wikidata.org/entity/Q499031
">Q499031
</a
>,
455 <a href=
"http://www.wikidata.org/entity/Q1564769
">Q1564769
</a
>,
456 <a href=
"http://www.wikidata.org/entity/Q1585239
">Q1585239
</a
>,
457 <a href=
"http://www.wikidata.org/entity/Q1585569
">Q1585569
</a
>,
458 <a href=
"http://www.wikidata.org/entity/Q1624236
">Q1624236
</a
>,
459 <a href=
"http://www.wikidata.org/entity/Q4796595
">Q4796595
</a
>,
460 <a href=
"http://www.wikidata.org/entity/Q4853469
">Q4853469
</a
>,
461 <a href=
"http://www.wikidata.org/entity/Q4873046
">Q4873046
</a
>,
462 <a href=
"http://www.wikidata.org/entity/Q915016
">Q915016
</a
>,
463 <a href=
"http://www.wikidata.org/entity/Q4660396
">Q4660396
</a
>,
464 <a href=
"http://www.wikidata.org/entity/Q4677708
">Q4677708
</a
>,
465 <a href=
"http://www.wikidata.org/entity/Q4738449
">Q4738449
</a
>,
466 <a href=
"http://www.wikidata.org/entity/Q4756096
">Q4756096
</a
>,
467 <a href=
"http://www.wikidata.org/entity/Q4766785
">Q4766785
</a
>,
468 <a href=
"http://www.wikidata.org/entity/Q880357
">Q880357
</a
>,
469 <a href=
"http://www.wikidata.org/entity/Q882066
">Q882066
</a
>,
470 <a href=
"http://www.wikidata.org/entity/Q882066
">Q882066
</a
>,
471 <a href=
"http://www.wikidata.org/entity/Q204191
">Q204191
</a
>,
472 <a href=
"http://www.wikidata.org/entity/Q204191
">Q204191
</a
>,
473 <a href=
"http://www.wikidata.org/entity/Q1194170
">Q1194170
</a
>,
474 <a href=
"http://www.wikidata.org/entity/Q940014
">Q940014
</a
>,
475 <a href=
"http://www.wikidata.org/entity/Q946863
">Q946863
</a
>,
476 <a href=
"http://www.wikidata.org/entity/Q172837
">Q172837
</a
>,
477 <a href=
"http://www.wikidata.org/entity/Q573077
">Q573077
</a
>,
478 <a href=
"http://www.wikidata.org/entity/Q1219005
">Q1219005
</a
>,
479 <a href=
"http://www.wikidata.org/entity/Q1219599
">Q1219599
</a
>,
480 <a href=
"http://www.wikidata.org/entity/Q1643798
">Q1643798
</a
>,
481 <a href=
"http://www.wikidata.org/entity/Q1656352
">Q1656352
</a
>,
482 <a href=
"http://www.wikidata.org/entity/Q1659549
">Q1659549
</a
>,
483 <a href=
"http://www.wikidata.org/entity/Q1660007
">Q1660007
</a
>,
484 <a href=
"http://www.wikidata.org/entity/Q1698154
">Q1698154
</a
>,
485 <a href=
"http://www.wikidata.org/entity/Q1737980
">Q1737980
</a
>,
486 <a href=
"http://www.wikidata.org/entity/Q1877284
">Q1877284
</a
>,
487 <a href=
"http://www.wikidata.org/entity/Q1199354
">Q1199354
</a
>,
488 <a href=
"http://www.wikidata.org/entity/Q1199354
">Q1199354
</a
>,
489 <a href=
"http://www.wikidata.org/entity/Q1199451
">Q1199451
</a
>,
490 <a href=
"http://www.wikidata.org/entity/Q1211871
">Q1211871
</a
>,
491 <a href=
"http://www.wikidata.org/entity/Q1212179
">Q1212179
</a
>,
492 <a href=
"http://www.wikidata.org/entity/Q1238382
">Q1238382
</a
>,
493 <a href=
"http://www.wikidata.org/entity/Q4906454
">Q4906454
</a
>,
494 <a href=
"http://www.wikidata.org/entity/Q320219
">Q320219
</a
>,
495 <a href=
"http://www.wikidata.org/entity/Q1148649
">Q1148649
</a
>,
496 <a href=
"http://www.wikidata.org/entity/Q645094
">Q645094
</a
>,
497 <a href=
"http://www.wikidata.org/entity/Q5050350
">Q5050350
</a
>,
498 <a href=
"http://www.wikidata.org/entity/Q5166548
">Q5166548
</a
>,
499 <a href=
"http://www.wikidata.org/entity/Q2677926
">Q2677926
</a
>,
500 <a href=
"http://www.wikidata.org/entity/Q2698139
">Q2698139
</a
>,
501 <a href=
"http://www.wikidata.org/entity/Q2707305
">Q2707305
</a
>,
502 <a href=
"http://www.wikidata.org/entity/Q2740725
">Q2740725
</a
>,
503 <a href=
"http://www.wikidata.org/entity/Q2024780
">Q2024780
</a
>,
504 <a href=
"http://www.wikidata.org/entity/Q2117418
">Q2117418
</a
>,
505 <a href=
"http://www.wikidata.org/entity/Q2138984
">Q2138984
</a
>,
506 <a href=
"http://www.wikidata.org/entity/Q1127992
">Q1127992
</a
>,
507 <a href=
"http://www.wikidata.org/entity/Q1058087
">Q1058087
</a
>,
508 <a href=
"http://www.wikidata.org/entity/Q1070484
">Q1070484
</a
>,
509 <a href=
"http://www.wikidata.org/entity/Q1080080
">Q1080080
</a
>,
510 <a href=
"http://www.wikidata.org/entity/Q1090813
">Q1090813
</a
>,
511 <a href=
"http://www.wikidata.org/entity/Q1251918
">Q1251918
</a
>,
512 <a href=
"http://www.wikidata.org/entity/Q1254110
">Q1254110
</a
>,
513 <a href=
"http://www.wikidata.org/entity/Q1257070
">Q1257070
</a
>,
514 <a href=
"http://www.wikidata.org/entity/Q1257079
">Q1257079
</a
>,
515 <a href=
"http://www.wikidata.org/entity/Q1197410
">Q1197410
</a
>,
516 <a href=
"http://www.wikidata.org/entity/Q1198423
">Q1198423
</a
>,
517 <a href=
"http://www.wikidata.org/entity/Q706951
">Q706951
</a
>,
518 <a href=
"http://www.wikidata.org/entity/Q723239
">Q723239
</a
>,
519 <a href=
"http://www.wikidata.org/entity/Q2079261
">Q2079261
</a
>,
520 <a href=
"http://www.wikidata.org/entity/Q1171364
">Q1171364
</a
>,
521 <a href=
"http://www.wikidata.org/entity/Q617858
">Q617858
</a
>,
522 <a href=
"http://www.wikidata.org/entity/Q5166611
">Q5166611
</a
>,
523 <a href=
"http://www.wikidata.org/entity/Q5166611
">Q5166611
</a
>,
524 <a href=
"http://www.wikidata.org/entity/Q324513
">Q324513
</a
>,
525 <a href=
"http://www.wikidata.org/entity/Q374172
">Q374172
</a
>,
526 <a href=
"http://www.wikidata.org/entity/Q7533269
">Q7533269
</a
>,
527 <a href=
"http://www.wikidata.org/entity/Q970386
">Q970386
</a
>,
528 <a href=
"http://www.wikidata.org/entity/Q976849
">Q976849
</a
>,
529 <a href=
"http://www.wikidata.org/entity/Q7458614
">Q7458614
</a
>,
530 <a href=
"http://www.wikidata.org/entity/Q5347416
">Q5347416
</a
>,
531 <a href=
"http://www.wikidata.org/entity/Q5460005
">Q5460005
</a
>,
532 <a href=
"http://www.wikidata.org/entity/Q5463392
">Q5463392
</a
>,
533 <a href=
"http://www.wikidata.org/entity/Q3038555
">Q3038555
</a
>,
534 <a href=
"http://www.wikidata.org/entity/Q5288458
">Q5288458
</a
>,
535 <a href=
"http://www.wikidata.org/entity/Q2346516
">Q2346516
</a
>,
536 <a href=
"http://www.wikidata.org/entity/Q5183645
">Q5183645
</a
>,
537 <a href=
"http://www.wikidata.org/entity/Q5185497
">Q5185497
</a
>,
538 <a href=
"http://www.wikidata.org/entity/Q5216127
">Q5216127
</a
>,
539 <a href=
"http://www.wikidata.org/entity/Q5223127
">Q5223127
</a
>,
540 <a href=
"http://www.wikidata.org/entity/Q5261159
">Q5261159
</a
>,
541 <a href=
"http://www.wikidata.org/entity/Q1300759
">Q1300759
</a
>,
542 <a href=
"http://www.wikidata.org/entity/Q5521241
">Q5521241
</a
>,
543 <a href=
"http://www.wikidata.org/entity/Q7733434
">Q7733434
</a
>,
544 <a href=
"http://www.wikidata.org/entity/Q7736264
">Q7736264
</a
>,
545 <a href=
"http://www.wikidata.org/entity/Q7737032
">Q7737032
</a
>,
546 <a href=
"http://www.wikidata.org/entity/Q7882671
">Q7882671
</a
>,
547 <a href=
"http://www.wikidata.org/entity/Q7719427
">Q7719427
</a
>,
548 <a href=
"http://www.wikidata.org/entity/Q7719444
">Q7719444
</a
>,
549 <a href=
"http://www.wikidata.org/entity/Q7722575
">Q7722575
</a
>,
550 <a href=
"http://www.wikidata.org/entity/Q2629763
">Q2629763
</a
>,
551 <a href=
"http://www.wikidata.org/entity/Q2640346
">Q2640346
</a
>,
552 <a href=
"http://www.wikidata.org/entity/Q2649671
">Q2649671
</a
>,
553 <a href=
"http://www.wikidata.org/entity/Q7703851
">Q7703851
</a
>,
554 <a href=
"http://www.wikidata.org/entity/Q7747041
">Q7747041
</a
>,
555 <a href=
"http://www.wikidata.org/entity/Q6544949
">Q6544949
</a
>,
556 <a href=
"http://www.wikidata.org/entity/Q6672759
">Q6672759
</a
>,
557 <a href=
"http://www.wikidata.org/entity/Q2445896
">Q2445896
</a
>,
558 <a href=
"http://www.wikidata.org/entity/Q12124891
">Q12124891
</a
>,
559 <a href=
"http://www.wikidata.org/entity/Q3127044
">Q3127044
</a
>,
560 <a href=
"http://www.wikidata.org/entity/Q2511262
">Q2511262
</a
>,
561 <a href=
"http://www.wikidata.org/entity/Q2517672
">Q2517672
</a
>,
562 <a href=
"http://www.wikidata.org/entity/Q2543165
">Q2543165
</a
>,
563 <a href=
"http://www.wikidata.org/entity/Q426628
">Q426628
</a
>,
564 <a href=
"http://www.wikidata.org/entity/Q426628
">Q426628
</a
>,
565 <a href=
"http://www.wikidata.org/entity/Q12126890
">Q12126890
</a
>,
566 <a href=
"http://www.wikidata.org/entity/Q13359969
">Q13359969
</a
>,
567 <a href=
"http://www.wikidata.org/entity/Q13359969
">Q13359969
</a
>,
568 <a href=
"http://www.wikidata.org/entity/Q2294295
">Q2294295
</a
>,
569 <a href=
"http://www.wikidata.org/entity/Q2294295
">Q2294295
</a
>,
570 <a href=
"http://www.wikidata.org/entity/Q2559509
">Q2559509
</a
>,
571 <a href=
"http://www.wikidata.org/entity/Q2559912
">Q2559912
</a
>,
572 <a href=
"http://www.wikidata.org/entity/Q7760469
">Q7760469
</a
>,
573 <a href=
"http://www.wikidata.org/entity/Q6703974
">Q6703974
</a
>,
574 <a href=
"http://www.wikidata.org/entity/Q4744
">Q4744
</a
>,
575 <a href=
"http://www.wikidata.org/entity/Q7766962
">Q7766962
</a
>,
576 <a href=
"http://www.wikidata.org/entity/Q7768516
">Q7768516
</a
>,
577 <a href=
"http://www.wikidata.org/entity/Q7769205
">Q7769205
</a
>,
578 <a href=
"http://www.wikidata.org/entity/Q7769988
">Q7769988
</a
>,
579 <a href=
"http://www.wikidata.org/entity/Q2946945
">Q2946945
</a
>,
580 <a href=
"http://www.wikidata.org/entity/Q3212086
">Q3212086
</a
>,
581 <a href=
"http://www.wikidata.org/entity/Q3212086
">Q3212086
</a
>,
582 <a href=
"http://www.wikidata.org/entity/Q18218448
">Q18218448
</a
>,
583 <a href=
"http://www.wikidata.org/entity/Q18218448
">Q18218448
</a
>,
584 <a href=
"http://www.wikidata.org/entity/Q18218448
">Q18218448
</a
>,
585 <a href=
"http://www.wikidata.org/entity/Q6909175
">Q6909175
</a
>,
586 <a href=
"http://www.wikidata.org/entity/Q7405709
">Q7405709
</a
>,
587 <a href=
"http://www.wikidata.org/entity/Q7416149
">Q7416149
</a
>,
588 <a href=
"http://www.wikidata.org/entity/Q7239952
">Q7239952
</a
>,
589 <a href=
"http://www.wikidata.org/entity/Q7317332
">Q7317332
</a
>,
590 <a href=
"http://www.wikidata.org/entity/Q7783674
">Q7783674
</a
>,
591 <a href=
"http://www.wikidata.org/entity/Q7783704
">Q7783704
</a
>,
592 <a href=
"http://www.wikidata.org/entity/Q7857590
">Q7857590
</a
>,
593 <a href=
"http://www.wikidata.org/entity/Q3372526
">Q3372526
</a
>,
594 <a href=
"http://www.wikidata.org/entity/Q3372642
">Q3372642
</a
>,
595 <a href=
"http://www.wikidata.org/entity/Q3372816
">Q3372816
</a
>,
596 <a href=
"http://www.wikidata.org/entity/Q3372909
">Q3372909
</a
>,
597 <a href=
"http://www.wikidata.org/entity/Q7959649
">Q7959649
</a
>,
598 <a href=
"http://www.wikidata.org/entity/Q7977485
">Q7977485
</a
>,
599 <a href=
"http://www.wikidata.org/entity/Q7992684
">Q7992684
</a
>,
600 <a href=
"http://www.wikidata.org/entity/Q3817966
">Q3817966
</a
>,
601 <a href=
"http://www.wikidata.org/entity/Q3821852
">Q3821852
</a
>,
602 <a href=
"http://www.wikidata.org/entity/Q3420907
">Q3420907
</a
>,
603 <a href=
"http://www.wikidata.org/entity/Q3429733
">Q3429733
</a
>,
604 <a href=
"http://www.wikidata.org/entity/Q774474
">Q774474
</a
></p
>
606 <p
>As usual, if you use Bitcoin and want to show your support of my
607 activities, please send Bitcoin donations to my address
608 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
613 <title>A one-way wall on the border?
</title>
614 <link>http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html
</link>
615 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html
</guid>
616 <pubDate>Sat,
14 Oct
2017 22:
10:
00 +
0200</pubDate>
617 <description><p
>I find it fascinating how many of the people being locked inside
618 the proposed border wall between USA and Mexico support the idea. The
619 proposal to keep Mexicans out reminds me of
620 <a href=
"http://www.history.com/news/
10-things-you-may-not-know-about-the-berlin-wall
">the
621 propaganda twist from the East Germany government
</a
> calling the wall
622 the “Antifascist Bulwark” after erecting the Berlin Wall, claiming
623 that the wall was erected to keep enemies from creeping into East
624 Germany, while it was obvious to the people locked inside it that it
625 was erected to keep the people from escaping.
</p
>
627 <p
>Do the people in USA supporting this wall really believe it is a
628 one way wall, only keeping people on the outside from getting in,
629 while not keeping people in the inside from getting out?
</p
>
631 <p
>As usual, if you use Bitcoin and want to show your support of my
632 activities, please send Bitcoin donations to my address
633 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
638 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
639 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
640 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
641 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
642 <description><p
>At my nearby maker space,
643 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
644 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
645 on Windows and MacOS X than Linux, because the software involved had
646 to be manually compiled and set up on Linux while premade packages
647 worked out of the box on Windows and MacOS X. I found this annoying,
648 as the software involved,
649 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
650 and should be trivial to get up and running on Linux if someone took
651 the time to package it for the relevant distributions. I even found
652 <a href=
"https://bugs.debian.org/
706656">a request for adding into
653 Debian
</a
> from
2013, which had seem some activity over the years but
654 never resulted in the software showing up in Debian. So a few days
655 ago I offered my help to try to improve the situation.
</p
>
657 <p
>Now I am very happy to see that all the packages required by a
658 working Cura in Debian are uploaded into Debian and waiting in the NEW
659 queue for the ftpmasters to have a look. You can track the progress
661 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
662 status page for the
3D printer team
</a
>.
</p
>
664 <p
>The uploaded packages are a bit behind upstream, and was uploaded
665 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
666 queue
</a
> while we work up updating the packages to the latest
667 upstream version.
</p
>
669 <p
>On a related note, two competitors for Cura, which I found harder
670 to use and was unable to configure correctly for Ultimaker
2+ in the
671 short time I spent on it, are already in Debian. If you are looking
672 for
3D printer
"slicers
" and want something already available in
674 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
675 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
676 The latter is a fork of the former.
</p
>
678 <p
>As usual, if you use Bitcoin and want to show your support of my
679 activities, please send Bitcoin donations to my address
680 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
685 <title>Mangler du en skrue, eller har du en skrue løs?
</title>
686 <link>http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html
</link>
687 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html
</guid>
688 <pubDate>Wed,
4 Oct
2017 09:
40:
00 +
0200</pubDate>
689 <description>Når jeg holder på med ulike prosjekter, så trenger jeg stadig ulike
690 skruer. Det siste prosjektet jeg holder på med er å lage
691 <a href=
"https://www.thingiverse.com/thing:
676916">en boks til en
692 HDMI-touch-skjerm
</a
> som skal brukes med Raspberry Pi. Boksen settes
693 sammen med skruer og bolter, og jeg har vært i tvil om hvor jeg kan
694 få tak i de riktige skruene. Clas Ohlson og Jernia i nærheten har
695 sjelden hatt det jeg trenger. Men her om dagen fikk jeg et fantastisk
696 tips for oss som bor i Oslo.
697 <a href=
"http://www.zachskruer.no/
">Zachariassen Jernvare AS
</a
> i
698 <a href=
"http://www.openstreetmap.org/?mlat=
59.93421&mlon=
10.76795#map=
19/
59.93421/
10.76795">Hegermannsgate
699 23A på Torshov
</a
> har et fantastisk utvalg, og åpent mellom
09:
00 og
700 17:
00. De selger skruer, muttere, bolter, skiver etc i løs vekt, og
701 så langt har jeg fått alt jeg har lett etter. De har i tillegg det
702 meste av annen jernvare, som verktøy, lamper, ledninger, etc. Jeg
703 håper de har nok kunder til å holde det gående lenge, da dette er en
704 butikk jeg kommer til å besøke ofte. Butikken er et funn å ha i
705 nabolaget for oss som liker å bygge litt selv. :)
</p
>
707 <p
>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
708 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
710 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
715 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
716 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
717 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
718 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
719 <description><p
>Every mobile phone announce its existence over radio to the nearby
720 mobile cell towers. And this radio chatter is available for anyone
721 with a radio receiver capable of receiving them. Details about the
722 mobile phones with very good accuracy is of course collected by the
723 phone companies, but this is not the topic of this blog post. The
724 mobile phone radio chatter make it possible to figure out when a cell
725 phone is nearby, as it include the SIM card ID (IMSI). By paying
726 attention over time, one can see when a phone arrive and when it leave
727 an area. I believe it would be nice to make this information more
728 available to the general public, to make more people aware of how
729 their phones are announcing their whereabouts to anyone that care to
732 <p
>I am very happy to report that we managed to get something
733 visualizing this information up and running for
734 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
735 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
736 library. The solution is based on the
737 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
738 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
739 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
740 Sone from the Computer Science department of the University of
741 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
742 IMSIs) as dots in a web browser graph, with lines to the dot
743 representing mobile base station it is talking to. It was working in
744 the lab yesterday, and was moved into place this morning.
</p
>
746 <p
>We set up a fairly powerful desktop machine using Debian
747 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
748 connected and visualize the visible cell phone towers using an
749 <a href=
"https://github.com/marlow925/hopglass
">English version of
750 Hopglass
</a
>. A fairly powerfull machine is needed as the
751 grgsm_livemon_headless processes from
752 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
753 the radio signal to data packages is quite CPU intensive.
</p
>
755 <p
>The frequencies to listen to, are identified using a slightly
756 patched scan-and-livemon (to set the --args values for each receiver),
757 and the Hopglass data is generated using the
758 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
759 in my meshviewer-output branch
</a
>. For some reason we could not get
760 more than four SDRs working. There is also a geographical map trying
761 to show the location of the base stations, but I believe their
762 coordinates are hardcoded to some random location in Germany, I
763 believe. The code should be replaced with code to look up location in
764 a text file, a sqlite database or one of the online databases
766 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
767 issue for the topic
</a
>.
769 <p
>If this sound interesting, visit the stand at the festival!
</p
>
774 <title>Easier recipe to observe the cell phones around you
</title>
775 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
776 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
777 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
778 <description><p
>A little more than a month ago I wrote
779 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
780 to observe the SIM card ID (aka IMSI number) of mobile phones talking
781 to nearby mobile phone base stations using Debian GNU/Linux and a
782 cheap USB software defined radio
</a
>, and thus being able to pinpoint
783 the location of people and equipment (like cars and trains) with an
784 accuracy of a few kilometer. Since then we have worked to make the
785 procedure even simpler, and it is now possible to do this without any
786 manual frequency tuning and without building your own packages.
</p
>
788 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
789 package is now included in Debian testing and unstable, and the
790 IMSI-catcher code no longer require root access to fetch and decode
791 the GSM data collected using gr-gsm.
</p
>
793 <p
>Here is an updated recipe, using packages built by Debian and a git
794 clone of two python scripts:
</p
>
798 <li
>Start with a Debian machine running the Buster version (aka
801 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
802 python-scapy
</tt
>' as root to install required packages.
</li
>
804 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
805 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
807 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
809 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
810 scan-and-livemon
</tt
>' to locate the frequency of nearby base
811 stations and start listening for GSM packages on one of them.
</li
>
813 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
814 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
818 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
819 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
820 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
821 work with RTL
8232 and other similar USB radio receivers you can get
823 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
824 from ebay
</a
>), so for now the solution is to scan using the RTL radio
825 and only use HackRF for fetching GSM data.
</p
>
827 <p
>As far as I can tell, a cell phone only show up on one of the
828 frequencies at the time, so if you are going to track and count every
829 cell phone around you, you need to listen to all the frequencies used.
830 To listen to several frequencies, use the --numrecv argument to
831 scan-and-livemon to use several receivers. Further, I am not sure if
832 phones using
3G or
4G will show as talking GSM to base stations, so
833 this approach might not see all phones around you. I typically see
834 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
836 <p
>I
've tried to run the scanner on a
837 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
838 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
839 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
840 stdout, I am told there it is caused by a buffer overflow between the
841 radio and GNU Radio, caused by the program being unable to read the
842 GSM data fast enough. If you see a stream of
'O
's from the terminal
843 where you started scan-and-livemon, you need a give the process more
844 CPU power. Perhaps someone are able to optimize the code to a point
845 where it become possible to set up RPi3 based GSM sniffers? I tried
846 using Raspbian instead of Debian, but there seem to be something wrong
847 with GNU Radio on raspbian, causing glibc to abort().
</p
>